5.1.12-stable review
Subsystems (3)
Greg Kroah-Hartman
maintainerPATCH 1/115 drm/nouveau: add kconfig option to turn off nouveau legacy contexts. (v3)
In reply to Greg Kroah-HartmanFrom: Dave Airlie <[email protected]>
commit b30a43ac7132cdda833ac4b13dd1ebd35ace14b7 upstream.
There was a nouveau DDX that relied on legacy context ioctls to work, but we fixed it years ago, give distros that have a modern DDX the option to break the uAPI and close the mess of holes that legacy context support is.
Full context of the story:
commit 0e975980d435d58df2d430d688b8c18778b42218
Author: Peter Antoine <[email protected]> Date: Tue Jun 23 08:18:49 2015 +0100
drm: Turn off Legacy Context Functions
The context functions are not used by the i915 driver and should not be used by modeset drivers. These driver functions contain several bugs and security holes. This change makes these functions optional can be turned on by a setting, they are turned off by default for modeset driver with the exception of the nouvea driver that may require them with an old version of libdrm.
The previous attempt was
commit 7c510133d93dd6f15ca040733ba7b2891ed61fd1
Author: Daniel Vetter <[email protected]>
Date: Thu Aug 8 15:41:21 2013 +0200
drm: mark context support as a legacy subsystem
but this had to be reverted
commit c21eb21cb50d58e7cbdcb8b9e7ff68b85cfa5095
Author: Dave Airlie <[email protected]>
Date: Fri Sep 20 08:32:59 2013 +1000
Revert "drm: mark context support as a legacy subsystem"
v2: remove returns from void function, and formatting (Daniel Vetter)
v3:
- s/Nova/nouveau/ in the commit message, and add references to the previous attempts
- drop the part touching the drm hw lock, that should be a separate patch.
v2: move DRM_VM dependency into legacy config.
v3: fix missing dep (kbuild robot)
--- drivers/gpu/drm/nouveau/Kconfig | 13 ++++++++++++- drivers/gpu/drm/nouveau/nouveau_drm.c | 7 +++++-- 2 files changed, 17 insertions(+), 3 deletions(-)
drivers/gpu/drm/nouveau/Kconfig +12 -1
@@ -17,10 +17,21 @@ config DRM_NOUVEAU select INPUT if ACPI && X86 select THERMAL if ACPI && X86 select ACPI_VIDEO if ACPI && X86 - select DRM_VM help Choose this option for open-source NVIDIA support. +config NOUVEAU_LEGACY_CTX_SUPPORT + bool "Nouveau legacy context support" + depends on DRM_NOUVEAU + select DRM_VM + default y + help + There was a version of the nouveau DDX that relied on legacy + ctx ioctls not erroring out. But that was back in time a long + ways, so offer a way to disable it now. For uapi compat with + old nouveau ddx this should be on by default, but modern distros + should consider turning it off. + config NOUVEAU_PLATFORM_DRIVER bool "Nouveau (NVIDIA) SoC GPUs" depends on DRM_NOUVEAU && ARCH_TEGRA
drivers/gpu/drm/nouveau/nouveau_drm.c +5 -2
@@ -1094,8 +1094,11 @@ nouveau_driver_fops = {static struct drm_driver driver_stub = { .driver_features = -DRIVER_GEM |DRIVER_MODESET |DRIVER_PRIME |DRIVER_RENDER | -DRIVER_KMS_LEGACY_CONTEXT , +DRIVER_GEM |DRIVER_MODESET |DRIVER_PRIME |DRIVER_RENDER +#if defined(CONFIG_NOUVEAU_LEGACY_CTX_SUPPORT) + |DRIVER_KMS_LEGACY_CONTEXT +#endif + , .open = nouveau_drm_open, .postclose = nouveau_drm_postclose,
Greg Kroah-Hartman
maintainerPATCH 10/115 HID: wacom: Correct button numbering 2nd-gen Intuos Pro over Bluetooth
In reply to Greg Kroah-HartmanFrom: Jason Gerecke <[email protected]>
commit 6441fc781c344df61402be1fde582c4491fa35fa upstream.
The button numbering of the 2nd-gen Intuos Pro is not consistent between the USB and Bluetooth interfaces. Over USB, the HID_GENERIC codepath enumerates the eight ExpressKeys first (BTN_0 - BTN_7) followed by the center modeswitch button (BTN_8). The Bluetooth codepath, however, has the center modeswitch button as BTN_0 and the the eight ExpressKeys as BTN_1 - BTN_8. To ensure userspace button mappings do not change depending on how the tablet is connected, modify the Bluetooth codepath to report buttons in the same order as USB.
To ensure the mode switch LED continues to toggle in response to the mode switch button, the wacom_is_led_toggled function also requires a small update.
--- drivers/hid/wacom_wac.c | 11 +++++++---- 1 file changed, 7 insertions(+), 4 deletions(-)
drivers/hid/wacom_wac.c +7 -4
@@ -1383,7 +1383,7 @@ static void wacom_intuos_pro2_bt_pad(strstruct input_dev *pad_input = wacom->pad_input;unsigned char *data = wacom->data; -int buttons = (data[282 ] <<1 ) | ((data[281 ] >>6 ) &0x01 ); +int buttons = data[282 ] | ((data[281 ] &0x40 ) <<2 );int ring = data[285 ] &0x7F ;bool ringstatus = data[285 ] &0x80 ;bool prox = buttons || ringstatus;
@@ -3832,7 +3832,7 @@ static void wacom_24hd_update_leds(strucstatic bool wacom_is_led_toggled (struct wacom *wacom,int button_count,int mask,int group) { -int button_per_group; +int group_button;/* * 21UX2 has LED group 1 to the left and LED group 0
@@ -3842,9 +3842,12 @@ static bool wacom_is_led_toggled(structif (wacom->wacom_wac.features.type ==WACOM_21UX2 ) group =1 - group; - button_per_group = button_count/wacom->led.count; + group_button = group * (button_count/wacom->led.count); -return mask & (1 << (group * button_per_group)); +if (wacom->wacom_wac.features.type ==INTUOSP2_BT ) + group_button =8 ; + +return mask & (1 << group_button); } static void wacom_update_led(struct wacom *wacom, int button_count, int mask,
Greg Kroah-Hartman
maintainerPATCH 11/115 HID: wacom: Sync INTUOSP2_BT touch state after each frame if necessary
In reply to Greg Kroah-HartmanFrom: Jason Gerecke <[email protected]>
commit 69dbdfffef20c715df9f381b2cee4e9e0a4efd93 upstream.
The Bluetooth interface of the 2nd-gen Intuos Pro batches together four independent "frames" of finger data into a single report. Each frame is essentially equivalent to a single USB report, with the up-to-10 fingers worth of information being spread across two frames. At the moment the driver only calls input_sync after processing all four frames have been processed, which can result in the driver sending multiple updates for a single slot within the same SYN_REPORT. This can confuse userspace, so modify the driver to sync more often if necessary (i.e., after reporting the state of all fingers).
--- drivers/hid/wacom_wac.c | 10 ++++++++-- 1 file changed, 8 insertions(+), 2 deletions(-)
drivers/hid/wacom_wac.c +8 -2
@@ -1371,11 +1371,17 @@ static void wacom_intuos_pro2_bt_touch(sif (wacom->num_contacts_left <=0 ) { wacom->num_contacts_left =0 ; wacom->shared->touch_down =wacom_wac_finger_count_touches (wacom); +input_sync (touch_input); } } -input_report_switch (touch_input,SW_MUTE_DEVICE , !(data[281 ] >>7 )); -input_sync (touch_input); +if (wacom->num_contacts_left ==0 ) { +// Be careful that we don't accidentally call input_sync with +// only a partial set of fingers of processed +input_report_switch (touch_input,SW_MUTE_DEVICE , !(data[281 ] >>7 )); +input_sync (touch_input); + } + }static void wacom_intuos_pro2_bt_pad (struct wacom_wac *wacom)
Greg Kroah-Hartman
maintainerPATCH 12/115 Revert "ALSA: hda/realtek - Improve the headset mic for Acer Aspire laptops"
In reply to Greg Kroah-HartmanFrom: Hui Wang <[email protected]>
commit 17d304604a88cf20c8dfd2c95d3decb9c4f8bca4 upstream.
This reverts commit 9cb40eb184c4220d244a532bd940c6345ad9dbd9.
This patch introduces noise and headphone playback issue after rebooting or suspending/resuming. Let us revert it.
--- sound/pci/hda/patch_realtek.c | 16 +++++----------- 1 file changed, 5 insertions(+), 11 deletions(-)
sound/pci/hda/patch_realtek.c +5 -11
@@ -6166,15 +6166,13 @@ static const struct hda_fixup alc269_fix .chain_id = ALC269_FIXUP_THINKPAD_ACPI, }, [ALC255_FIXUP_ACER_MIC_NO_PRESENCE] = { - .type = HDA_FIXUP_VERBS, - .v.verbs = (const struct hda_verb []) { -/* Enable the Mic */ - {0x20 ,AC_VERB_SET_COEF_INDEX ,0x45 }, - {0x20 ,AC_VERB_SET_PROC_COEF ,0x5089 }, - {} + .type = HDA_FIXUP_PINS, + .v.pins = (const struct hda_pintbl []) { + {0x19 ,0x01a1913c },/* use as headset mic, without its own jack detect */ + { } }, .chained = true, - .chain_id =ALC269_FIXUP_LIFEBOOK_EXTMIC + .chain_id =ALC255_FIXUP_HEADSET_MODE }, [ALC255_FIXUP_ASUS_MIC_NO_PRESENCE] = { .type = HDA_FIXUP_PINS,
@@ -7220,10 +7218,6 @@ static const struct snd_hda_pin_quirk al {0x19, 0x0181303F}, {0x21, 0x0221102f}),SND_HDA_PIN_QUIRK (0x10ec0255 ,0x1025 ,"Acer" ,ALC255_FIXUP_ACER_MIC_NO_PRESENCE , - {0x12, 0x90a60140}, - {0x14, 0x90170120}, - {0x21, 0x02211030}), -SND_HDA_PIN_QUIRK (0x10ec0255 ,0x1025 ,"Acer" ,ALC255_FIXUP_ACER_MIC_NO_PRESENCE , {0x12, 0x90a601c0}, {0x14, 0x90171120}, {0x21, 0x02211030}),
Greg Kroah-Hartman
maintainerPATCH 13/115 ALSA: oxfw: allow PCM capture for Stanton SCS.1m
In reply to Greg Kroah-HartmanFrom: Takashi Sakamoto <[email protected]>
commit d8fa87c368f5b4096c4746894fdcc195da285df1 upstream.
Stanton SCS.1m can transfer isochronous packet with Multi Bit Linear Audio data channels, therefore it allows software to capture PCM substream. However, ALSA oxfw driver doesn't.
This commit changes the driver to add one PCM substream for capture direction.
--- sound/firewire/oxfw/oxfw.c | 3 --- 1 file changed, 3 deletions(-)
sound/firewire/oxfw/oxfw.c +0 -3
@@ -148,9 +148,6 @@ static int detect_quirks(struct snd_oxfw oxfw->midi_input_ports =0 ; oxfw->midi_output_ports =0 ; -/* Output stream exists but no data channels are useful. */ - oxfw->has_output = false; -return snd_oxfw_scs1x_add (oxfw); }
Greg Kroah-Hartman
maintainerPATCH 14/115 ALSA: ice1712: Check correct return value to snd_i2c_sendbytes (EWS/DMX 6Fire)
In reply to Greg Kroah-HartmanFrom: Rui Nuno Capela <[email protected]>
commit 352bcae97f9ba87801f497571cdec20af190efe1 upstream.
Check for exact and correct return value to snd_i2c_sendbytes call for EWS/DMX 6Fire (snd_ice1712).
Fixes a systemic error on every boot starting from kernel 5.1 onwards to snd_ice1712 driver ("cannot send pca") on Terratec EWS/DMX 6Fire PCI soundcards.
Check for exact and correct return value to snd_i2c_sendbytes call for EWS/DMX 6Fire (snd_ice1712).
Fixes a systemic error on every boot to snd_ice1712 driver ("cannot send pca") on Terratec EWS/DMX 6Fire PCI soundcards.
--- sound/pci/ice1712/ews.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
sound/pci/ice1712/ews.c +1 -1
@@ -826,7 +826,7 @@ static int snd_ice1712_6fire_read_pca(stsnd_i2c_lock (ice->i2c); byte = reg; -if (snd_i2c_sendbytes (spec->i2cdevs[EWS_I2C_6FIRE ], &byte,1 )) { +if (snd_i2c_sendbytes (spec->i2cdevs[EWS_I2C_6FIRE ], &byte,1 ) !=1 ) {snd_i2c_unlock (ice->i2c);dev_err (ice->card->dev,"cannot send pca\n" );return -EIO ;
Greg Kroah-Hartman
maintainerPATCH 15/115 ALSA: hda/realtek - Update headset mode for ALC256
In reply to Greg Kroah-HartmanFrom: Kailang Yang <[email protected]>
commit 717f43d81afc1250300479075952a0e36d74ded3 upstream.
ALC255 and ALC256 were some difference for hidden register. This update was suitable for ALC256.
--- sound/pci/hda/patch_realtek.c | 75 +++++++++++++++++++++++++++++++++--------- 1 file changed, 60 insertions(+), 15 deletions(-)
sound/pci/hda/patch_realtek.c +60 -15
@@ -4084,18 +4084,19 @@ static struct coef_fw alc225_pre_hsmode[static void alc_headset_mode_unplugged (struct hda_codec *codec) {static struct coef_fw coef0255[] = { +WRITE_COEF (0x1b ,0x0c0b ),/* LDO and MISC control */ WRITE_COEF (0x45 ,0xd089 ),/* UAJ function set to menual mode */ UPDATE_COEFEX (0x57 ,0x05 ,1 <<14 ,0 ),/* Direct Drive HP Amp control(Set to verb control)*/ WRITE_COEF (0x06 ,0x6104 ),/* Set MIC2 Vref gate with HP */ WRITE_COEFEX (0x57 ,0x03 ,0x8aa6 ),/* Direct Drive HP Amp control */ {} }; -static struct coef_fw coef0255_1[] = { -WRITE_COEF (0x1b ,0x0c0b ),/* LDO and MISC control */ - {} - };static struct coef_fw coef0256[] = {WRITE_COEF (0x1b ,0x0c4b ),/* LDO and MISC control */ +WRITE_COEF (0x45 ,0xd089 ),/* UAJ function set to menual mode */ +WRITE_COEF (0x06 ,0x6104 ),/* Set MIC2 Vref gate with HP */ +WRITE_COEFEX (0x57 ,0x03 ,0x09a3 ),/* Direct Drive HP Amp control */ +UPDATE_COEFEX (0x57 ,0x05 ,1 <<14 ,0 ),/* Direct Drive HP Amp control(Set to verb control)*/ {} };static struct coef_fw coef0233[] = {
@@ -4158,13 +4159,11 @@ static void alc_headset_mode_unplugged(sswitch (codec->core.vendor_id) {case 0x10ec0255 : -alc_process_coef_fw (codec, coef0255_1);alc_process_coef_fw (codec, coef0255);break ;case 0x10ec0236 :case 0x10ec0256 :alc_process_coef_fw (codec, coef0256); -alc_process_coef_fw (codec, coef0255);break ;case 0x10ec0234 :case 0x10ec0274 :
@@ -4217,6 +4216,12 @@ static void alc_headset_mode_mic_in(stru WRITE_COEF(0x06, 0x6100), /* Set MIC2 Vref gate to normal */ {} }; +static struct coef_fw coef0256[] = { +UPDATE_COEFEX (0x57 ,0x05 ,1 <<14 ,1 <<14 ),/* Direct Drive HP Amp control(Set to verb control)*/ +WRITE_COEFEX (0x57 ,0x03 ,0x09a3 ), +WRITE_COEF (0x06 ,0x6100 ),/* Set MIC2 Vref gate to normal */ + {} + };static struct coef_fw coef0233[] = {UPDATE_COEF (0x35 ,0 ,1 <<14 ),WRITE_COEF (0x06 ,0x2100 ),
@@ -4264,14 +4269,19 @@ static void alc_headset_mode_mic_in(stru };switch (codec->core.vendor_id) { -case 0x10ec0236 :case 0x10ec0255 : -case 0x10ec0256 :alc_write_coef_idx (codec,0x45 ,0xc489 );snd_hda_set_pin_ctl_cache (codec, hp_pin,0 );alc_process_coef_fw (codec, coef0255);snd_hda_set_pin_ctl_cache (codec, mic_pin,PIN_VREF50 );break ; +case 0x10ec0236 : +case 0x10ec0256 : +alc_write_coef_idx (codec,0x45 ,0xc489 ); +snd_hda_set_pin_ctl_cache (codec, hp_pin,0 ); +alc_process_coef_fw (codec, coef0256); +snd_hda_set_pin_ctl_cache (codec, mic_pin,PIN_VREF50 ); +break ;case 0x10ec0234 :case 0x10ec0274 :case 0x10ec0294 :
@@ -4353,6 +4363,14 @@ static void alc_headset_mode_default(str WRITE_COEF(0x49, 0x0049), {} }; +static struct coef_fw coef0256[] = { +WRITE_COEF (0x45 ,0xc489 ), +WRITE_COEFEX (0x57 ,0x03 ,0x0da3 ), +WRITE_COEF (0x49 ,0x0049 ), +UPDATE_COEFEX (0x57 ,0x05 ,1 <<14 ,0 ),/* Direct Drive HP Amp control(Set to verb control)*/ +WRITE_COEF (0x06 ,0x6100 ), + {} + };static struct coef_fw coef0233[] = {WRITE_COEF (0x06 ,0x2100 ),WRITE_COEF (0x32 ,0x4ea3 ),
@@ -4403,11 +4421,16 @@ static void alc_headset_mode_default(stralc_process_coef_fw (codec, alc225_pre_hsmode);alc_process_coef_fw (codec, coef0225);break ; -case 0x10ec0236 :case 0x10ec0255 : -case 0x10ec0256 :alc_process_coef_fw (codec, coef0255);break ; +case 0x10ec0236 : +case 0x10ec0256 : +alc_write_coef_idx (codec,0x1b ,0x0e4b ); +alc_write_coef_idx (codec,0x45 ,0xc089 ); +msleep (50 ); +alc_process_coef_fw (codec, coef0256); +break ;case 0x10ec0234 :case 0x10ec0274 :case 0x10ec0294 :
@@ -4451,8 +4474,7 @@ static void alc_headset_mode_ctia(struct };static struct coef_fw coef0256[] = {WRITE_COEF (0x45 ,0xd489 ),/* Set to CTIA type */ -WRITE_COEF (0x1b ,0x0c6b ), -WRITE_COEFEX (0x57 ,0x03 ,0x8ea6 ), +WRITE_COEF (0x1b ,0x0e6b ), {} };static struct coef_fw coef0233[] = {
@@ -4570,8 +4592,7 @@ static void alc_headset_mode_omtp(struct };static struct coef_fw coef0256[] = {WRITE_COEF (0x45 ,0xe489 ),/* Set to OMTP Type */ -WRITE_COEF (0x1b ,0x0c6b ), -WRITE_COEFEX (0x57 ,0x03 ,0x8ea6 ), +WRITE_COEF (0x1b ,0x0e6b ), {} };static struct coef_fw coef0233[] = {
@@ -4703,13 +4724,37 @@ static void alc_determine_headset_type(s };switch (codec->core.vendor_id) { -case 0x10ec0236 :case 0x10ec0255 : +alc_process_coef_fw (codec, coef0255); +msleep (300 ); + val =alc_read_coef_idx (codec,0x46 ); + is_ctia = (val &0x0070 ) ==0x0070 ; +break ; +case 0x10ec0236 :case 0x10ec0256 : +alc_write_coef_idx (codec,0x1b ,0x0e4b ); +alc_write_coef_idx (codec,0x06 ,0x6104 ); +alc_write_coefex_idx (codec,0x57 ,0x3 ,0x09a3 ); + +snd_hda_codec_write (codec,0x21 ,0 , +AC_VERB_SET_AMP_GAIN_MUTE ,AMP_OUT_MUTE ); +msleep (80 ); +snd_hda_codec_write (codec,0x21 ,0 , +AC_VERB_SET_PIN_WIDGET_CONTROL ,0x0 ); +alc_process_coef_fw (codec, coef0255);msleep (300 ); val =alc_read_coef_idx (codec,0x46 ); is_ctia = (val &0x0070 ) ==0x0070 ; + +alc_write_coefex_idx (codec,0x57 ,0x3 ,0x0da3 ); +alc_update_coefex_idx (codec,0x57 ,0x5 ,1 <<14 ,0 ); + +snd_hda_codec_write (codec,0x21 ,0 , +AC_VERB_SET_PIN_WIDGET_CONTROL ,PIN_OUT ); +msleep (80 ); +snd_hda_codec_write (codec,0x21 ,0 , +AC_VERB_SET_AMP_GAIN_MUTE ,AMP_OUT_UNMUTE );break ;case 0x10ec0234 :case 0x10ec0274 :
Greg Kroah-Hartman
maintainerPATCH 18/115 selinux: fix a missing-check bug in selinux_add_mnt_opt( )
In reply to Greg Kroah-HartmanFrom: Gen Zhang <[email protected]>
commit e2e0e09758a6f7597de0f9b819647addfb71b6bd upstream.
In selinux_add_mnt_opt(), 'val' is allocated by kmemdup_nul(). It returns NULL when fails. So 'val' should be checked. And 'mnt_opts' should be freed when error.
--- security/selinux/hooks.c | 19 ++++++++++++++----- 1 file changed, 14 insertions(+), 5 deletions(-)
security/selinux/hooks.c +14 -5
@@ -1048,15 +1048,24 @@ static int selinux_add_mnt_opt(const chaif (token == Opt_error)return -EINVAL ; -if (token != Opt_seclabel) +if (token != Opt_seclabel) { val =kmemdup_nul (val, len,GFP_KERNEL ); +if (!val) { + rc = -ENOMEM ; + goto free_opt; + } + } rc =selinux_add_opt (token, val, mnt_opts);if (unlikely (rc)) {kfree (val); -if (*mnt_opts) { -selinux_free_mnt_opts (*mnt_opts); - *mnt_opts =NULL ; - } + goto free_opt; + } +return rc; + +free_opt: +if (*mnt_opts) { +selinux_free_mnt_opts (*mnt_opts); + *mnt_opts =NULL ; }return rc; }
Greg Kroah-Hartman
maintainerPATCH 19/115 selinux: fix a missing-check bug in selinux_sb_eat_lsm_opts()
In reply to Greg Kroah-HartmanFrom: Gen Zhang <[email protected]>
commit fec6375320c6399c708fa9801f8cfbf950fee623 upstream.
In selinux_sb_eat_lsm_opts(), 'arg' is allocated by kmemdup_nul(). It returns NULL when fails. So 'arg' should be checked. And 'mnt_opts' should be freed when error.
--- security/selinux/hooks.c | 20 ++++++++++++++------ 1 file changed, 14 insertions(+), 6 deletions(-)
security/selinux/hooks.c +14 -6
@@ -2612,10 +2612,11 @@ static int selinux_sb_eat_lsm_opts(charchar *from = options;char *to = options;bool first = true; +int rc;while (1 ) {int len =opt_len (from); -int token, rc; +int token;char *arg =NULL ; token =match_opt_prefix (from, len, &arg);
@@ -2631,15 +2632,15 @@ static int selinux_sb_eat_lsm_opts(char *q++ = c; } arg =kmemdup_nul (arg, q - arg,GFP_KERNEL ); +if (!arg) { + rc = -ENOMEM ; + goto free_opt; + } } rc =selinux_add_opt (token, arg, mnt_opts);if (unlikely (rc)) {kfree (arg); -if (*mnt_opts) { -selinux_free_mnt_opts (*mnt_opts); - *mnt_opts =NULL ; - } -return rc; + goto free_opt; } }else {if (!first) {// copy with preceding comma
@@ -2657,6 +2658,13 @@ static int selinux_sb_eat_lsm_opts(char } *to ='\0' ;return 0 ; + +free_opt: +if (*mnt_opts) { +selinux_free_mnt_opts (*mnt_opts); + *mnt_opts =NULL ; + } +return rc; }static int selinux_sb_remount (struct super_block *sb,void *mnt_opts)
Greg Kroah-Hartman
maintainerPATCH 2/115 nouveau: Fix build with CONFIG_NOUVEAU_LEGACY_CTX_SUPPORT disabled
In reply to Greg Kroah-HartmanFrom: Thomas Backlund <[email protected]>
Not-entirely-upstream-sha1-but-equivalent: bed2dd8421 ("drm/ttm: Quick-test mmap offset in ttm_bo_mmap()")
Setting CONFIG_NOUVEAU_LEGACY_CTX_SUPPORT=n (added by commit: b30a43ac7132) causes the build to fail with:
ERROR: "drm_legacy_mmap" [drivers/gpu/drm/nouveau/nouveau.ko] undefined!
This does not happend upstream as the offending code got removed in:bed2dd8421 ("drm/ttm: Quick-test mmap offset in ttm_bo_mmap()")
Fix that by adding check for CONFIG_NOUVEAU_LEGACY_CTX_SUPPORT around the drm_legacy_mmap() call.
Also, as Sven Joachim pointed out, we need to make the check in CONFIG_NOUVEAU_LEGACY_CTX_SUPPORT=n case return -EINVAL as its done for basically all other gpu drivers, especially in upstream kernels drivers/gpu/drm/ttm/ttm_bo_vm.c as of the upstream commit bed2dd8421.
NOTE. This is a minimal stable-only fix for trees where b30a43ac7132 is backported as the build error affects nouveau only.
legacy contexts. (v3)")
--- drivers/gpu/drm/nouveau/nouveau_ttm.c | 4 ++++ 1 file changed, 4 insertions(+)
drivers/gpu/drm/nouveau/nouveau_ttm.c +4 -0
@@ -169,7 +169,11 @@ nouveau_ttm_mmap(struct file *filp, strustruct nouveau_drm *drm =nouveau_drm (file_priv->minor->dev); if (unlikely(vma->vm_pgoff < DRM_FILE_PAGE_OFFSET)) +#if defined(CONFIG_NOUVEAU_LEGACY_CTX_SUPPORT )return drm_legacy_mmap (filp, vma); +#else +return -EINVAL ; +#endif return ttm_bo_mmap (filp, vma, &drm->ttm.bdev); }
Greg Kroah-Hartman
maintainerPATCH 20/115 libata: Extend quirks for the ST1000LM024 drives with NOLPM quirk
In reply to Greg Kroah-HartmanFrom: Hans de Goede <[email protected]>
commit 31f6264e225fb92cf6f4b63031424f20797c297d upstream.
We've received a bugreport that using LPM with ST1000LM024 drives leads to system lockups. So it seems that these models are buggy in more then 1 way. Add NOLPM quirk to the existing quirks entry for BROKEN_FPDMA_AA.
--- drivers/ata/libata-core.c | 9 ++++++--- 1 file changed, 6 insertions(+), 3 deletions(-)
drivers/ata/libata-core.c +6 -3
@@ -4476,9 +4476,12 @@ static const struct ata_blacklist_entry {"ST3320[68]13AS" ,"SD1[5-9]" ,ATA_HORKAGE_NONCQ | ATA_HORKAGE_FIRMWARE_WARN }, -/* drives which fail FPDMA_AA activation (some may freeze afterwards) */ - { "ST1000LM024 HN-M101MBB", "2AR10001", ATA_HORKAGE_BROKEN_FPDMA_AA }, - { "ST1000LM024 HN-M101MBB", "2BA30001", ATA_HORKAGE_BROKEN_FPDMA_AA }, +/* drives which fail FPDMA_AA activation (some may freeze afterwards) +the ST disks also have LPM issues */ + { "ST1000LM024 HN-M101MBB", "2AR10001", ATA_HORKAGE_BROKEN_FPDMA_AA | + ATA_HORKAGE_NOLPM, }, + { "ST1000LM024 HN-M101MBB", "2BA30001", ATA_HORKAGE_BROKEN_FPDMA_AA | + ATA_HORKAGE_NOLPM, }, { "VB0250EAVER", "HPG7", ATA_HORKAGE_BROKEN_FPDMA_AA },/* Blacklist entries taken from Silicon Image 3124/3132
Greg Kroah-Hartman
maintainerPATCH 22/115 mm/list_lru.c: fix memory leak in __memcg_init_list_lru_node
In reply to Greg Kroah-HartmanFrom: Shakeel Butt <[email protected]>
commit 3510955b327176fd4cbab5baa75b449f077722a2 upstream.
Syzbot reported following memory leak:
ffffffffda RBX: 0000000000000003 RCX: 0000000000441f79
BUG: memory leak
unreferenced object 0xffff888114f26040 (size 32):
comm "syz-executor626", pid 7056, jiffies 4294948701 (age 39.410s)
hex dump (first 32 bytes):
40 60 f2 14 81 88 ff ff 40 60 f2 14 81 88 ff ff @`......@`......
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
backtrace:
slab_post_alloc_hook mm/slab.h:439 [inline]
slab_alloc mm/slab.c:3326 [inline]
kmem_cache_alloc_trace+0x13d/0x280 mm/slab.c:3553
kmalloc include/linux/slab.h:547 [inline]
__memcg_init_list_lru_node+0x58/0xf0 mm/list_lru.c:352
memcg_init_list_lru_node mm/list_lru.c:375 [inline]
memcg_init_list_lru mm/list_lru.c:459 [inline]
__list_lru_init+0x193/0x2a0 mm/list_lru.c:626
alloc_super+0x2e0/0x310 fs/super.c:269
sget_userns+0x94/0x2a0 fs/super.c:609
sget+0x8d/0xb0 fs/super.c:660
mount_nodev+0x31/0xb0 fs/super.c:1387
fuse_mount+0x2d/0x40 fs/fuse/inode.c:1236
legacy_get_tree+0x27/0x80 fs/fs_context.c:661
vfs_get_tree+0x2e/0x120 fs/super.c:1476
do_new_mount fs/namespace.c:2790 [inline]
do_mount+0x932/0xc50 fs/namespace.c:3110
ksys_mount+0xab/0x120 fs/namespace.c:3319
__do_sys_mount fs/namespace.c:3333 [inline]
__se_sys_mount fs/namespace.c:3330 [inline]
__x64_sys_mount+0x26/0x30 fs/namespace.c:3330
do_syscall_64+0x76/0x1a0 arch/x86/entry/common.c:301
entry_SYSCALL_64_after_hwframe+0x44/0xa9This is a simple off by one bug on the error path.
--- mm/list_lru.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
mm/list_lru.c +1 -1
@@ -353,7 +353,7 @@ static int __memcg_init_list_lru_node(st }return 0 ; fail: -__memcg_destroy_list_lru_node (memcg_lrus, begin, i -1 ); +__memcg_destroy_list_lru_node (memcg_lrus, begin, i);return -ENOMEM ; }
Greg Kroah-Hartman
maintainerPATCH 23/115 fs/ocfs2: fix race in ocfs2_dentry_attach_lock()
In reply to Greg Kroah-HartmanFrom: Wengang Wang <[email protected]>
commit be99ca2716972a712cde46092c54dee5e6192bf8 upstream.
ocfs2_dentry_attach_lock() can be executed in parallel threads against the same dentry. Make that race safe. The race is like this:
thread A thread B
(A1) enter ocfs2_dentry_attach_lock,
seeing dentry->d_fsdata is NULL,
and no alias found byocfs2_find_local_alias, so kmalloc
a new ocfs2_dentry_lock structure
to local variable "dl", dl1
.....
(B1) enter ocfs2_dentry_attach_lock, seeing dentry->d_fsdata is NULL, and no alias found by ocfs2_find_local_alias so kmalloc a new ocfs2_dentry_lock structure to local variable "dl", dl2.
......
(A2) set dentry->d_fsdata with dl1,
call ocfs2_dentry_lock() and increasedl1->dl_lockres.l_ro_holders to 1 on
success.
......
(B2) set dentry->d_fsdata with dl2
call ocfs2_dentry_lock() and increase
dl2->dl_lockres.l_ro_holders to 1 on
success.
......(A3) call ocfs2_dentry_unlock()
and decreasedl2->dl_lockres.l_ro_holders to 0
on success.
....
(B3) call ocfs2_dentry_unlock(),
decreasing
dl2->dl_lockres.l_ro_holders, but
see it's zero now, panic--- fs/ocfs2/dcache.c | 12 ++++++++++++ 1 file changed, 12 insertions(+)
fs/ocfs2/dcache.c +12 -0
@@ -310,6 +310,18 @@ int ocfs2_dentry_attach_lock(struct dent out_attach:spin_lock (&dentry_attach_lock); +if (unlikely (dentry->d_fsdata && !alias)) { +/* d_fsdata is set by a racing thread which is doing +* the same thing as this thread is doing. Leave the racing +* thread going ahead and we return here. +*/ +spin_unlock (&dentry_attach_lock); +iput (dl->dl_inode); +ocfs2_lock_res_free (&dl->dl_lockres); +kfree (dl); +return 0 ; + } + dentry->d_fsdata = dl; dl->dl_count++;spin_unlock (&dentry_attach_lock);
Greg Kroah-Hartman
maintainerPATCH 24/115 mm/vmscan.c: fix trying to reclaim unevictable LRU page
In reply to Greg Kroah-HartmanFrom: Minchan Kim <[email protected]>
commit a58f2cef26e1ca44182c8b22f4f4395e702a5795 upstream.
There was the below bug report from Wu Fangsuo.
On the CMA allocation path, isolate_migratepages_range() could isolate unevictable LRU pages and reclaim_clean_page_from_list() can try to reclaim them if they are clean file-backed pages.
page:ffffffbf02f33b40 count:86 mapcount:84 mapping:ffffffc08fa7a810 index:0x24
flags: 0x19040c(referenced|uptodate|arch_1|mappedtodisk|unevictable|mlocked)
raw: 000000000019040c ffffffc08fa7a810 0000000000000024 0000005600000053
raw: ffffffc009b05b20 ffffffc009b05b20 0000000000000000 ffffffc09bf3ee80
page dumped because: VM_BUG_ON_PAGE(PageLRU(page) || PageUnevictable(page))
page->mem_cgroup:ffffffc09bf3ee80
------------[ cut here ]------------
kernel BUG at /home/build/farmland/adroid9.0/kernel/linux/mm/vmscan.c:1350!
Internal error: Oops - BUG: 0 [#1] PREEMPT SMP
Modules linked in:
CPU: 0 PID: 7125 Comm: syz-executor Tainted: G S 4.14.81 #3
Hardware name: ASR AQUILAC EVB (DT)
task: ffffffc00a54cd00 task.stack: ffffffc009b00000
PC is at shrink_page_list+0x1998/0x3240
LR is at shrink_page_list+0x1998/0x3240
pc : [<ffffff90083a2158>] lr : [<ffffff90083a2158>] pstate: 60400045
sp : ffffffc009b05940
..
shrink_page_list+0x1998/0x3240
reclaim_clean_pages_from_list+0x3c0/0x4f0
alloc_contig_range+0x3bc/0x650
cma_alloc+0x214/0x668
ion_cma_allocate+0x98/0x1d8
ion_alloc+0x200/0x7e0
ion_ioctl+0x18c/0x378
do_vfs_ioctl+0x17c/0x1780
SyS_ioctl+0xac/0xc0Wu found it's due to commit ad6b67041a45 ("mm: remove SWAP_MLOCK in ttu"). Before that, unevictable pages go to cull_mlocked so that we can't reach the VM_BUG_ON_PAGE line.
To fix the issue, this patch filters out unevictable LRU pages from the reclaim_clean_pages_from_list in CMA.
--- mm/vmscan.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
mm/vmscan.c +1 -1
@@ -1502,7 +1502,7 @@ unsigned long reclaim_clean_pages_from_llist_for_each_entry_safe (page, next, page_list, lru) {if (page_is_file_cache (page) && !PageDirty (page) && - !__PageMovable (page)) { + !__PageMovable (page) && !PageUnevictable (page)) {ClearPageActive (page);list_move (&page->lru, &clean_pages); }
Greg Kroah-Hartman
maintainerPATCH 26/115 ptrace: restore smp_rmb() in __ptrace_may_access()
In reply to Greg Kroah-HartmanFrom: Jann Horn <[email protected]>
commit f6581f5b55141a95657ef5742cf6a6bfa20a109f upstream.
Restore the read memory barrier in __ptrace_may_access() that was deleted a couple years ago. Also add comments on this barrier and the one it pairs with to explain why they're there (as far as I understand).
--- kernel/cred.c | 9 +++++++++ kernel/ptrace.c | 10 ++++++++++ 2 files changed, 19 insertions(+)
kernel/cred.c +9 -0
@@ -450,6 +450,15 @@ int commit_creds(struct cred *new)if (task->mm)set_dumpable (task->mm, suid_dumpable); task->pdeath_signal =0 ; +/* +* If a task drops privileges and becomes nondumpable, +* the dumpability change must become visible before +* the credential change; otherwise, a __ptrace_may_access() +* racing with this change may be able to attach to a task it +* shouldn't be able to attach to (as if the task had dropped +* privileges without becoming nondumpable). +* Pairs with a read barrier in __ptrace_may_access(). +*/ smp_wmb (); }
kernel/ptrace.c +10 -0
@@ -323,6 +323,16 @@ static int __ptrace_may_access(struct tareturn -EPERM ; ok:rcu_read_unlock (); +/* +* If a task drops privileges and becomes nondumpable (through a syscall +* like setresuid()) while we are trying to access it, we must ensure +* that the dumpability is read after the credentials; otherwise, +* we may be able to attach to a task that we shouldn't be able to +* attach to (as if the task had dropped privileges without becoming +* nondumpable). +* Pairs with a write barrier in commit_creds(). +*/ +smp_rmb (); mm = task->mm; if (mm && ((get_dumpable(mm) != SUID_DUMP_USER) &&
Greg Kroah-Hartman
maintainerPATCH 25/115 signal/ptrace: Dont leak unitialized kernel memory with PTRACE_PEEK_SIGINFO
In reply to Greg Kroah-HartmanFrom: Eric W. Biederman <[email protected]>
commit f6e2aa91a46d2bc79fce9b93a988dbe7655c90c0 upstream.
Recently syzbot in conjunction with KMSAN reported that ptrace_peek_siginfo can copy an uninitialized siginfo to userspace. Inspecting ptrace_peek_siginfo confirms this.
The problem is that off when initialized from args.off can be initialized to a negaive value. At which point the "if (off >= 0)" test to see if off became negative fails because off started off negative.
Prevent the core problem by adding a variable found that is only true if a siginfo is found and copied to a temporary in preparation for being copied to userspace.
Prevent args.off from being truncated when being assigned to off by testing that off is <= the maximum possible value of off. Convert off to an unsigned long so that we should not have to truncate args.off, we have well defined overflow behavior so if we add another check we won't risk fighting undefined compiler behavior, and so that we have a type whose maximum value is easy to test for.
--- kernel/ptrace.c | 10 ++++++++-- 1 file changed, 8 insertions(+), 2 deletions(-)
kernel/ptrace.c +8 -2
@@ -704,6 +704,10 @@ static int ptrace_peek_siginfo(struct taif (arg.nr <0 )return -EINVAL ; +/* Ensure arg.off fits in an unsigned long */ +if (arg.off >ULONG_MAX ) +return 0 ; +if (arg.flags &PTRACE_PEEKSIGINFO_SHARED ) pending = &child->signal->shared_pending;else
@@ -711,18 +715,20 @@ static int ptrace_peek_siginfo(struct tafor (i =0 ; i < arg.nr; ) {kernel_siginfo_t info; -s32 off = arg.off + i; +unsigned long off = arg.off + i; +bool found = false;spin_lock_irq (&child->sighand->siglock);list_for_each_entry (q, &pending->list, list) {if (!off--) { + found = true;copy_siginfo (&info, &q->info);break ; } }spin_unlock_irq (&child->sighand->siglock); -if (off >=0 )/* beyond the end of the list */ +if (!found)/* beyond the end of the list */ break ;#ifdef CONFIG_COMPAT
Greg Kroah-Hartman
maintainerPATCH 27/115 media: dvb: warning about dvb frequency limits produces too much noise
In reply to Greg Kroah-HartmanFrom: Sean Young <[email protected]>
commit eb96e57b913ff668b8b804178cdc509f9b3d4472 upstream.
This can be a debug message. Favour dev_dbg() over dprintk() as this is already used much more than dprintk().
dvb_frontend: dvb_frontend_get_frequency_limits: frequency interval: tuner: 45000000...860000000, frontend: 44250000...867250000
--- drivers/media/dvb-core/dvb_frontend.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/media/dvb-core/dvb_frontend.c +1 -1
@@ -917,7 +917,7 @@ static void dvb_frontend_get_frequency_l"DVB: adapter %i frontend %u frequency limits undefined - fix the driver\n" , fe->dvb->num, fe->id); -dprintk ("frequency interval: tuner: %u...%u, frontend: %u...%u" , +dev_dbg (fe->dvb->device,"frequency interval: tuner: %u...%u, frontend: %u...%u" , tuner_min, tuner_max, frontend_min, frontend_max);/* If the standard is for satellite, convert frequencies to kHz */
Greg Kroah-Hartman
maintainerPATCH 28/115 iommu/arm-smmu: Avoid constant zero in TLBI writes
In reply to Greg Kroah-HartmanFrom: Robin Murphy <[email protected]>
commit 4e4abae311e4b44aaf61f18a826fd7136037f199 upstream.
Apparently, some Qualcomm arm64 platforms which appear to expose their SMMU global register space are still, in fact, using a hypervisor to mediate it by trapping and emulating register accesses. Sadly, some deployed versions of said trapping code have bugs wherein they go horribly wrong for stores using r31 (i.e. XZR/WZR) as the source register.
While this can be mitigated for GCC today by tweaking the constraints for the implementation of writel_relaxed(), to avoid any potential arms race with future compilers more aggressively optimising register allocation, the simple way is to just remove all the problematic constant zeros. For the write-only TLB operations, the actual value is irrelevant anyway and any old nearby variable will provide a suitable GPR to encode. The one point at which we really do need a zero to clear a context bank happens before any of the TLB maintenance where crashes have been reported, so is apparently not a problem... :/
--- drivers/iommu/arm-smmu.c | 15 ++++++++++++--- 1 file changed, 12 insertions(+), 3 deletions(-)
drivers/iommu/arm-smmu.c +12 -3
@@ -59,6 +59,15 @@#include "arm-smmu-regs.h" +/* +* Apparently, some Qualcomm arm64 platforms which appear to expose their SMMU +* global register space are still, in fact, using a hypervisor to mediate it +* by trapping and emulating register accesses. Sadly, some deployed versions +* of said trapping code have bugs wherein they go horribly wrong for stores +* using r31 (i.e. XZR/WZR) as the source register. +*/ +#define QCOM_DUMMY_VAL -1 +#define ARM_MMU500_ACTLR_CPRE (1 << 1)#define ARM_MMU500_ACR_CACHE_LOCK (1 << 26)
@@ -422,7 +431,7 @@ static void __arm_smmu_tlb_sync(struct a {unsigned int spin_cnt, delay; -writel_relaxed (0 , sync); +writel_relaxed (QCOM_DUMMY_VAL , sync);for (delay =1 ; delay <TLB_LOOP_TIMEOUT ; delay *=2 ) {for (spin_cnt =TLB_SPIN_COUNT ; spin_cnt >0 ; spin_cnt--) {if (!(readl_relaxed (status) & sTLBGSTATUS_GSACTIVE))
@@ -1760,8 +1769,8 @@ static void arm_smmu_device_reset(struct }/* Invalidate the TLB, just in case */ -writel_relaxed (0 , gr0_base +ARM_SMMU_GR0_TLBIALLH ); -writel_relaxed (0 , gr0_base +ARM_SMMU_GR0_TLBIALLNSNH ); +writel_relaxed (QCOM_DUMMY_VAL , gr0_base +ARM_SMMU_GR0_TLBIALLH ); +writel_relaxed (QCOM_DUMMY_VAL , gr0_base +ARM_SMMU_GR0_TLBIALLNSNH ); reg =readl_relaxed (ARM_SMMU_GR0_NS (smmu) + ARM_SMMU_GR0_sCR0);
Greg Kroah-Hartman
maintainerPATCH 3/115 HID: input: make sure the wheel high resolution multiplier is set
In reply to Greg Kroah-HartmanFrom: Benjamin Tissoires <[email protected]>
commit d43c17ead879ba7c076dc2f5fd80cd76047c9ff4 upstream.
Some old mice have a tendency to not accept the high resolution multiplier. They reply with a -EPIPE which was previously ignored.
Force the call to resolution multiplier to be synchronous and actually check for the answer. If this fails, consider the mouse like a normal one.
high-resolution scrolling")
--- drivers/hid/hid-core.c | 7 ++-- drivers/hid/hid-input.c | 81 +++++++++++++++++++++++++++++------------------- include/linux/hid.h | 2 - 3 files changed, 56 insertions(+), 34 deletions(-)
drivers/hid/hid-core.c +5 -2
@@ -1636,7 +1636,7 @@ static struct hid_report *hid_get_report* Implement a generic .request() callback, using .raw_request() * DO NOT USE in hid drivers directly, but through hid_hw_request instead. */ -void __hid_request (struct hid_device *hid,struct hid_report *report, +int __hid_request (struct hid_device *hid,struct hid_report *report,int reqtype) {char *buf;
@@ -1645,7 +1645,7 @@ void __hid_request(struct hid_device *hi buf =hid_alloc_report_buf (report,GFP_KERNEL );if (!buf) -return ; +return -ENOMEM ; len =hid_report_len (report);
@@ -1662,8 +1662,11 @@ void __hid_request(struct hid_device *hiif (reqtype ==HID_REQ_GET_REPORT )hid_input_report (hid, report->type, buf, ret,0 ); + ret =0 ; + out:kfree (buf); +return ret; }EXPORT_SYMBOL_GPL (__hid_request);
drivers/hid/hid-input.c +50 -31
102 lines not on this page · raw message
include/linux/hid.h +1 -1
@@ -894,7 +894,7 @@ struct hid_field *hidinput_get_led_fieldunsigned int hidinput_count_leds (struct hid_device *hid);__s32 hidinput_calc_abs_res (const struct hid_field *field,__u16 code);void hid_output_report (struct hid_report *report,__u8 *data); -void __hid_request (struct hid_device *hid,struct hid_report *rep,int reqtype); +int __hid_request (struct hid_device *hid,struct hid_report *rep,int reqtype);u8 *hid_alloc_report_buf (struct hid_report *report,gfp_t flags);struct hid_device *hid_allocate_device (void ); struct hid_report *hid_register_report(struct hid_device *device,
Greg Kroah-Hartman
maintainerPATCH 30/115 i2c: acorn: fix i2c warning
In reply to Greg Kroah-HartmanFrom: Russell King <[email protected]>
commit ca21f851cc9643af049226d57fabc3c883ea648e upstream.
The Acorn i2c driver (for RiscPC) triggers the "i2c adapter has no name" warning in the I2C core driver, resulting in the RTC being inaccessible. Fix this.
--- drivers/i2c/busses/i2c-acorn.c | 1 + 1 file changed, 1 insertion(+)
drivers/i2c/busses/i2c-acorn.c +1 -0
@@ -81,6 +81,7 @@ static struct i2c_algo_bit_data ioc_datastatic struct i2c_adapter ioc_ops = { .nr =0 , + .name ="ioc" , .algo_data = &ioc_data, };
Greg Kroah-Hartman
maintainerPATCH 32/115 bcache: only set BCACHE_DEV_WB_RUNNING when cached device attached
In reply to Greg Kroah-HartmanFrom: Coly Li <[email protected]>
commit 1f0ffa67349c56ea54c03ccfd1e073c990e7411e upstream.
When people set a writeback percent via sysfs file,
/sys/block/bcache<N>/bcache/writeback_percent
current code directly sets BCACHE_DEV_WB_RUNNING to dc->disk.flags and schedules kworker dc->writeback_rate_update.
If there is no cache set attached to, the writeback kernel thread is not running indeed, running dc->writeback_rate_update does not make sense and may cause NULL pointer deference when reference cache set pointer inside update_writeback_rate().
This patch checks whether the cache set point (dc->disk.c) is NULL in sysfs interface handler, and only set BCACHE_DEV_WB_RUNNING and schedule dc->writeback_rate_update when dc->disk.c is not NULL (it means the cache device is attached to a cache set).
This problem might be introduced from initial bcache commit, but commit 3fd47bfe55b0 ("bcache: stop dc->writeback_rate_update properly") changes part of the original code piece, so I add 'Fixes: 3fd47bfe55b0' to indicate from which commit this patch can be applied.
--- drivers/md/bcache/sysfs.c | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-)
drivers/md/bcache/sysfs.c +6 -1
@@ -431,8 +431,13 @@ STORE(bch_cached_dev)bch_writeback_queue (dc); } +/* +* Only set BCACHE_DEV_WB_RUNNING when cached device attached to +* a cache set, otherwise it doesn't make sense. +*/ if (attr == &sysfs_writeback_percent) -if (!test_and_set_bit (BCACHE_DEV_WB_RUNNING , &dc->disk.flags)) +if ((dc->disk.c !=NULL ) && + (!test_and_set_bit (BCACHE_DEV_WB_RUNNING , &dc->disk.flags)))schedule_delayed_work (&dc->writeback_rate_update, dc->writeback_rate_update_seconds *HZ );
Greg Kroah-Hartman
maintainerPATCH 33/115 cgroup: Use css_tryget() instead of css_tryget_online() in task_get_css()
In reply to Greg Kroah-HartmanFrom: Tejun Heo <[email protected]>
commit 18fa84a2db0e15b02baa5d94bdb5bd509175d2f6 upstream.
A PF_EXITING task can stay associated with an offline css. If such task calls task_get_css(), it can get stuck indefinitely. This can be triggered by BSD process accounting which writes to a file with PF_EXITING set when racing against memcg disable as in the backtrace at the end.
After this change, task_get_css() may return a css which was already offline when the function was called. None of the existing users are affected by this change.
INFO: rcu_sched self-detected stall on CPU INFO: rcu_sched detected stalls on CPUs/tasks: ... NMI backtrace for cpu 0 ... Call Trace: <IRQ> dump_stack+0x46/0x68 nmi_cpu_backtrace.cold.2+0x13/0x57 nmi_trigger_cpumask_backtrace+0xba/0xca rcu_dump_cpu_stacks+0x9e/0xce rcu_check_callbacks.cold.74+0x2af/0x433 update_process_times+0x28/0x60 tick_sched_timer+0x34/0x70 __hrtimer_run_queues+0xee/0x250 hrtimer_interrupt+0xf4/0x210 smp_apic_timer_interrupt+0x56/0x110 apic_timer_interrupt+0xf/0x20 </IRQ> RIP: 0010:balance_dirty_pages_ratelimited+0x28f/0x3d0 ... btrfs_file_write_iter+0x31b/0x563 __vfs_write+0xfa/0x140 __kernel_write+0x4f/0x100 do_acct_process+0x495/0x580 acct_process+0xb9/0xdb do_exit+0x748/0xa00 do_group_exit+0x3a/0xa0 get_signal+0x254/0x560 do_signal+0x23/0x5c0 exit_to_usermode_loop+0x5d/0xa0 prepare_exit_to_usermode+0x53/0x80 retint_user+0x8/0x8
--- include/linux/cgroup.h | 10 ++++++++-- 1 file changed, 8 insertions(+), 2 deletions(-)
include/linux/cgroup.h +8 -2
@@ -487,7 +487,7 @@ static inline struct cgroup_subsys_state* * Find the css for the (@task, @subsys_id) combination, increment a * reference on and return it. This function is guaranteed to return a -* valid css. +* valid css. The returned css may already have been offlined. */ static inline struct cgroup_subsys_state *task_get_css (struct task_struct *task,int subsys_id)
@@ -497,7 +497,13 @@ task_get_css(struct task_struct *task, ircu_read_lock ();while (true) { css =task_css (task, subsys_id); -if (likely (css_tryget_online (css))) +/* +* Can't use css_tryget_online() here. A task which has +* PF_EXITING set may stay associated with an offline css. +* If such task calls this function, css_tryget_online() +* will keep failing. +*/ +if (likely (css_tryget (css)))break ;cpu_relax (); }
Greg Kroah-Hartman
maintainerPATCH 34/115 ASoC: cs42xx8: Add regcache mask dirty
In reply to Greg Kroah-HartmanFrom: S.j. Wang <[email protected]>
commit ad6eecbfc01c987e0253371f274c3872042e4350 upstream.
Add regcache_mark_dirty before regcache_sync for power of codec may be lost at suspend, then all the register need to be reconfigured.
support for CS42448/CS42888")
--- sound/soc/codecs/cs42xx8.c | 1 + 1 file changed, 1 insertion(+)
sound/soc/codecs/cs42xx8.c +1 -0
@@ -558,6 +558,7 @@ static int cs42xx8_runtime_resume(structmsleep (5 );regcache_cache_only (cs42xx8->regmap, false); +regcache_mark_dirty (cs42xx8->regmap); ret =regcache_sync (cs42xx8->regmap);if (ret) {
Greg Kroah-Hartman
maintainerPATCH 35/115 ASoC: fsl_asrc: Fix the issue about unsupported rate
In reply to Greg Kroah-HartmanFrom: S.j. Wang <[email protected]>
commit b06c58c2a1eed571ea2a6640fdb85b7b00196b1e upstream.
When the output sample rate is [8kHz, 30kHz], the limitation of the supported ratio range is [1/24, 8]. In the driver we use (8kHz, 30kHz) instead of [8kHz, 30kHz].
So this patch is to fix this issue and the potential rounding issue with divider.
output sample rate")
--- sound/soc/fsl/fsl_asrc.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
sound/soc/fsl/fsl_asrc.c +2 -2
@@ -282,8 +282,8 @@ static int fsl_asrc_config_pair(struct freturn -EINVAL ; } -if ((outrate >8000 && outrate <30000 ) && - (outrate/inrate >24 || inrate/outrate >8 )) { +if ((outrate >=8000 && outrate <=30000 ) && + (outrate >24 * inrate || inrate >8 * outrate)) {pair_err ("exceed supported ratio range [1/24, 8] for \ inrate/outrate: %d/%d\n" , inrate, outrate);return -EINVAL ;
Greg Kroah-Hartman
maintainerPATCH 36/115 ASoC: soc-core: fixup references at soc_cleanup_card_resources()
In reply to Greg Kroah-HartmanFrom: Kuninori Morimoto <[email protected]>
commit 29040d1ac569606fece70966179de272cfc0d4db upstream.
commit 53e947a0e1f7 ("ASoC: soc-core: merge card resources cleanup method") merged cleanup method of snd_soc_instantiate_card() and soc_cleanup_card_resources().
But, after this commit, if user uses unbind/bind to Component factor drivers, Kernel might indicates refcount error at soc_cleanup_card_resources().
The 1st reason is card->snd_card is still exist even though snd_card_free() was called, but it is already cleaned. We need to set NULL to it.
2nd is card->dapm and card create debugfs, but its dentry is still exist even though it was removed. We need to set NULL to it.
--- sound/soc/soc-core.c | 7 ++++++- sound/soc/soc-dapm.c | 3 +++ 2 files changed, 9 insertions(+), 1 deletion(-)
sound/soc/soc-core.c +6 -1
@@ -228,7 +228,10 @@ static void soc_init_card_debugfs(structstatic void soc_cleanup_card_debugfs (struct snd_soc_card *card) { +if (!card->debugfs_card_root) +return ;debugfs_remove_recursive (card->debugfs_card_root); + card->debugfs_card_root =NULL ; }static void snd_soc_debugfs_init (void )
@@ -2034,8 +2037,10 @@ static void soc_check_tplg_fes(struct snstatic int soc_cleanup_card_resources (struct snd_soc_card *card) {/* free the ALSA card at first; this syncs with pending operations */ -if (card->snd_card) +if (card->snd_card) {snd_card_free (card->snd_card); + card->snd_card =NULL ; + }/* remove and free each DAI */ soc_remove_dai_links (card);
sound/soc/soc-dapm.c +3 -0
@@ -2192,7 +2192,10 @@ static void dapm_debugfs_add_widget(strustatic void dapm_debugfs_cleanup (struct snd_soc_dapm_context *dapm) { +if (!dapm->debugfs_dapm) +return ;debugfs_remove_recursive (dapm->debugfs_dapm); + dapm->debugfs_dapm =NULL ; }#else
Greg Kroah-Hartman
maintainerPATCH 37/115 drm/amdgpu/{uvd,vcn}: fetch rings read_ptr after alloc
In reply to Greg Kroah-HartmanFrom: Shirish S <[email protected]>
commit 517b91f4cde3043d77b2178548473e8545ef07cb upstream.
[What]
readptr read always returns zero, since most likely these blocks are either power or clock gated.
[How]
fetch rptr after amdgpu_ring_alloc() which informs the power management code that the block is about to be used and hence the gating is turned off.
--- drivers/gpu/drm/amd/amdgpu/amdgpu_vcn.c | 4 +++- drivers/gpu/drm/amd/amdgpu/uvd_v6_0.c | 5 ++++- drivers/gpu/drm/amd/amdgpu/uvd_v7_0.c | 5 ++++- 3 files changed, 11 insertions(+), 3 deletions(-)
drivers/gpu/drm/amd/amdgpu/amdgpu_vcn.c +3 -1
@@ -594,7 +594,7 @@ error:int amdgpu_vcn_enc_ring_test_ring (struct amdgpu_ring *ring) {struct amdgpu_device *adev = ring->adev; -uint32_t rptr =amdgpu_ring_get_rptr (ring); +uint32_t rptr;unsigned i;int r;
@@ -602,6 +602,8 @@ int amdgpu_vcn_enc_ring_test_ring(structif (r)return r; + rptr =amdgpu_ring_get_rptr (ring); +amdgpu_ring_write (ring,VCN_ENC_CMD_END );amdgpu_ring_commit (ring);
drivers/gpu/drm/amd/amdgpu/uvd_v6_0.c +4 -1
@@ -170,13 +170,16 @@ static void uvd_v6_0_enc_ring_set_wptr(sstatic int uvd_v6_0_enc_ring_test_ring (struct amdgpu_ring *ring) {struct amdgpu_device *adev = ring->adev; -uint32_t rptr =amdgpu_ring_get_rptr (ring); +uint32_t rptr;unsigned i;int r; r =amdgpu_ring_alloc (ring,16 );if (r)return r; + + rptr =amdgpu_ring_get_rptr (ring); +amdgpu_ring_write (ring,HEVC_ENC_CMD_END );amdgpu_ring_commit (ring);
drivers/gpu/drm/amd/amdgpu/uvd_v7_0.c +4 -1
@@ -175,7 +175,7 @@ static void uvd_v7_0_enc_ring_set_wptr(sstatic int uvd_v7_0_enc_ring_test_ring (struct amdgpu_ring *ring) {struct amdgpu_device *adev = ring->adev; -uint32_t rptr =amdgpu_ring_get_rptr (ring); +uint32_t rptr;unsigned i;int r;
@@ -185,6 +185,9 @@ static int uvd_v7_0_enc_ring_test_ring(s r =amdgpu_ring_alloc (ring,16 );if (r)return r; + + rptr =amdgpu_ring_get_rptr (ring); +amdgpu_ring_write (ring,HEVC_ENC_CMD_END );amdgpu_ring_commit (ring);
Greg Kroah-Hartman
maintainerPATCH 38/115 drm/i915/sdvo: Implement proper HDMI audio support for SDVO
In reply to Greg Kroah-HartmanFrom: Ville Syrjälä <[email protected]>
commit d74408f528261f900dddb9778f61b5c5a7a6249c upstream.
Our SDVO audio support is pretty bogus. We can't push audio over the SDVO bus, so trying to enable audio in the SDVO control register doesn't do anything. In fact it looks like the SDVO encoder will always mix in the audio coming over HDA, and there's no (at least documented) way to disable that from our side. So HDMI audio does work currently on gen4 but only by luck really. On gen3 it got broken by the referenced commit. And what has always been missing on every platform is the ELD.
To pass the ELD to the audio driver we need to write it to magic buffer in the SDVO encoder hardware which then gets pulled out via HDA in the other end. Ie. pretty much the same thing we had for native HDMI before we started to just pass the ELD between the drivers. This sort of explains why we even have that silly hardware buffer with native HDMI.
$ cat /proc/asound/card0/eld#1.0 -monitor_present 0 -eld_valid 0 +monitor_present 1 +eld_valid 1 +monitor_name LG TV +connection_type HDMI +...
This also fixes our state readout since we can now query the SDVO encoder about the state of the "ELD valid" and "presence detect" bits. As mentioned those don't actually control whether audio gets sent over the HDMI cable, but it's the best we can do. And with the state checker appeased we can re-enable HDMI audio for gen3.
Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=108976
--- drivers/gpu/drm/i915/intel_sdvo.c | 58 ++++++++++++++++++++++++++------- drivers/gpu/drm/i915/intel_sdvo_regs.h | 3 + 2 files changed, 50 insertions(+), 11 deletions(-)
drivers/gpu/drm/i915/intel_sdvo.c +47 -11
@@ -909,6 +909,13 @@ static bool intel_sdvo_set_colorimetry(sreturn intel_sdvo_set_value (intel_sdvo,SDVO_CMD_SET_COLORIMETRY , &mode,1 ); } +static bool intel_sdvo_set_audio_state (struct intel_sdvo *intel_sdvo, +u8 audio_state) +{ +return intel_sdvo_set_value (intel_sdvo,SDVO_CMD_SET_AUDIO_STAT , + &audio_state,1 ); +} +#if 0 static void intel_sdvo_dump_hdmi_buf (struct intel_sdvo *intel_sdvo) {
@@ -1366,11 +1373,6 @@ static void intel_sdvo_pre_enable(structelse sdvox |=SDVO_PIPE_SEL (crtc->pipe); -if (crtc_state->has_audio) { -WARN_ON_ONCE (INTEL_GEN (dev_priv) <4 ); - sdvox |=SDVO_AUDIO_ENABLE ; - } -if (INTEL_GEN (dev_priv) >=4 ) {/* done in crtc_mode_set as the dpll_md reg must be written early */ } else if (IS_I945G(dev_priv) || IS_I945GM(dev_priv) ||
@@ -1510,8 +1512,13 @@ static void intel_sdvo_get_config(structif (sdvox &HDMI_COLOR_RANGE_16_235 ) pipe_config->limited_color_range = true; -if (sdvox &SDVO_AUDIO_ENABLE ) - pipe_config->has_audio = true; +if (intel_sdvo_get_value (intel_sdvo,SDVO_CMD_GET_AUDIO_STAT , + &val,1 )) { +u8 mask =SDVO_AUDIO_ELD_VALID |SDVO_AUDIO_PRESENCE_DETECT ; + +if ((val & mask) == mask) + pipe_config->has_audio = true; + }if (intel_sdvo_get_value (intel_sdvo,SDVO_CMD_GET_ENCODE , &val,1 )) {
@@ -1524,6 +1531,32 @@ static void intel_sdvo_get_config(struct pipe_config->pixel_multiplier, encoder_pixel_multiplier); } +static void intel_sdvo_disable_audio (struct intel_sdvo *intel_sdvo) +{ +intel_sdvo_set_audio_state (intel_sdvo,0 ); +} + +static void intel_sdvo_enable_audio (struct intel_sdvo *intel_sdvo, +const struct intel_crtc_state *crtc_state, +const struct drm_connector_state *conn_state) +{ +const struct drm_display_mode *adjusted_mode = + &crtc_state->base.adjusted_mode; +struct drm_connector *connector = conn_state->connector; +u8 *eld = connector->eld; + + eld[6 ] =drm_av_sync_delay (connector, adjusted_mode) /2 ; + +intel_sdvo_set_audio_state (intel_sdvo,0 ); + +intel_sdvo_write_infoframe (intel_sdvo,SDVO_HBUF_INDEX_ELD , +SDVO_HBUF_TX_DISABLED , + eld,drm_eld_size (eld)); + +intel_sdvo_set_audio_state (intel_sdvo,SDVO_AUDIO_ELD_VALID | +SDVO_AUDIO_PRESENCE_DETECT ); +} +static void intel_disable_sdvo (struct intel_encoder *encoder,const struct intel_crtc_state *old_crtc_state,const struct drm_connector_state *conn_state)
@@ -1533,6 +1566,9 @@ static void intel_disable_sdvo(struct instruct intel_crtc *crtc =to_intel_crtc (old_crtc_state->base.crtc);u32 temp; +if (old_crtc_state->has_audio) +intel_sdvo_disable_audio (intel_sdvo); +intel_sdvo_set_active_outputs (intel_sdvo,0 );if (0 ) intel_sdvo_set_encoder_power_state(intel_sdvo,
@@ -1618,6 +1654,9 @@ static void intel_enable_sdvo(struct intintel_sdvo_set_encoder_power_state (intel_sdvo,DRM_MODE_DPMS_ON );intel_sdvo_set_active_outputs (intel_sdvo, intel_sdvo->attached_output); + +if (pipe_config->has_audio) +intel_sdvo_enable_audio (intel_sdvo, pipe_config, conn_state); } static enum drm_mode_status
@@ -2480,7 +2519,6 @@ static bool intel_sdvo_dvi_init(struct intel_sdvo *intel_sdvo, int device) {struct drm_encoder *encoder = &intel_sdvo->base.base; -struct drm_i915_private *dev_priv =to_i915 (encoder->dev);struct drm_connector *connector;struct intel_encoder *intel_encoder =to_intel_encoder (encoder);struct intel_connector *intel_connector;
@@ -2517,9 +2555,7 @@ intel_sdvo_dvi_init(struct intel_sdvo *i encoder->encoder_type =DRM_MODE_ENCODER_TMDS ; connector->connector_type =DRM_MODE_CONNECTOR_DVID ; -/* gen3 doesn't do the hdmi bits in the SDVO register */ -if (INTEL_GEN (dev_priv) >=4 && -intel_sdvo_is_hdmi_connector (intel_sdvo, device)) { +if (intel_sdvo_is_hdmi_connector (intel_sdvo, device)) { connector->connector_type =DRM_MODE_CONNECTOR_HDMIA ; intel_sdvo_connector->is_hdmi = true; }
drivers/gpu/drm/i915/intel_sdvo_regs.h +3 -0
@@ -707,6 +707,9 @@ struct intel_sdvo_enhancements_arg {#define SDVO_CMD_GET_AUDIO_ENCRYPT_PREFER 0x90#define SDVO_CMD_SET_AUDIO_STAT 0x91#define SDVO_CMD_GET_AUDIO_STAT 0x92 +#define SDVO_AUDIO_ELD_VALID (1 << 0) +#define SDVO_AUDIO_PRESENCE_DETECT (1 << 1) +#define SDVO_AUDIO_CP_READY (1 << 2)#define SDVO_CMD_SET_HBUF_INDEX 0x93#define SDVO_HBUF_INDEX_ELD 0#define SDVO_HBUF_INDEX_AVI_IF 1
Greg Kroah-Hartman
maintainerPATCH 4/115 HID: input: fix assignment of .value
In reply to Greg Kroah-HartmanFrom: Benjamin Tissoires <[email protected]>
commit 39b3c3a5fbc5d744114e497d35bf0c12f798c134 upstream.
The value field is actually an array of .maxfield. We should assign the correct number to the correct usage.
Not that we never encounter a device that requires this ATM, but better have the proper code path.
high-resolution scrolling")
--- drivers/hid/hid-input.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/hid/hid-input.c +1 -1
@@ -1595,7 +1595,7 @@ static bool __hidinput_change_resolutionif (usage->hid !=HID_GD_RESOLUTION_MULTIPLIER )continue ; - *report->field[i]->value = value; + report->field[i]->value[j] = value; update_needed = true; } }
Greg Kroah-Hartman
maintainerPATCH 40/115 drm/i915: Fix per-pixel alpha with CCS
In reply to Greg Kroah-HartmanFrom: Ville Syrjälä <[email protected]>
commit 77ce94dbe586c1a6a26cf021c08109c9ce71b3e0 upstream.
We forgot to set .has_alpha=true for the A+CCS formats when the code started to consult .has_alpha. This manifests as A+CCS being treated as X+CCS which means no per-pixel alpha blending. Fix the format list appropriately.
--- drivers/gpu/drm/i915/intel_display.c | 12 ++++++++---- 1 file changed, 8 insertions(+), 4 deletions(-)
drivers/gpu/drm/i915/intel_display.c +8 -4
@@ -2444,10 +2444,14 @@ static unsigned int intel_fb_modifier_to* main surface. */ static const struct drm_format_info ccs_formats[] = { - { .format =DRM_FORMAT_XRGB8888 , .depth =24 , .num_planes =2 , .cpp = {4 ,1 , }, .hsub =8 , .vsub =16 , }, - { .format =DRM_FORMAT_XBGR8888 , .depth =24 , .num_planes =2 , .cpp = {4 ,1 , }, .hsub =8 , .vsub =16 , }, - { .format =DRM_FORMAT_ARGB8888 , .depth =32 , .num_planes =2 , .cpp = {4 ,1 , }, .hsub =8 , .vsub =16 , }, - { .format =DRM_FORMAT_ABGR8888 , .depth =32 , .num_planes =2 , .cpp = {4 ,1 , }, .hsub =8 , .vsub =16 , }, + { .format =DRM_FORMAT_XRGB8888 , .depth =24 , .num_planes =2 , + .cpp = {4 ,1 , }, .hsub =8 , .vsub =16 , }, + { .format =DRM_FORMAT_XBGR8888 , .depth =24 , .num_planes =2 , + .cpp = {4 ,1 , }, .hsub =8 , .vsub =16 , }, + { .format =DRM_FORMAT_ARGB8888 , .depth =32 , .num_planes =2 , + .cpp = {4 ,1 , }, .hsub =8 , .vsub =16 , .has_alpha = true, }, + { .format =DRM_FORMAT_ABGR8888 , .depth =32 , .num_planes =2 , + .cpp = {4 ,1 , }, .hsub =8 , .vsub =16 , .has_alpha = true, }, }; static const struct drm_format_info *
Greg Kroah-Hartman
maintainerPATCH 5/115 Revert "HID: Increase maximum report size allowed by hid_field_extract()"
In reply to Greg Kroah-HartmanFrom: Benjamin Tissoires <[email protected]>
commit 15fc1b5c86128f91c8c6699c3b0d9615740b13f1 upstream.
This reverts commit 94a9992f7dbdfb28976b565af220e0c4a117144a.
The commit allows for more than 32 bits in hid_field_extract(), but the return value is a 32 bits int.
So basically what this commit is doing is just silencing those legitimate errors.
Revert to a previous situation in the hope that a proper fix will be impletemented.
--- drivers/hid/hid-core.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-)
drivers/hid/hid-core.c +3 -3
@@ -1313,10 +1313,10 @@ static u32 __extract(u8 *report, unsigneu32 hid_field_extract (const struct hid_device *hid,u8 *report,unsigned offset,unsigned n) { -if (n >256 ) { -hid_warn (hid,"hid_field_extract() called with n (%d) > 256! (%s)\n" , +if (n >32 ) { +hid_warn (hid,"hid_field_extract() called with n (%d) > 32! (%s)\n" , n, current->comm); - n =256 ; + n =32 ; }return __extract (report, offset, n);
Greg Kroah-Hartman
maintainerPATCH 6/115 HID: multitouch: handle faulty Elo touch device
In reply to Greg Kroah-HartmanFrom: Benjamin Tissoires <[email protected]>
commit 81bcbad53bab4bf9f200eda303d7a05cdb9bd73b upstream.
Since kernel v5.0, one single win8 touchscreen device failed. And it turns out this is because it reports 2 InRange usage per touch.
It's a first, and I *really* wonder how this was allowed by Microsoft in the first place. But IIRC, Breno told me this happened *after* a firmware upgrade...
Anyway, better be safe for those crappy devices, and make sure we have a full slot before jumping to the next.
This won't prevent all crappy devices to fail here, but at least we will have a safeguard as long as the contact ID and the X and Y coordinates are placed in the report after the grabage.
--- drivers/hid/hid-multitouch.c | 7 +++++++ 1 file changed, 7 insertions(+)
drivers/hid/hid-multitouch.c +7 -0
@@ -641,6 +641,13 @@ static void mt_store_field(struct hid_deif (*target !=DEFAULT_TRUE && *target !=DEFAULT_FALSE && *target !=DEFAULT_ZERO ) { +if (usage->contactid ==DEFAULT_ZERO || + usage->x ==DEFAULT_ZERO || + usage->y ==DEFAULT_ZERO ) { +hid_dbg (hdev, +"ignoring duplicate usage on incomplete" ); +return ; + } usage =mt_allocate_usage (hdev, application);if (!usage)return ;
Greg Kroah-Hartman
maintainerPATCH 7/115 HID: wacom: Dont set tool type until were in range
In reply to Greg Kroah-HartmanFrom: Jason Gerecke <[email protected]>
commit 2cc08800a6b9fcda7c7afbcf2da1a6e8808da725 upstream.
The serial number and tool type information that is reported by the tablet while a pen is merely "in prox" instead of fully "in range" can be stale and cause us to report incorrect tool information. Serial number, tool type, and other information is only valid once the pen comes fully in range so we should be careful to not use this information until that point.
In particular, this issue may cause the driver to incorectly report BTN_TOOL_RUBBER after switching from the eraser tool back to the pen.
--- drivers/hid/wacom_wac.c | 17 ++++++++++++++++- 1 file changed, 16 insertions(+), 1 deletion(-)
drivers/hid/wacom_wac.c +16 -1
@@ -1236,13 +1236,13 @@ static void wacom_intuos_pro2_bt_pen(str/* Add back in missing bits of ID for non-USI pens */ wacom->id[0 ] |= (wacom->serial[0 ] >>32 ) &0xFFFFF ; } - wacom->tool[0 ] =wacom_intuos_get_tool_type (wacom_intuos_id_mangle (wacom->id[0 ]));for (i =0 ; i < pen_frames; i++) {unsigned char *frame = &data[i*pen_frame_len +1 ];bool valid = frame[0 ] &0x80 ;bool prox = frame[0 ] &0x40 ;bool range = frame[0 ] &0x20 ; +bool invert = frame[0 ] &0x10 ;if (!valid)continue ;
@@ -1251,9 +1251,24 @@ static void wacom_intuos_pro2_bt_pen(str wacom->shared->stylus_in_proximity = false;wacom_exit_report (wacom);input_sync (pen_input); + + wacom->tool[0 ] =0 ; + wacom->id[0 ] =0 ; + wacom->serial[0 ] =0 ;return ; } +if (range) { +if (!wacom->tool[0 ]) {/* first in range */ +/* Going into range select tool */ +if (invert) + wacom->tool[0 ] =BTN_TOOL_RUBBER ; +else if (wacom->id[0 ]) + wacom->tool[0 ] =wacom_intuos_get_tool_type (wacom->id[0 ]); +else + wacom->tool[0 ] =BTN_TOOL_PEN ; + } +input_report_abs (pen_input,ABS_X ,get_unaligned_le16 (&frame[1 ]));input_report_abs (pen_input,ABS_Y ,get_unaligned_le16 (&frame[3 ]));
Greg Kroah-Hartman
maintainerPATCH 8/115 HID: wacom: Dont report anything prior to the tool entering range
In reply to Greg Kroah-HartmanFrom: Jason Gerecke <[email protected]>
commit e92a7be7fe5b2510fa60965eaf25f9e3dc08b8cc upstream.
If the tool spends some time in prox before entering range, a series of events (e.g. ABS_DISTANCE, MSC_SERIAL) can be sent before we or userspace have any clue about the pen whose data is being reported. We need to hold off on reporting anything until the pen has entered range. Since we still want to report events that occur "in prox" after the pen has *left* range we use 'wacom-tool[0]' as the indicator that the pen did at one point enter range and provide us/userspace with tool type and serial number information.
--- drivers/hid/wacom_wac.c | 33 ++++++++++++++++++--------------- 1 file changed, 18 insertions(+), 15 deletions(-)
drivers/hid/wacom_wac.c +18 -15
@@ -1290,23 +1290,26 @@ static void wacom_intuos_pro2_bt_pen(str get_unaligned_le16(&frame[11])); } } -input_report_abs (pen_input,ABS_PRESSURE ,get_unaligned_le16 (&frame[5 ])); -if (wacom->features.type ==INTUOSP2_BT ) { -input_report_abs (pen_input,ABS_DISTANCE , - range ? frame[13 ] : wacom->features.distance_max); - }else { -input_report_abs (pen_input,ABS_DISTANCE , - range ? frame[7 ] : wacom->features.distance_max); - } -input_report_key (pen_input,BTN_TOUCH , frame[0 ] &0x01 ); -input_report_key (pen_input,BTN_STYLUS , frame[0 ] &0x02 ); -input_report_key (pen_input,BTN_STYLUS2 , frame[0 ] &0x04 ); +if (wacom->tool[0 ]) { +input_report_abs (pen_input,ABS_PRESSURE ,get_unaligned_le16 (&frame[5 ])); +if (wacom->features.type ==INTUOSP2_BT ) { +input_report_abs (pen_input,ABS_DISTANCE , + range ? frame[13 ] : wacom->features.distance_max); + }else { +input_report_abs (pen_input,ABS_DISTANCE , + range ? frame[7 ] : wacom->features.distance_max); + } + +input_report_key (pen_input,BTN_TOUCH , frame[0 ] &0x01 ); +input_report_key (pen_input,BTN_STYLUS , frame[0 ] &0x02 ); +input_report_key (pen_input,BTN_STYLUS2 , frame[0 ] &0x04 ); -input_report_key (pen_input, wacom->tool[0 ], prox); -input_event (pen_input,EV_MSC ,MSC_SERIAL , wacom->serial[0 ]); -input_report_abs (pen_input,ABS_MISC , -wacom_intuos_id_mangle (wacom->id[0 ]));/* report tool id */ +input_report_key (pen_input, wacom->tool[0 ], prox); +input_event (pen_input,EV_MSC ,MSC_SERIAL , wacom->serial[0 ]); +input_report_abs (pen_input,ABS_MISC , +wacom_intuos_id_mangle (wacom->id[0 ]));/* report tool id */ + } wacom->shared->stylus_in_proximity = prox;
Greg Kroah-Hartman
maintainerPATCH 9/115 HID: wacom: Send BTN_TOUCH in response to INTUOSP2_BT eraser contact
In reply to Greg Kroah-HartmanFrom: Jason Gerecke <[email protected]>
commit fe7f8d73d1af19b678171170e4e5384deb57833d upstream.
The Bluetooth reports from the 2nd-gen Intuos Pro have separate bits for indicating if the tip or eraser is in contact with the tablet. At the moment, only the tip contact bit controls the state of the BTN_TOUCH event. This prevents the eraser from working as expected. This commit changes the driver to send BTN_TOUCH whenever either the tip or eraser contact bit is set.
--- drivers/hid/wacom_wac.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/hid/wacom_wac.c +1 -1
@@ -1301,7 +1301,7 @@ static void wacom_intuos_pro2_bt_pen(str range ? frame[7] : wacom->features.distance_max); } -input_report_key (pen_input,BTN_TOUCH , frame[0 ] &0x01 ); +input_report_key (pen_input,BTN_TOUCH , frame[0 ] &0x09 );input_report_key (pen_input,BTN_STYLUS , frame[0 ] &0x02 );input_report_key (pen_input,BTN_STYLUS2 , frame[0 ] &0x04 );
Greg Kroah-Hartman
maintainercover 5.1.12-stable review
This is the start of the stable review cycle for the 5.1.12 release. There are 115 patches in this series, all will be posted as a response to this one. If anyone has any issues with these being applied, please let me know.
Responses should be made by Wed 19 Jun 2019 09:06:21 PM UTC. Anything received after that time might be too late.
The whole patch series can be found in one patch at:
https://www.kernel.org/pub/linux/kernel/v5.x/stable-review/patch-5.1.12-rc1.gz
or in the git tree and branch at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git linux-5.1.y
and the diffstat can be found below.
thanks,
greg k-h
-------------
Pseudo-Shortlog of commits:
Greg Kroah-Hartman <[email protected]>
Linux 5.1.12-rc1
Nicholas Piggin <[email protected]>
powerpc/64s: Fix THP PMD collapse serialisation
Christophe Leroy <[email protected]>
powerpc: Fix kexec failure on book3s/32
Jani Nikula <[email protected]>
drm: add fallback override/firmware EDID modes workaround
Jani Nikula <[email protected]>
drm/edid: abstract override/firmware EDID retrieval
Prarit Bhargava <[email protected]>
x86/resctrl: Prevent NULL pointer dereference when local MBM is disabled
Baoquan He <[email protected]>
x86/mm/KASLR: Compute the size of the vmemmap section properly
Andrey Ryabinin <[email protected]>
x86/kasan: Fix boot with 5-level paging and KASAN
Borislav Petkov <[email protected]>
x86/microcode, cpuhotplug: Add a microcode loader CPU hotplug callback
Borislav Petkov <[email protected]>
RAS/CEC: Fix binary search function
Cong Wang <[email protected]>
RAS/CEC: Convert the timer callback to a workqueue
Thomas Gleixner <[email protected]>
timekeeping: Repair ktime_get_coarse*() granularity
Eiichi Tsukata <[email protected]>
tracing/uprobe: Fix NULL pointer dereference in trace_uprobe_create()
Daniele Palmas <[email protected]>
USB: serial: option: add Telit 0x1260 and 0x1261 compositions
Jörgen Storvist <[email protected]>
USB: serial: option: add support for Simcom SIM7500/SIM7600 RNDIS mode
Chris Packham <[email protected]>
USB: serial: pl2303: add Allied Telesis VT-Kit3
Kai-Heng Feng <[email protected]>
USB: usb-storage: Add new ID to ums-realtek
Marco Zatta <[email protected]>
USB: Fix chipmunk-like voice when using Logitech C270 for recording audio.
Douglas Anderson <[email protected]>
usb: dwc2: host: Fix wMaxPacketSize handling (fix webcam regression)
Martin Schiller <[email protected]>
usb: dwc2: Fix DMA cache alignment issues
Murray McAllister <[email protected]>
drm/vmwgfx: NULL pointer dereference from vmw_cmd_dx_view_define()
Murray McAllister <[email protected]>
drm/vmwgfx: integer underflow in vmw_cmd_dx_set_shader() leading to an invalid read
Stefan Raspl <[email protected]>
tools/kvm_stat: fix fields filter for child events
Andrew Jones <[email protected]>
kvm: selftests: aarch64: fix default vm mode
Andrew Jones <[email protected]>
kvm: selftests: aarch64: dirty_log_test: fix unaligned memslot size
Christian Borntraeger <[email protected]>
KVM: s390: fix memory slot handling for KVM_SET_USER_MEMORY_REGION
Paolo Bonzini <[email protected]>
KVM: x86/pmu: do not mask the value that is written to fixed PMUs
Paolo Bonzini <[email protected]>
KVM: x86/pmu: mask the result of rdpmc according to the width of the counters
Paolo Bonzini <[email protected]>
KVM: x86: do not spam dmesg with VMCS/VMCB dumps
Wanpeng Li <[email protected]>
KVM: LAPIC: Fix lapic_timer_advance_ns parameter overflow
Yi Wang <[email protected]>
kvm: vmx: Fix -Wmissing-prototypes warnings
Dan Carpenter <[email protected]>
KVM: selftests: Fix a condition in test_hv_cpuid()
Paolo Bonzini <[email protected]>
KVM: nVMX: really fix the size checks on KVM_SET_NESTED_STATE
James Morse <[email protected]>
KVM: arm/arm64: Move cc/it checks under hyp's Makefile to avoid instrumentation
Jens Axboe <[email protected]>
tools/io_uring: fix Makefile for pthread library link
Keith Busch <[email protected]>
nvme-pci: use blk-mq mapping for unmanaged irqs
Bernd Eckstein <[email protected]>
usbnet: ipheth: fix racing condition
Tom Zanussi <[email protected]>
tracing: Prevent hist_field_var_ref() from accessing NULL tracing_map_elts
Kees Cook <[email protected]>
selftests/timers: Add missing fflush(stdout) calls
Hangbin Liu <[email protected]>
selftests: fib_rule_tests: fix local IPv4 address typo
Qian Cai <[email protected]>
libnvdimm: Fix compilation warnings with W=1
Flora Cui <[email protected]>
drm/amdgpu: keep stolen memory on picasso
Colin Ian King <[email protected]>
scsi: bnx2fc: fix incorrect cast to u64 on shift operation
YueHaibing <[email protected]>
scsi: myrs: Fix uninitialized variable
Steffen Dirkwinkel <[email protected]>
platform/x86: pmc_atom: Add several Beckhoff Automation boards to critclk_systems DMI table
Hans de Goede <[email protected]>
platform/x86: pmc_atom: Add Lex 3I380D industrial PC to critclk_systems DMI table
Yufen Yu <[email protected]>
nvme: fix memory leak for power latency tolerance
Christoph Hellwig <[email protected]>
nvme: release namespace SRCU protection before performing controller ioctls
Christoph Hellwig <[email protected]>
nvme: merge nvme_ns_ioctl into nvme_ioctl
Christoph Hellwig <[email protected]>
nvme: remove the ifdef around nvme_nvm_ioctl
Christoph Hellwig <[email protected]>
nvme: fix srcu locking on error return in nvme_get_ns_from_disk
Keith Busch <[email protected]>
nvme-pci: Fix controller freeze wait disabling
Alexei Starovoitov <[email protected]>
selftests/bpf: fix bpf_get_current_task
Yonghong Song <[email protected]>
tools/bpftool: move set_max_rlimit() before __bpf_object__open_xattr()
Mark Rutland <[email protected]>
arm64/mm: Inhibit huge-vmap with ptdump
John Fastabend <[email protected]>
bpf, tcp: correctly handle DONT_WAIT flags and timeo == 0
Claudiu Manoil <[email protected]>
enetc: Fix NULL dma address unmap for Tx BD extensions
Luca Ceresoli <[email protected]>
net: macb: fix error format in dev_err()
Will Deacon <[email protected]>
arm64: Print physical address of page table base in show_pte()
James Smart <[email protected]>
scsi: lpfc: add check for loss of ndlp when sending RRQ
James Smart <[email protected]>
scsi: lpfc: correct rcu unlock issue in lpfc_nvme_info_show
James Smart <[email protected]>
scsi: lpfc: resolve lockdep warnings
YueHaibing <[email protected]>
scsi: qedi: remove set but not used variables 'cdev' and 'udev'
YueHaibing <[email protected]>
scsi: qedi: remove memset/memcpy to nfunc and use func instead
Quinn Tran <[email protected]>
scsi: qla2xxx: Add cleanup for PCI EEH recovery
John Fastabend <[email protected]>
bpf: sockmap fix msg->sg.size account on ingress skb
John Fastabend <[email protected]>
bpf: sockmap remove duplicate queue free
John Fastabend <[email protected]>
bpf: sockmap, only stop/flush strp if it was enabled at some point
Will Deacon <[email protected]>
drivers/perf: arm_spe: Don't error on high-order pages for aux buf
Randall Huang <[email protected]>
f2fs: fix to avoid accessing xattr across the boundary
Young Xiao <[email protected]>
Drivers: misc: fix out-of-bounds access in function param_set_kgdbts_var
Takashi Iwai <[email protected]>
Revert "ALSA: seq: Protect in-kernel ioctl calls with mutex"
Takashi Iwai <[email protected]>
ALSA: seq: Fix race of get-subscription call vs port-delete ioctls
Takashi Iwai <[email protected]>
ALSA: seq: Protect in-kernel ioctl calls with mutex
Peter Zijlstra <[email protected]>
x86/uaccess, kcov: Disable stack protector
Lucas De Marchi <[email protected]>
drm/i915/dmc: protect against reading random memory
Ville Syrjälä <[email protected]>
drm/i915: Fix per-pixel alpha with CCS
Hans de Goede <[email protected]>
drm/i915/dsi: Use a fuzzy check for burst mode clock check
Ville Syrjälä <[email protected]>
drm/i915/sdvo: Implement proper HDMI audio support for SDVO
Shirish S <[email protected]>
drm/amdgpu/{uvd,vcn}: fetch ring's read_ptr after alloc
Kuninori Morimoto <[email protected]>
ASoC: soc-core: fixup references at soc_cleanup_card_resources()
S.j. Wang <[email protected]>
ASoC: fsl_asrc: Fix the issue about unsupported rate
S.j. Wang <[email protected]>
ASoC: cs42xx8: Add regcache mask dirty
Tejun Heo <[email protected]>
cgroup: Use css_tryget() instead of css_tryget_online() in task_get_css()
Coly Li <[email protected]>
bcache: only set BCACHE_DEV_WB_RUNNING when cached device attached
Coly Li <[email protected]>
bcache: fix stack corruption by PRECEDING_KEY()
Russell King <[email protected]>
i2c: acorn: fix i2c warning
Casey Schaufler <[email protected]>
Smack: Restore the smackfsdef mount option and add missing prefixes
Robin Murphy <[email protected]>
iommu/arm-smmu: Avoid constant zero in TLBI writes
Sean Young <[email protected]>
media: dvb: warning about dvb frequency limits produces too much noise
Jann Horn <[email protected]>
ptrace: restore smp_rmb() in __ptrace_may_access()
Eric W. Biederman <[email protected]>
signal/ptrace: Don't leak unitialized kernel memory with PTRACE_PEEK_SIGINFO
Minchan Kim <[email protected]>
mm/vmscan.c: fix trying to reclaim unevictable LRU page
Wengang Wang <[email protected]>
fs/ocfs2: fix race in ocfs2_dentry_attach_lock()
Shakeel Butt <[email protected]>
mm/list_lru.c: fix memory leak in __memcg_init_list_lru_node
Eric Biggers <[email protected]>
io_uring: fix memory leak of UNIX domain socket inode
Hans de Goede <[email protected]>
libata: Extend quirks for the ST1000LM024 drives with NOLPM quirk
Gen Zhang <[email protected]>
selinux: fix a missing-check bug in selinux_sb_eat_lsm_opts()
Gen Zhang <[email protected]>
selinux: fix a missing-check bug in selinux_add_mnt_opt( )
Ondrej Mosnacek <[email protected]>
selinux: log raw contexts as untrusted strings
Takashi Sakamoto <[email protected]>
ALSA: firewire-motu: fix destruction of data for isochronous resources
Kailang Yang <[email protected]>
ALSA: hda/realtek - Update headset mode for ALC256
Rui Nuno Capela <[email protected]>
ALSA: ice1712: Check correct return value to snd_i2c_sendbytes (EWS/DMX 6Fire)
Takashi Sakamoto <[email protected]>
ALSA: oxfw: allow PCM capture for Stanton SCS.1m
Hui Wang <[email protected]>
Revert "ALSA: hda/realtek - Improve the headset mic for Acer Aspire laptops"
Jason Gerecke <[email protected]>
HID: wacom: Sync INTUOSP2_BT touch state after each frame if necessary
Jason Gerecke <[email protected]>
HID: wacom: Correct button numbering 2nd-gen Intuos Pro over Bluetooth
Jason Gerecke <[email protected]>
HID: wacom: Send BTN_TOUCH in response to INTUOSP2_BT eraser contact
Jason Gerecke <[email protected]>
HID: wacom: Don't report anything prior to the tool entering range
Jason Gerecke <[email protected]>
HID: wacom: Don't set tool type until we're in range
Benjamin Tissoires <[email protected]>
HID: multitouch: handle faulty Elo touch device
Benjamin Tissoires <[email protected]>
Revert "HID: Increase maximum report size allowed by hid_field_extract()"
Benjamin Tissoires <[email protected]>
HID: input: fix assignment of .value
Benjamin Tissoires <[email protected]>
HID: input: make sure the wheel high resolution multiplier is set
Thomas Backlund <[email protected]>
nouveau: Fix build with CONFIG_NOUVEAU_LEGACY_CTX_SUPPORT disabled
Dave Airlie <[email protected]>
drm/nouveau: add kconfig option to turn off nouveau legacy contexts. (v3)
-------------
Diffstat:
Makefile | 4 +- arch/arm/kvm/hyp/Makefile | 1 + arch/arm64/kvm/hyp/Makefile | 1 + arch/arm64/mm/fault.c | 5 +- arch/arm64/mm/mmu.c | 11 +- arch/powerpc/include/asm/book3s/64/pgtable.h | 30 +++ arch/powerpc/include/asm/kexec.h | 3 + arch/powerpc/kernel/machine_kexec_32.c | 4 +- arch/powerpc/mm/pgtable-book3s64.c | 3 + arch/s390/kvm/kvm-s390.c | 35 ++-- arch/x86/kernel/cpu/microcode/core.c | 2 +- arch/x86/kernel/cpu/resctrl/monitor.c | 3 + arch/x86/kvm/pmu.c | 10 +- arch/x86/kvm/pmu.h | 3 +- arch/x86/kvm/pmu_amd.c | 2 +- arch/x86/kvm/svm.c | 9 +- arch/x86/kvm/vmx/nested.c | 2 +- arch/x86/kvm/vmx/pmu_intel.c | 26 ++- arch/x86/kvm/vmx/vmx.c | 26 ++- arch/x86/kvm/vmx/vmx.h | 1 + arch/x86/kvm/x86.c | 2 +- arch/x86/mm/kasan_init_64.c | 2 +- arch/x86/mm/kaslr.c | 11 +- drivers/ata/libata-core.c | 9 +- drivers/gpu/drm/amd/amdgpu/amdgpu_vcn.c | 4 +- drivers/gpu/drm/amd/amdgpu/gmc_v9_0.c | 1 + drivers/gpu/drm/amd/amdgpu/uvd_v6_0.c | 5 +- drivers/gpu/drm/amd/amdgpu/uvd_v7_0.c | 5 +- drivers/gpu/drm/drm_edid.c | 55 ++++- drivers/gpu/drm/drm_probe_helper.c | 7 + drivers/gpu/drm/i915/intel_csr.c | 18 ++ drivers/gpu/drm/i915/intel_display.c | 14 +- drivers/gpu/drm/i915/intel_drv.h | 1 + drivers/gpu/drm/i915/intel_dsi_vbt.c | 11 + drivers/gpu/drm/i915/intel_sdvo.c | 58 +++++- drivers/gpu/drm/i915/intel_sdvo_regs.h | 3 + drivers/gpu/drm/nouveau/Kconfig | 13 +- drivers/gpu/drm/nouveau/nouveau_drm.c | 7 +- drivers/gpu/drm/nouveau/nouveau_ttm.c | 4 + drivers/gpu/drm/vmwgfx/vmwgfx_execbuf.c | 7 +- drivers/hid/hid-core.c | 13 +- drivers/hid/hid-input.c | 81 +++++--- drivers/hid/hid-multitouch.c | 7 + drivers/hid/wacom_wac.c | 71 +++++-- drivers/i2c/busses/i2c-acorn.c | 1 + drivers/iommu/arm-smmu.c | 15 +- drivers/md/bcache/bset.c | 16 +- drivers/md/bcache/bset.h | 34 ++-- drivers/md/bcache/sysfs.c | 7 +- drivers/media/dvb-core/dvb_frontend.c | 2 +- drivers/misc/kgdbts.c | 4 +- drivers/net/ethernet/cadence/macb_main.c | 16 +- drivers/net/ethernet/freescale/enetc/enetc.c | 4 +- drivers/net/usb/ipheth.c | 3 +- drivers/nvdimm/bus.c | 4 +- drivers/nvdimm/label.c | 2 + drivers/nvdimm/label.h | 2 - drivers/nvme/host/core.c | 74 ++++--- drivers/nvme/host/pci.c | 14 +- drivers/perf/arm_spe_pmu.c | 10 +- drivers/platform/x86/pmc_atom.c | 33 +++ drivers/ras/cec.c | 80 ++++---- drivers/scsi/bnx2fc/bnx2fc_hwi.c | 2 +- drivers/scsi/lpfc/lpfc_attr.c | 37 ++-- drivers/scsi/lpfc/lpfc_els.c | 5 +- drivers/scsi/lpfc/lpfc_sli.c | 84 +++++--- drivers/scsi/myrs.c | 2 +- drivers/scsi/qedi/qedi_dbg.c | 32 +-- drivers/scsi/qedi/qedi_iscsi.c | 4 - drivers/scsi/qla2xxx/qla_os.c | 221 ++++++++------------- drivers/usb/core/quirks.c | 3 + drivers/usb/dwc2/hcd.c | 39 ++-- drivers/usb/dwc2/hcd.h | 20 +- drivers/usb/dwc2/hcd_intr.c | 5 +- drivers/usb/dwc2/hcd_queue.c | 10 +- drivers/usb/serial/option.c | 6 + drivers/usb/serial/pl2303.c | 1 + drivers/usb/serial/pl2303.h | 3 + drivers/usb/storage/unusual_realtek.h | 5 + fs/f2fs/xattr.c | 36 +++- fs/f2fs/xattr.h | 2 + fs/io_uring.c | 4 +- fs/ocfs2/dcache.c | 12 ++ include/drm/drm_edid.h | 1 + include/linux/cgroup.h | 10 +- include/linux/cpuhotplug.h | 1 + include/linux/hid.h | 2 +- kernel/Makefile | 1 + kernel/cred.c | 9 + kernel/ptrace.c | 20 +- kernel/time/timekeeping.c | 5 +- kernel/trace/trace_events_hist.c | 3 + kernel/trace/trace_uprobe.c | 13 +- mm/list_lru.c | 2 +- mm/vmscan.c | 2 +- net/core/skmsg.c | 7 +- net/ipv4/tcp_bpf.c | 7 +- security/selinux/avc.c | 10 +- security/selinux/hooks.c | 39 +++- security/smack/smack_lsm.c | 12 +- sound/core/seq/seq_clientmgr.c | 10 +- sound/core/seq/seq_ports.c | 13 +- sound/core/seq/seq_ports.h | 5 +- sound/firewire/motu/motu-stream.c | 2 +- sound/firewire/oxfw/oxfw.c | 3 - sound/pci/hda/patch_realtek.c | 91 ++++++--- sound/pci/ice1712/ews.c | 2 +- sound/soc/codecs/cs42xx8.c | 1 + sound/soc/fsl/fsl_asrc.c | 4 +- sound/soc/soc-core.c | 7 +- sound/soc/soc-dapm.c | 3 + tools/bpf/bpftool/prog.c | 4 +- tools/io_uring/Makefile | 2 +- tools/kvm/kvm_stat/kvm_stat | 16 +- tools/kvm/kvm_stat/kvm_stat.txt | 2 + tools/testing/selftests/bpf/bpf_helpers.h | 2 +- tools/testing/selftests/kvm/dirty_log_test.c | 2 +- .../testing/selftests/kvm/lib/aarch64/processor.c | 2 +- tools/testing/selftests/kvm/x86_64/hyperv_cpuid.c | 5 +- tools/testing/selftests/net/fib_rule_tests.sh | 2 +- tools/testing/selftests/timers/adjtick.c | 1 + tools/testing/selftests/timers/leapcrash.c | 1 + tools/testing/selftests/timers/mqueue-lat.c | 1 + tools/testing/selftests/timers/nanosleep.c | 1 + tools/testing/selftests/timers/nsleep-lat.c | 1 + tools/testing/selftests/timers/raw_skew.c | 1 + tools/testing/selftests/timers/set-tai.c | 1 + tools/testing/selftests/timers/set-tz.c | 2 + tools/testing/selftests/timers/threadtest.c | 1 + tools/testing/selftests/timers/valid-adjtimex.c | 2 + virt/kvm/arm/aarch32.c | 121 ----------- virt/kvm/arm/hyp/aarch32.c | 136 +++++++++++++ 132 files changed, 1296 insertions(+), 739 deletions(-)
Greg Kroah-Hartman
maintainerPATCH 42/115 x86/uaccess, kcov: Disable stack protector
[ Upstream commit 40ea97290b08be2e038b31cbb33097d1145e8169 ]
New tooling noticed this mishap:
kernel/kcov.o: warning: objtool: write_comp_data()+0x138: call to __stack_chk_fail() with UACCESS enabled kernel/kcov.o: warning: objtool: __sanitizer_cov_trace_pc()+0xd9: call to __stack_chk_fail() with UACCESS enabled
All the other instrumentation (KASAN,UBSAN) also have stack protector disabled.
--- kernel/Makefile | 1 + 1 file changed, 1 insertion(+)
kernel/Makefile +1 -0
@@ -30,6 +30,7 @@ KCOV_INSTRUMENT_extable.o := n # Don't self-instrument. KCOV_INSTRUMENT_kcov.o := n KASAN_SANITIZE_kcov.o := n +CFLAGS_kcov.o := $(call cc-option, -fno-conserve-stack -fno-stack-protector) # cond_syscall is currently not LTO compatible CFLAGS_sys_ni.o = $(DISABLE_LTO)
Signature · 1 line
2.20.1
Greg Kroah-Hartman
maintainerPATCH 51/115 bpf: sockmap fix msg->sg.size account on ingress skb
In reply to Greg Kroah-Hartman[ Upstream commit cabede8b4f2b746232aa25730a0b752de1cb82ca ]
When converting a skb to msg->sg we forget to set the size after the latest ktls/tls code conversion. This patch can be reached by doing a redir into ingress path from BPF skb sock recv hook. Then trying to read the size fails.
Fix this by setting the size.
--- net/core/skmsg.c | 1 + 1 file changed, 1 insertion(+)
net/core/skmsg.c +1 -0
@@ -411,6 +411,7 @@ static int sk_psock_skb_ingress(struct sk_psock *psock, struct sk_buff *skb)sk_mem_charge (sk, skb->len); copied = skb->len; msg->sg.start =0 ; + msg->sg.size = copied; msg->sg.end = num_sge ==MAX_MSG_FRAGS ?0 : num_sge; msg->skb = skb;
Signature · 1 line
2.20.1
Greg Kroah-Hartman
maintainerPATCH 52/115 scsi: qla2xxx: Add cleanup for PCI EEH recovery
In reply to Greg Kroah-Hartman[ Upstream commit 5386a4e6c7fecd282d265a24d930a74ba3c5917b ]
During EEH error recovery testing it was discovered that driver's reset() callback partially frees resources used by driver, leaving some stale memory. After reset() is done and when resume() callback in driver uses old data which results into error leaving adapter disabled due to PCIe error.
This patch does cleanup for EEH recovery code path and prevents adapter from getting disabled.
--- drivers/scsi/qla2xxx/qla_os.c | 221 +++++++++++++--------------------- 1 file changed, 82 insertions(+), 139 deletions(-)
drivers/scsi/qla2xxx/qla_os.c +82 -139
@@ -6838,6 +6838,78 @@ qla2x00_release_firmware(void)mutex_unlock (&qla_fw_lock); } +static void qla_pci_error_cleanup (scsi_qla_host_t *vha) +{ +struct qla_hw_data *ha = vha->hw; +scsi_qla_host_t *base_vha =pci_get_drvdata (ha->pdev); +struct qla_qpair *qpair =NULL ; +struct scsi_qla_host *vp; +fc_port_t *fcport; +int i; +unsigned long flags; + + ha->chip_reset++; + + ha->base_qpair->chip_reset = ha->chip_reset; +for (i =0 ; i < ha->max_qpairs; i++) { +if (ha->queue_pair_map[i]) + ha->queue_pair_map[i]->chip_reset = + ha->base_qpair->chip_reset; + } + +/* purge MBox commands */ +if (atomic_read (&ha->num_pend_mbx_stage3)) { +clear_bit (MBX_INTR_WAIT , &ha->mbx_cmd_flags); +complete (&ha->mbx_intr_comp); + } + + i =0 ; + +while (atomic_read (&ha->num_pend_mbx_stage3) || +atomic_read (&ha->num_pend_mbx_stage2) || +atomic_read (&ha->num_pend_mbx_stage1)) { +msleep (20 ); + i++; +if (i >50 ) +break ; + } + + ha->flags.purge_mbox =0 ; + +mutex_lock (&ha->mq_lock); +list_for_each_entry (qpair, &base_vha->qp_list, qp_list_elem) + qpair->online =0 ; +mutex_unlock (&ha->mq_lock); + +qla2x00_mark_all_devices_lost (vha,0 ); + +spin_lock_irqsave (&ha->vport_slock, flags); +list_for_each_entry (vp, &ha->vp_list, list) { +atomic_inc (&vp->vref_count); +spin_unlock_irqrestore (&ha->vport_slock, flags); +qla2x00_mark_all_devices_lost (vp,0 ); +spin_lock_irqsave (&ha->vport_slock, flags); +atomic_dec (&vp->vref_count); + } +spin_unlock_irqrestore (&ha->vport_slock, flags); + +/* Clear all async request states across all VPs. */ +list_for_each_entry (fcport, &vha->vp_fcports, list) + fcport->flags &= ~(FCF_LOGIN_NEEDED |FCF_ASYNC_SENT ); + +spin_lock_irqsave (&ha->vport_slock, flags); +list_for_each_entry (vp, &ha->vp_list, list) { +atomic_inc (&vp->vref_count); +spin_unlock_irqrestore (&ha->vport_slock, flags); +list_for_each_entry (fcport, &vp->vp_fcports, list) + fcport->flags &= ~(FCF_LOGIN_NEEDED |FCF_ASYNC_SENT ); +spin_lock_irqsave (&ha->vport_slock, flags); +atomic_dec (&vp->vref_count); + } +spin_unlock_irqrestore (&ha->vport_slock, flags); +} + +static pci_ers_result_t qla2xxx_pci_error_detected (struct pci_dev *pdev,pci_channel_state_t state) {
@@ -6863,20 +6935,7 @@ qla2xxx_pci_error_detected(struct pci_dev *pdev, pci_channel_state_t state)return PCI_ERS_RESULT_CAN_RECOVER ;case pci_channel_io_frozen: ha->flags.eeh_busy =1 ; -/* For ISP82XX complete any pending mailbox cmd */ -if (IS_QLA82XX (ha)) { - ha->flags.isp82xx_fw_hung =1 ; -ql_dbg (ql_dbg_aer, vha,0x9001 ,"Pci channel io frozen\n" ); -qla82xx_clear_pending_mbx (vha); - } -qla2x00_free_irqs (vha); -pci_disable_device (pdev); -/* Return back all IOs */ -qla2x00_abort_all_cmds (vha,DID_RESET <<16 ); -if (ql2xmqsupport || ql2xnvmeenable) { -set_bit (QPAIR_ONLINE_CHECK_NEEDED , &vha->dpc_flags); -qla2xxx_wake_dpc (vha); - } +qla_pci_error_cleanup (vha);return PCI_ERS_RESULT_NEED_RESET ;case pci_channel_io_perm_failure: ha->flags.pci_channel_io_perm_failure =1 ;
@@ -6930,122 +6989,14 @@ qla2xxx_pci_mmio_enabled(struct pci_dev *pdev)return PCI_ERS_RESULT_RECOVERED ; } -static uint32_t -qla82xx_error_recovery (scsi_qla_host_t *base_vha) -{ -uint32_t rval =QLA_FUNCTION_FAILED ; -uint32_t drv_active =0 ; -struct qla_hw_data *ha = base_vha->hw; -int fn; -struct pci_dev *other_pdev =NULL ; - -ql_dbg (ql_dbg_aer, base_vha,0x9006 , -"Entered %s.\n" , __func__); - -set_bit (ABORT_ISP_ACTIVE , &base_vha->dpc_flags); - -if (base_vha->flags.online) { -/* Abort all outstanding commands, -* so as to be requeued later */ -qla2x00_abort_isp_cleanup (base_vha); - } - - - fn =PCI_FUNC (ha->pdev->devfn); -while (fn >0 ) { - fn--; -ql_dbg (ql_dbg_aer, base_vha,0x9007 , -"Finding pci device at function = 0x%x.\n" , fn); - other_pdev = -pci_get_domain_bus_and_slot (pci_domain_nr (ha->pdev->bus), - ha->pdev->bus->number,PCI_DEVFN (PCI_SLOT (ha->pdev->devfn), - fn)); - -if (!other_pdev) -continue ; -if (atomic_read (&other_pdev->enable_cnt)) { -ql_dbg (ql_dbg_aer, base_vha,0x9008 , -"Found PCI func available and enable at 0x%x.\n" , - fn); -pci_dev_put (other_pdev); -break ; - } -pci_dev_put (other_pdev); - } - -if (!fn) { -/* Reset owner */ -ql_dbg (ql_dbg_aer, base_vha,0x9009 , -"This devfn is reset owner = 0x%x.\n" , - ha->pdev->devfn); -qla82xx_idc_lock (ha); - -qla82xx_wr_32 (ha,QLA82XX_CRB_DEV_STATE , -QLA8XXX_DEV_INITIALIZING ); - -qla82xx_wr_32 (ha,QLA82XX_CRB_DRV_IDC_VERSION , -QLA82XX_IDC_VERSION ); - - drv_active =qla82xx_rd_32 (ha,QLA82XX_CRB_DRV_ACTIVE ); -ql_dbg (ql_dbg_aer, base_vha,0x900a , -"drv_active = 0x%x.\n" , drv_active); - -qla82xx_idc_unlock (ha); -/* Reset if device is not already reset -* drv_active would be 0 if a reset has already been done -*/ -if (drv_active) - rval =qla82xx_start_firmware (base_vha); -else - rval =QLA_SUCCESS ; -qla82xx_idc_lock (ha); - -if (rval !=QLA_SUCCESS ) { -ql_log (ql_log_info, base_vha,0x900b , -"HW State: FAILED.\n" ); -qla82xx_clear_drv_active (ha); -qla82xx_wr_32 (ha,QLA82XX_CRB_DEV_STATE , -QLA8XXX_DEV_FAILED ); - }else { -ql_log (ql_log_info, base_vha,0x900c , -"HW State: READY.\n" ); -qla82xx_wr_32 (ha,QLA82XX_CRB_DEV_STATE , -QLA8XXX_DEV_READY ); -qla82xx_idc_unlock (ha); - ha->flags.isp82xx_fw_hung =0 ; - rval =qla82xx_restart_isp (base_vha); -qla82xx_idc_lock (ha); -/* Clear driver state register */ -qla82xx_wr_32 (ha,QLA82XX_CRB_DRV_STATE ,0 ); -qla82xx_set_drv_active (base_vha); - } -qla82xx_idc_unlock (ha); - }else { -ql_dbg (ql_dbg_aer, base_vha,0x900d , -"This devfn is not reset owner = 0x%x.\n" , - ha->pdev->devfn); -if ((qla82xx_rd_32 (ha,QLA82XX_CRB_DEV_STATE ) == -QLA8XXX_DEV_READY )) { - ha->flags.isp82xx_fw_hung =0 ; - rval =qla82xx_restart_isp (base_vha); -qla82xx_idc_lock (ha); -qla82xx_set_drv_active (base_vha); -qla82xx_idc_unlock (ha); - } - } -clear_bit (ABORT_ISP_ACTIVE , &base_vha->dpc_flags); - -return rval; -} -static pci_ers_result_t qla2xxx_pci_slot_reset (struct pci_dev *pdev) {pci_ers_result_t ret =PCI_ERS_RESULT_DISCONNECT ;scsi_qla_host_t *base_vha =pci_get_drvdata (pdev);struct qla_hw_data *ha = base_vha->hw; -struct rsp_que *rsp; -int rc, retries =10 ; +int rc; +struct qla_qpair *qpair =NULL ;ql_dbg (ql_dbg_aer, base_vha,0x9004 ,"Slot Reset.\n" );
@@ -7074,24 +7025,16 @@ qla2xxx_pci_slot_reset(struct pci_dev *pdev) goto exit_slot_reset; } - rsp = ha->rsp_q_map[0 ]; -if (qla2x00_request_irqs (ha, rsp)) - goto exit_slot_reset;if (ha->isp_ops->pci_config (base_vha)) goto exit_slot_reset; -if (IS_QLA82XX (ha)) { -if (qla82xx_error_recovery (base_vha) ==QLA_SUCCESS ) { - ret =PCI_ERS_RESULT_RECOVERED ; - goto exit_slot_reset; - }else - goto exit_slot_reset; - } - -while (ha->flags.mbox_busy && retries--) -msleep (1000 ); +mutex_lock (&ha->mq_lock); +list_for_each_entry (qpair, &base_vha->qp_list, qp_list_elem) + qpair->online =1 ; +mutex_unlock (&ha->mq_lock); + base_vha->flags.online =1 ;set_bit (ABORT_ISP_ACTIVE , &base_vha->dpc_flags);if (ha->isp_ops->abort_isp (base_vha) ==QLA_SUCCESS ) ret =PCI_ERS_RESULT_RECOVERED ;
@@ -7115,13 +7058,13 @@ qla2xxx_pci_resume(struct pci_dev *pdev)ql_dbg (ql_dbg_aer, base_vha,0x900f ,"pci_resume.\n" ); + ha->flags.eeh_busy =0 ; + ret =qla2x00_wait_for_hba_online (base_vha);if (ret !=QLA_SUCCESS ) {ql_log (ql_log_fatal, base_vha,0x9002 ,"The device failed to resume I/O from slot/link_reset.\n" ); } - - ha->flags.eeh_busy =0 ; } static void
Signature · 1 line
2.20.1
Greg Kroah-Hartman
maintainerPATCH 53/115 scsi: qedi: remove memset/memcpy to nfunc and use func instead
In reply to Greg Kroah-Hartman[ Upstream commit c09581a52765a85f19fc35340127396d5e3379cc ]
KASAN reports this:
BUG: KASAN: global-out-of-bounds in qedi_dbg_err+0xda/0x330 [qedi] Read of size 31 at addr ffffffffc12b0ae0 by task syz-executor.0/2429 CPU: 0 PID: 2429 Comm: syz-executor.0 Not tainted 5.0.0-rc7+ #45 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.10.2-1ubuntu1 04/01/2014 Call Trace: __dump_stack lib/dump_stack.c:77 [inline] dump_stack+0xfa/0x1ce lib/dump_stack.c:113 print_address_description+0x1c4/0x270 mm/kasan/report.c:187 kasan_report+0x149/0x18d mm/kasan/report.c:317 memcpy+0x1f/0x50 mm/kasan/common.c:130 qedi_dbg_err+0xda/0x330 [qedi] ? 0xffffffffc12d0000 qedi_init+0x118/0x1000 [qedi] ? 0xffffffffc12d0000 ? 0xffffffffc12d0000 ? 0xffffffffc12d0000 do_one_initcall+0xfa/0x5ca init/main.c:887 do_init_module+0x204/0x5f6 kernel/module.c:3460 load_module+0x66b2/0x8570 kernel/module.c:3808 __do_sys_finit_module+0x238/0x2a0 kernel/module.c:3902 do_syscall_64+0x147/0x600 arch/x86/entry/common.c:290 entry_SYSCALL_64_after_hwframe+0x49/0xbe RIP: 0033:0x462e99 Code: f7 d8 64 89 02 b8 ff ff ff ff c3 66 0f 1f 44 00 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 bc ff ff ff f7 d8 64 89 01 48 RSP: 002b:00007f2d57e55c58 EFLAGS: 00000246 ORIG_RAX: 0000000000000139 RAX: ffffffffffffffda RBX: 000000000073bfa0 RCX: 0000000000462e99 RDX: 0000000000000000 RSI: 00000000200003c0 RDI: 0000000000000003 RBP: 00007f2d57e55c70 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 00007f2d57e566bc R13: 00000000004bcefb R14: 00000000006f7030 R15: 0000000000000004 The buggy address belongs to the variable: __func__.67584+0x0/0xffffffffffffd520 [qedi] Memory state around the buggy address: ffffffffc12b0980: fa fa fa fa 00 04 fa fa fa fa fa fa 00 00 05 fa ffffffffc12b0a00: fa fa fa fa 00 00 04 fa fa fa fa fa 00 05 fa fa
Quoted 1 line
ffffffffc12b0a80: fa fa fa fa 00 06 fa fa fa fa fa fa 00 02 fa fa
^
ffffffffc12b0b00: fa fa fa fa 00 00 04 fa fa fa fa fa 00 00 03 fa
ffffffffc12b0b80: fa fa fa fa 00 00 02 fa fa fa fa fa 00 00 04 fa
Currently the qedi_dbg_* family of functions can overrun the end of the source string if it is less than the destination buffer length because of the use of a fixed sized memcpy. Remove the memset/memcpy calls to nfunc and just use func instead as it is always a null terminated string.
--- drivers/scsi/qedi/qedi_dbg.c | 32 ++++++++------------------------ 1 file changed, 8 insertions(+), 24 deletions(-)
drivers/scsi/qedi/qedi_dbg.c +8 -24
@@ -16,10 +16,6 @@ qedi_dbg_err(struct qedi_dbg_ctx *qedi, const char *func, u32 line, {va_list va;struct va_format vaf; -char nfunc[32 ]; - -memset (nfunc,0 ,sizeof (nfunc)); -memcpy (nfunc, func,sizeof (nfunc) -1 );va_start (va, fmt);
@@ -28,9 +24,9 @@ qedi_dbg_err(struct qedi_dbg_ctx *qedi, const char *func, u32 line,if (likely (qedi) &&likely (qedi->pdev))pr_err ("[%s]:[%s:%d]:%d: %pV" ,dev_name (&qedi->pdev->dev), - nfunc, line, qedi->host_no, &vaf); + func, line, qedi->host_no, &vaf);else -pr_err ("[0000:00:00.0]:[%s:%d]: %pV" , nfunc, line, &vaf); +pr_err ("[0000:00:00.0]:[%s:%d]: %pV" , func, line, &vaf);va_end (va); }
@@ -41,10 +37,6 @@ qedi_dbg_warn(struct qedi_dbg_ctx *qedi, const char *func, u32 line, {va_list va;struct va_format vaf; -char nfunc[32 ]; - -memset (nfunc,0 ,sizeof (nfunc)); -memcpy (nfunc, func,sizeof (nfunc) -1 );va_start (va, fmt);
@@ -56,9 +48,9 @@ qedi_dbg_warn(struct qedi_dbg_ctx *qedi, const char *func, u32 line,if (likely (qedi) &&likely (qedi->pdev))pr_warn ("[%s]:[%s:%d]:%d: %pV" ,dev_name (&qedi->pdev->dev), - nfunc, line, qedi->host_no, &vaf); + func, line, qedi->host_no, &vaf);else -pr_warn ("[0000:00:00.0]:[%s:%d]: %pV" , nfunc, line, &vaf); +pr_warn ("[0000:00:00.0]:[%s:%d]: %pV" , func, line, &vaf); ret:va_end (va);
@@ -70,10 +62,6 @@ qedi_dbg_notice(struct qedi_dbg_ctx *qedi, const char *func, u32 line, {va_list va;struct va_format vaf; -char nfunc[32 ]; - -memset (nfunc,0 ,sizeof (nfunc)); -memcpy (nfunc, func,sizeof (nfunc) -1 );va_start (va, fmt);
@@ -85,10 +73,10 @@ qedi_dbg_notice(struct qedi_dbg_ctx *qedi, const char *func, u32 line,if (likely (qedi) &&likely (qedi->pdev))pr_notice ("[%s]:[%s:%d]:%d: %pV" , -dev_name (&qedi->pdev->dev), nfunc, line, +dev_name (&qedi->pdev->dev), func, line, qedi->host_no, &vaf);else -pr_notice ("[0000:00:00.0]:[%s:%d]: %pV" , nfunc, line, &vaf); +pr_notice ("[0000:00:00.0]:[%s:%d]: %pV" , func, line, &vaf); ret:va_end (va);
@@ -100,10 +88,6 @@ qedi_dbg_info(struct qedi_dbg_ctx *qedi, const char *func, u32 line, {va_list va;struct va_format vaf; -char nfunc[32 ]; - -memset (nfunc,0 ,sizeof (nfunc)); -memcpy (nfunc, func,sizeof (nfunc) -1 );va_start (va, fmt);
@@ -115,9 +99,9 @@ qedi_dbg_info(struct qedi_dbg_ctx *qedi, const char *func, u32 line,if (likely (qedi) &&likely (qedi->pdev))pr_info ("[%s]:[%s:%d]:%d: %pV" ,dev_name (&qedi->pdev->dev), - nfunc, line, qedi->host_no, &vaf); + func, line, qedi->host_no, &vaf);else -pr_info ("[0000:00:00.0]:[%s:%d]: %pV" , nfunc, line, &vaf); +pr_info ("[0000:00:00.0]:[%s:%d]: %pV" , func, line, &vaf); ret:va_end (va);
Signature · 1 line
2.20.1
Greg Kroah-Hartman
maintainerPATCH 54/115 scsi: qedi: remove set but not used variables cdev and udev
In reply to Greg Kroah-Hartman[ Upstream commit d0adee5d12752256ff0c87ad7f002f21fe49d618 ]
Fixes gcc '-Wunused-but-set-variable' warning:
drivers/scsi/qedi/qedi_iscsi.c: In function 'qedi_ep_connect':drivers/scsi/qedi/qedi_iscsi.c:813:23: warning: variable 'udev' set but not used [-Wunused-but-set-variable] drivers/scsi/qedi/qedi_iscsi.c:812:18: warning: variable 'cdev' set but not used [-Wunused-but-set-variable]
These have never been used since introduction.
--- drivers/scsi/qedi/qedi_iscsi.c | 4 ---- 1 file changed, 4 deletions(-)
drivers/scsi/qedi/qedi_iscsi.c +0 -4
@@ -809,8 +809,6 @@ qedi_ep_connect(struct Scsi_Host *shost, struct sockaddr *dst_addr,struct qedi_endpoint *qedi_ep;struct sockaddr_in *addr;struct sockaddr_in6 *addr6; -struct qed_dev *cdev =NULL ; -struct qedi_uio_dev *udev =NULL ;struct iscsi_path path_req;u32 msg_type =ISCSI_KEVENT_IF_DOWN ;u32 iscsi_cid =QEDI_CID_RESERVED ;
@@ -830,8 +828,6 @@ qedi_ep_connect(struct Scsi_Host *shost, struct sockaddr *dst_addr, } qedi =iscsi_host_priv (shost); - cdev = qedi->cdev; - udev = qedi->udev;if (test_bit (QEDI_IN_OFFLINE , &qedi->flags) ||test_bit (QEDI_IN_RECOVERY , &qedi->flags)) {
Signature · 1 line
2.20.1
Greg Kroah-Hartman
maintainerPATCH 55/115 scsi: lpfc: resolve lockdep warnings
In reply to Greg Kroah-Hartman[ Upstream commit e2a8be5696e706a2fce6edd11e5c74ce14cffec0 ]
There were a number of erroneous comments and incorrect older lockdep checks that were causing a number of warnings.
Resolve the following:
- Inconsistent lock state warnings in lpfc_nvme_info_show().
- Fixed comments and code on sequences where ring lock is now held instead of hbalock.
- Reworked calling sequences around lpfc_sli_iocbq_lookup(). Rather than locking prior to the routine and have routine guess on what lock, take the lock within the routine. The lockdep check becomes unnecessary.
- Fixed comments and removed erroneous hbalock checks.
--- drivers/scsi/lpfc/lpfc_attr.c | 5 ++- drivers/scsi/lpfc/lpfc_sli.c | 84 ++++++++++++++++++++++------------- 2 files changed, 56 insertions(+), 33 deletions(-)
drivers/scsi/lpfc/lpfc_attr.c +3 -2
@@ -159,6 +159,7 @@ lpfc_nvme_info_show(struct device *dev, struct device_attribute *attr,int i;int len =0 ;char tmp[LPFC_MAX_NVME_INFO_TMP_LEN ] = {0 }; +unsigned long iflags =0 ;if (!(vport->cfg_enable_fc4_type &LPFC_ENABLE_NVME )) { len =scnprintf (buf,PAGE_SIZE ,"NVME Disabled\n" );
@@ -357,11 +358,11 @@ lpfc_nvme_info_show(struct device *dev, struct device_attribute *attr,list_for_each_entry (ndlp, &vport->fc_nodes, nlp_listp) { nrport =NULL ; -spin_lock (&vport->phba->hbalock); +spin_lock_irqsave (&vport->phba->hbalock, iflags); rport =lpfc_ndlp_get_nrport (ndlp);if (rport) nrport = rport->remoteport; -spin_unlock (&vport->phba->hbalock); +spin_unlock_irqrestore (&vport->phba->hbalock, iflags);if (!nrport)continue ;
drivers/scsi/lpfc/lpfc_sli.c +53 -31
215 lines not on this page · raw message
Signature · 1 line
2.20.1
Greg Kroah-Hartman
maintainerPATCH 57/115 scsi: lpfc: add check for loss of ndlp when sending RRQ
In reply to Greg Kroah-Hartman[ Upstream commit c8cb261a072c88ca1aff0e804a30db4c7606521b ]
There was a missing qualification of a valid ndlp structure when calling to send an RRQ for an abort. Add the check.
--- drivers/scsi/lpfc/lpfc_els.c | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-)
drivers/scsi/lpfc/lpfc_els.c +4 -1
@@ -7338,7 +7338,10 @@ int lpfc_send_rrq(struct lpfc_hba *phba, struct lpfc_node_rrq *rrq) { struct lpfc_nodelist *ndlp = lpfc_findnode_did(rrq->vport, - rrq->nlp_DID); + rrq->nlp_DID); +if (!ndlp) +return 1 ; +if (lpfc_test_rrq_active (phba, ndlp, rrq->xritag))return lpfc_issue_els_rrq (rrq->vport, ndlp, rrq->nlp_DID, rrq);
Signature · 1 line
2.20.1
Greg Kroah-Hartman
maintainerPATCH 58/115 arm64: Print physical address of page table base in show_pte()
In reply to Greg Kroah-Hartman[ Upstream commit 48caebf7e1313eb9f0a06fe59a07ac05b38a5806 ]
When dumping the page table in response to an unexpected kernel page fault, we print the virtual (hashed) address of the page table base, but display physical addresses for everything else.
Make the page table dumping code in show_pte() consistent, by printing the page table base pointer as a physical address.
--- arch/arm64/mm/fault.c | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-)
arch/arm64/mm/fault.c +3 -2
@@ -171,9 +171,10 @@ void show_pte(unsigned long addr)return ; } -pr_alert ("%s pgtable: %luk pages, %u-bit VAs, pgdp = %p\n" , +pr_alert ("%s pgtable: %luk pages, %u-bit VAs, pgdp=%016lx\n" , mm == &init_mm ?"swapper" :"user" ,PAGE_SIZE /SZ_1K , - mm == &init_mm ?VA_BITS : (int ) vabits_user, mm->pgd); + mm == &init_mm ?VA_BITS : (int )vabits_user, + (unsigned long )virt_to_phys (mm->pgd)); pgdp =pgd_offset (mm, addr); pgd =READ_ONCE (*pgdp);pr_alert ("[%016lx] pgd=%016llx" , addr,pgd_val (pgd));
Signature · 1 line
2.20.1
Greg Kroah-Hartman
maintainerPATCH 59/115 net: macb: fix error format in dev_err()
In reply to Greg Kroah-Hartman[ Upstream commit f413cbb332a0b5251a790f396d0eb4ebcade5dec ]
Errors are negative numbers. Using %u shows them as very large positive numbers such as 4294967277 that don't make sense. Use the %d format instead, and get a much nicer -19.
--- drivers/net/ethernet/cadence/macb_main.c | 16 ++++++++-------- 1 file changed, 8 insertions(+), 8 deletions(-)
drivers/net/ethernet/cadence/macb_main.c +8 -8
@@ -3377,7 +3377,7 @@ static int macb_clk_init(struct platform_device *pdev, struct clk **pclk,if (!err) err = -ENODEV ; -dev_err (&pdev->dev,"failed to get macb_clk (%u)\n" , err); +dev_err (&pdev->dev,"failed to get macb_clk (%d)\n" , err);return err; }
@@ -3386,7 +3386,7 @@ static int macb_clk_init(struct platform_device *pdev, struct clk **pclk,if (!err) err = -ENODEV ; -dev_err (&pdev->dev,"failed to get hclk (%u)\n" , err); +dev_err (&pdev->dev,"failed to get hclk (%d)\n" , err);return err; }
@@ -3404,31 +3404,31 @@ static int macb_clk_init(struct platform_device *pdev, struct clk **pclk, err =clk_prepare_enable (*pclk);if (err) { -dev_err (&pdev->dev,"failed to enable pclk (%u)\n" , err); +dev_err (&pdev->dev,"failed to enable pclk (%d)\n" , err);return err; } err =clk_prepare_enable (*hclk);if (err) { -dev_err (&pdev->dev,"failed to enable hclk (%u)\n" , err); +dev_err (&pdev->dev,"failed to enable hclk (%d)\n" , err); goto err_disable_pclk; } err =clk_prepare_enable (*tx_clk);if (err) { -dev_err (&pdev->dev,"failed to enable tx_clk (%u)\n" , err); +dev_err (&pdev->dev,"failed to enable tx_clk (%d)\n" , err); goto err_disable_hclk; } err =clk_prepare_enable (*rx_clk);if (err) { -dev_err (&pdev->dev,"failed to enable rx_clk (%u)\n" , err); +dev_err (&pdev->dev,"failed to enable rx_clk (%d)\n" , err); goto err_disable_txclk; } err =clk_prepare_enable (*tsu_clk);if (err) { -dev_err (&pdev->dev,"failed to enable tsu_clk (%u)\n" , err); +dev_err (&pdev->dev,"failed to enable tsu_clk (%d)\n" , err); goto err_disable_rxclk; }
@@ -3902,7 +3902,7 @@ static int at91ether_clk_init(struct platform_device *pdev, struct clk **pclk, err =clk_prepare_enable (*pclk);if (err) { -dev_err (&pdev->dev,"failed to enable pclk (%u)\n" , err); +dev_err (&pdev->dev,"failed to enable pclk (%d)\n" , err);return err; }
Signature · 1 line
2.20.1
Greg Kroah-Hartman
maintainerPATCH 60/115 enetc: Fix NULL dma address unmap for Tx BD extensions
In reply to Greg Kroah-Hartman[ Upstream commit f4a0be84d73ec648628bf8094600ceb73cb6073f ]
For the unlikely case of TxBD extensions (i.e. ptp) the driver tries to unmap the tx_swbd corresponding to the extension, which is bogus as it has no buffer attached.
--- drivers/net/ethernet/freescale/enetc/enetc.c | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-)
drivers/net/ethernet/freescale/enetc/enetc.c +3 -1
@@ -313,7 +313,9 @@ static bool enetc_clean_tx_ring(struct enetc_bdr *tx_ring, int napi_budget)while (bds_to_clean && tx_frm_cnt <ENETC_DEFAULT_TX_WORK ) {bool is_eof = !!tx_swbd->skb; -enetc_unmap_tx_buff (tx_ring, tx_swbd); +if (likely (tx_swbd->dma)) +enetc_unmap_tx_buff (tx_ring, tx_swbd); +if (is_eof) {napi_consume_skb (tx_swbd->skb, napi_budget); tx_swbd->skb =NULL ;
Signature · 1 line
2.20.1
Greg Kroah-Hartman
maintainerPATCH 61/115 bpf, tcp: correctly handle DONT_WAIT flags and timeo == 0
In reply to Greg Kroah-Hartman[ Upstream commit 5fa2ca7c4a3fc176f31b495e1a704862d8188b53 ]
The tcp_bpf_wait_data() routine needs to check timeo != 0 before calling sk_wait_event() otherwise we may see unexpected stalls on receiver.
Arika did all the leg work here I just formatted, posted and ran a few tests.
--- net/ipv4/tcp_bpf.c | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-)
net/ipv4/tcp_bpf.c +4 -1
@@ -27,7 +27,10 @@ static int tcp_bpf_wait_data(struct sock *sk, struct sk_psock *psock, int flags, long timeo, int *err) {DEFINE_WAIT_FUNC (wait ,woken_wake_function ); -int ret; +int ret =0 ; + +if (!timeo) +return ret;add_wait_queue (sk_sleep (sk), &wait);sk_set_bit (SOCKWQ_ASYNC_WAITDATA , sk);
Signature · 1 line
2.20.1
Greg Kroah-Hartman
maintainerPATCH 62/115 arm64/mm: Inhibit huge-vmap with ptdump
In reply to Greg Kroah-Hartman[ Upstream commit 7ba36eccb3f83983a651efd570b4f933ecad1b5c ]
The arm64 ptdump code can race with concurrent modification of the kernel page tables. At the time this was added, this was sound as:
* Modifications to leaf entries could result in stale information being logged, but would not result in a functional problem.
* Boot time modifications to non-leaf entries (e.g. freeing of initmem) were performed when the ptdump code cannot be invoked.
* At runtime, modifications to non-leaf entries only occurred in the vmalloc region, and these were strictly additive, as intermediate entries were never freed.
However, since commit:
commit 324420bf91f6 ("arm64: add support for ioremap() block mappings")
... it has been possible to create huge mappings in the vmalloc area at runtime, and as part of this existing intermediate levels of table my be removed and freed.
It's possible for the ptdump code to race with this, and continue to walk tables which have been freed (and potentially poisoned or reallocated). As a result of this, the ptdump code may dereference bogus addresses, which could be fatal.
Since huge-vmap is a TLB and memory optimization, we can disable it when the runtime ptdump code is in use to avoid this problem.
--- arch/arm64/mm/mmu.c | 11 ++++++++--- 1 file changed, 8 insertions(+), 3 deletions(-)
arch/arm64/mm/mmu.c +8 -3
@@ -936,13 +936,18 @@ void *__init fixmap_remap_fdt(phys_addr_t dt_phys)int __init arch_ioremap_pud_supported (void ) { -/* only 4k granule supports level 1 block mappings */ -return IS_ENABLED (CONFIG_ARM64_4K_PAGES ); +/* +* Only 4k granule supports level 1 block mappings. +* SW table walks can't handle removal of intermediate entries. +*/ +return IS_ENABLED (CONFIG_ARM64_4K_PAGES ) && + !IS_ENABLED (CONFIG_ARM64_PTDUMP_DEBUGFS ); }int __init arch_ioremap_pmd_supported (void ) { -return 1 ; +/* See arch_ioremap_pud_supported() */ +return !IS_ENABLED (CONFIG_ARM64_PTDUMP_DEBUGFS ); }int pud_set_huge (pud_t *pudp,phys_addr_t phys,pgprot_t prot)
Signature · 1 line
2.20.1
Greg Kroah-Hartman
maintainerPATCH 63/115 tools/bpftool: move set_max_rlimit() before __bpf_object__open_xattr()
In reply to Greg Kroah-Hartman[ Upstream commit ac4e0e055fee5751c78bba1fc9ce508a6874d916 ]
For a host which has a lower rlimit for max locked memory (e.g., 64KB), the following error occurs in one of our production systems:
# /usr/sbin/bpftool prog load /paragon/pods/52877437/home/mark.o \
/sys/fs/bpf/paragon_mark_21 type cgroup/skb \
map idx 0 pinned /sys/fs/bpf/paragon_map_21
libbpf: Error in bpf_object__probe_name():Operation not permitted(1).
Couldn't load basic 'r0 = 0' BPF program.
Error: failed to open object fileThe reason is due to low locked memory during bpf_object__probe_name() which probes whether program name is supported in kernel or not during __bpf_object__open_xattr().
bpftool program load already tries to relax mlock rlimit before bpf_object__load(). Let us move set_max_rlimit() before __bpf_object__open_xattr(), which fixed the issue here.
--- tools/bpf/bpftool/prog.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
tools/bpf/bpftool/prog.c +2 -2
@@ -873,6 +873,8 @@ static int load_with_options(int argc, char **argv, bool first_prog_only) } } +set_max_rlimit (); + obj =__bpf_object__open_xattr (&attr, bpf_flags);if (IS_ERR_OR_NULL (obj)) {p_err ("failed to open object file" );
@@ -952,8 +954,6 @@ static int load_with_options(int argc, char **argv, bool first_prog_only) goto err_close_obj; } -set_max_rlimit (); - err =bpf_object__load (obj);if (err) {p_err ("failed to load object file" );
Signature · 1 line
2.20.1
Greg Kroah-Hartman
maintainerPATCH 64/115 selftests/bpf: fix bpf_get_current_task
In reply to Greg Kroah-Hartman[ Upstream commit 7ed4b4e60bb1dd3df7a45dfbde3a96efce9df7eb ]
Fix bpf_get_current_task() declaration.
--- tools/testing/selftests/bpf/bpf_helpers.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
tools/testing/selftests/bpf/bpf_helpers.h +1 -1
@@ -246,7 +246,7 @@ static int (*bpf_skb_change_type)(void *ctx, __u32 type) = (void *) BPF_FUNC_skb_change_type;static unsigned int (*bpf_get_hash_recalc)(void *ctx) = (void *) BPF_FUNC_get_hash_recalc; -static unsigned long long (*bpf_get_current_task)(void *ctx) = +static unsigned long long (*bpf_get_current_task)(void ) = (void *) BPF_FUNC_get_current_task;static int (*bpf_skb_change_tail)(void *ctx,__u32 len,__u64 flags) = (void *) BPF_FUNC_skb_change_tail;
Signature · 1 line
2.20.1
Greg Kroah-Hartman
maintainerPATCH 65/115 nvme-pci: Fix controller freeze wait disabling
In reply to Greg Kroah-Hartman[ Upstream commit e43269e6e5c49d7fec599e6bba71963935b0e4ba ]
If a controller disabling didn't start a freeze, don't wait for the operation to complete.
--- drivers/nvme/host/pci.c | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-)
drivers/nvme/host/pci.c +6 -6
@@ -2400,7 +2400,7 @@ static void nvme_pci_disable(struct nvme_dev *dev)static void nvme_dev_disable (struct nvme_dev *dev,bool shutdown) { -bool dead = true; +bool dead = true, freeze = false;struct pci_dev *pdev =to_pci_dev (dev->dev);mutex_lock (&dev->shutdown_lock);
@@ -2408,8 +2408,10 @@ static void nvme_dev_disable(struct nvme_dev *dev, bool shutdown)u32 csts =readl (dev->bar +NVME_REG_CSTS );if (dev->ctrl.state ==NVME_CTRL_LIVE || - dev->ctrl.state ==NVME_CTRL_RESETTING ) + dev->ctrl.state ==NVME_CTRL_RESETTING ) { + freeze = true;nvme_start_freeze (&dev->ctrl); + } dead = !!((csts &NVME_CSTS_CFS ) || !(csts &NVME_CSTS_RDY ) || pdev->error_state != pci_channel_io_normal); }
@@ -2418,10 +2420,8 @@ static void nvme_dev_disable(struct nvme_dev *dev, bool shutdown)* Give the controller a chance to complete all entered requests if * doing a safe shutdown. */ -if (!dead) { -if (shutdown) -nvme_wait_freeze_timeout (&dev->ctrl,NVME_IO_TIMEOUT ); - } +if (!dead && shutdown && freeze) +nvme_wait_freeze_timeout (&dev->ctrl,NVME_IO_TIMEOUT );nvme_stop_queues (&dev->ctrl);
Signature · 1 line
2.20.1
Greg Kroah-Hartman
maintainerPATCH 66/115 nvme: fix srcu locking on error return in nvme_get_ns_from_disk
In reply to Greg Kroah-Hartman[ Upstream commit 100c815cbd56480b3e31518475b04719c363614a ]
If we can't get a namespace don't leak the SRCU lock. nvme_ioctl was working around this, but nvme_pr_command wasn't handling this properly. Just do what callers would usually expect.
--- drivers/nvme/host/core.c | 13 +++++++++---- 1 file changed, 9 insertions(+), 4 deletions(-)
drivers/nvme/host/core.c +9 -4
@@ -1362,9 +1362,14 @@ static struct nvme_ns *nvme_get_ns_from_disk(struct gendisk *disk, {#ifdef CONFIG_NVME_MULTIPATH if (disk->fops == &nvme_ns_head_ops) { +struct nvme_ns *ns; + *head = disk->private_data; *srcu_idx =srcu_read_lock (&(*head)->srcu); -return nvme_find_path (*head); + ns =nvme_find_path (*head); +if (!ns) +srcu_read_unlock (&(*head)->srcu, *srcu_idx); +return ns; }#endif *head =NULL ;
@@ -1411,9 +1416,9 @@ static int nvme_ioctl(struct block_device *bdev, fmode_t mode, ns =nvme_get_ns_from_disk (bdev->bd_disk, &head, &srcu_idx);if (unlikely (!ns)) - ret = -EWOULDBLOCK ; -else - ret =nvme_ns_ioctl (ns, cmd, arg); +return -EWOULDBLOCK ; + + ret =nvme_ns_ioctl (ns, cmd, arg);nvme_put_ns_from_disk (head, srcu_idx);return ret; }
Signature · 1 line
2.20.1
Greg Kroah-Hartman
maintainerPATCH 67/115 nvme: remove the ifdef around nvme_nvm_ioctl
In reply to Greg Kroah-Hartman[ Upstream commit 3f98bcc58cd5f1e4668db289dcab771874cc0920 ]
We already have a proper stub if lightnvm is not enabled, so don't bother with the ifdef.
--- drivers/nvme/host/core.c | 2 -- 1 file changed, 2 deletions(-)
drivers/nvme/host/core.c +0 -2
@@ -1396,10 +1396,8 @@ static int nvme_ns_ioctl(struct nvme_ns *ns, unsigned cmd, unsigned long arg)case NVME_IOCTL_SUBMIT_IO :return nvme_submit_io (ns, (void __user *)arg);default : -#ifdef CONFIG_NVM if (ns->ndev)return nvme_nvm_ioctl (ns, cmd, arg); -#endif if (is_sed_ioctl (cmd))return sed_ioctl (ns->ctrl->opal_dev, cmd, (void __user *) arg);
Signature · 1 line
2.20.1
Greg Kroah-Hartman
maintainerPATCH 68/115 nvme: merge nvme_ns_ioctl into nvme_ioctl
In reply to Greg Kroah-Hartman[ Upstream commit 90ec611adcf20b96d0c2b7166497d53e4301a57f ]
Merge the two functions to make future changes a little easier.
--- drivers/nvme/host/core.c | 47 ++++++++++++++++++++-------------------- 1 file changed, 24 insertions(+), 23 deletions(-)
drivers/nvme/host/core.c +24 -23
@@ -1383,32 +1383,11 @@ static void nvme_put_ns_from_disk(struct nvme_ns_head *head, int idx)srcu_read_unlock (&head->srcu, idx); } -static int nvme_ns_ioctl (struct nvme_ns *ns,unsigned cmd,unsigned long arg) -{ -switch (cmd) { -case NVME_IOCTL_ID : -force_successful_syscall_return (); -return ns->head->ns_id; -case NVME_IOCTL_ADMIN_CMD : -return nvme_user_cmd (ns->ctrl,NULL , (void __user *)arg); -case NVME_IOCTL_IO_CMD : -return nvme_user_cmd (ns->ctrl, ns, (void __user *)arg); -case NVME_IOCTL_SUBMIT_IO : -return nvme_submit_io (ns, (void __user *)arg); -default : -if (ns->ndev) -return nvme_nvm_ioctl (ns, cmd, arg); -if (is_sed_ioctl (cmd)) -return sed_ioctl (ns->ctrl->opal_dev, cmd, - (void __user *) arg); -return -ENOTTY ; - } -} -static int nvme_ioctl (struct block_device *bdev,fmode_t mode,unsigned int cmd,unsigned long arg) {struct nvme_ns_head *head =NULL ; +void __user *argp = (void __user *)arg;struct nvme_ns *ns;int srcu_idx, ret;
@@ -1416,7 +1395,29 @@ static int nvme_ioctl(struct block_device *bdev, fmode_t mode,if (unlikely (!ns))return -EWOULDBLOCK ; - ret =nvme_ns_ioctl (ns, cmd, arg); +switch (cmd) { +case NVME_IOCTL_ID : +force_successful_syscall_return (); + ret = ns->head->ns_id; +break ; +case NVME_IOCTL_ADMIN_CMD : + ret =nvme_user_cmd (ns->ctrl,NULL , argp); +break ; +case NVME_IOCTL_IO_CMD : + ret =nvme_user_cmd (ns->ctrl, ns, argp); +break ; +case NVME_IOCTL_SUBMIT_IO : + ret =nvme_submit_io (ns, argp); +break ; +default : +if (ns->ndev) + ret =nvme_nvm_ioctl (ns, cmd, arg); +else if (is_sed_ioctl (cmd)) + ret =sed_ioctl (ns->ctrl->opal_dev, cmd, argp); +else + ret = -ENOTTY ; + } +nvme_put_ns_from_disk (head, srcu_idx);return ret; }
Signature · 1 line
2.20.1
Greg Kroah-Hartman
maintainerPATCH 70/115 nvme: fix memory leak for power latency tolerance
In reply to Greg Kroah-Hartman[ Upstream commit 510a405d945bc985abc513fafe45890cac34fafa ]
Unconditionally hide device pm latency tolerance when uninitializing the controller to ensure all qos resources are released so that we're not leaking this memory. This is safe to call if none were allocated in the first place, or were previously freed.
--- drivers/nvme/host/core.c | 1 + 1 file changed, 1 insertion(+)
drivers/nvme/host/core.c +1 -0
@@ -3699,6 +3699,7 @@ EXPORT_SYMBOL_GPL(nvme_start_ctrl);void nvme_uninit_ctrl (struct nvme_ctrl *ctrl) { +dev_pm_qos_hide_latency_tolerance (ctrl->device);cdev_device_del (&ctrl->cdev, ctrl->device); }EXPORT_SYMBOL_GPL (nvme_uninit_ctrl);
Signature · 1 line
2.20.1
Greg Kroah-Hartman
maintainerPATCH 44/115 ALSA: seq: Fix race of get-subscription call vs port-delete ioctls
In reply to Greg Kroah-Hartman[ Upstream commit 2eabc5ec8ab4d4748a82050dfcb994119b983750 ]
The snd_seq_ioctl_get_subscription() retrieves the port subscriber information as a pointer, while the object isn't protected, hence it may be deleted before the actual reference. This race was spotted by syzkaller and may lead to a UAF.
The fix is simply copying the data in the lookup function that performs in the rwsem to protect against the deletion.
--- sound/core/seq/seq_clientmgr.c | 10 ++-------- sound/core/seq/seq_ports.c | 13 ++++++++----- sound/core/seq/seq_ports.h | 5 +++-- 3 files changed, 13 insertions(+), 15 deletions(-)
sound/core/seq/seq_clientmgr.c +2 -8
@@ -1900,20 +1900,14 @@ static int snd_seq_ioctl_get_subscription(struct snd_seq_client *client,int result;struct snd_seq_client *sender =NULL ;struct snd_seq_client_port *sport =NULL ; -struct snd_seq_subscribers *p; result = -EINVAL ;if ((sender =snd_seq_client_use_ptr (subs->sender.client)) ==NULL ) goto __end;if ((sport =snd_seq_port_use_ptr (sender, subs->sender.port)) ==NULL ) goto __end; - p =snd_seq_port_get_subscription (&sport->c_src, &subs->dest); -if (p) { - result =0 ; - *subs = p->info; - }else - result = -ENOENT ; - + result =snd_seq_port_get_subscription (&sport->c_src, &subs->dest, + subs); __end:if (sport)snd_seq_port_unlock (sport);
sound/core/seq/seq_ports.c +8 -5
@@ -635,20 +635,23 @@ int snd_seq_port_disconnect(struct snd_seq_client *connector,/* get matched subscriber */ -struct snd_seq_subscribers *snd_seq_port_get_subscription (struct snd_seq_port_subs_info *src_grp, -struct snd_seq_addr *dest_addr) +int snd_seq_port_get_subscription (struct snd_seq_port_subs_info *src_grp, +struct snd_seq_addr *dest_addr, +struct snd_seq_port_subscribe *subs) { -struct snd_seq_subscribers *s, *found =NULL ; +struct snd_seq_subscribers *s; +int err = -ENOENT ;down_read (&src_grp->list_mutex);list_for_each_entry (s, &src_grp->list_head, src_list) {if (addr_match (dest_addr, &s->info.dest)) { - found = s; + *subs = s->info; + err =0 ;break ; } }up_read (&src_grp->list_mutex); -return found; +return err; }/*
sound/core/seq/seq_ports.h +3 -2
@@ -135,7 +135,8 @@ int snd_seq_port_subscribe(struct snd_seq_client_port *port, struct snd_seq_port_subscribe *info);/* get matched subscriber */ -struct snd_seq_subscribers *snd_seq_port_get_subscription (struct snd_seq_port_subs_info *src_grp, -struct snd_seq_addr *dest_addr); +int snd_seq_port_get_subscription (struct snd_seq_port_subs_info *src_grp, +struct snd_seq_addr *dest_addr, +struct snd_seq_port_subscribe *subs);#endif
Signature · 1 line
2.20.1
Greg Kroah-Hartman
maintainerPATCH 71/115 platform/x86: pmc_atom: Add Lex 3I380D industrial PC to critclk_systems DMI table
In reply to Greg Kroah-Hartman[ Upstream commit 3d0818f5eba80fbe4c0addbfe6ddb2d19dc82cd4 ]
The Lex 3I380D industrial PC has 4 ethernet controllers on board which need pmc_plt_clk0 - 3 to function, add it to the critclk_systems DMI table, so that drivers/clk/x86/clk-pmc-atom.c will mark the clocks as CLK_CRITICAL and they will not get turned off.
--- drivers/platform/x86/pmc_atom.c | 9 +++++++++ 1 file changed, 9 insertions(+)
drivers/platform/x86/pmc_atom.c +9 -0
@@ -398,12 +398,21 @@ static int pmc_dbgfs_register(struct pmc_dev *pmc)*/ static const struct dmi_system_id critclk_systems[] = { { +/* pmc_plt_clk0 is used for an external HSIC USB HUB */ .ident ="MPL CEC1x" , .matches = {DMI_MATCH (DMI_SYS_VENDOR ,"MPL AG" ),DMI_MATCH (DMI_PRODUCT_NAME ,"CEC10 Family" ), }, }, + { +/* pmc_plt_clk0 - 3 are used for the 4 ethernet controllers */ + .ident ="Lex 3I380D" , + .matches = { +DMI_MATCH (DMI_SYS_VENDOR ,"Lex BayTrail" ), +DMI_MATCH (DMI_PRODUCT_NAME ,"3I380D" ), + }, + }, {/*sentinel*/ } };
Signature · 1 line
2.20.1
Greg Kroah-Hartman
maintainerPATCH 72/115 platform/x86: pmc_atom: Add several Beckhoff Automation boards to critclk_systems DMI table
In reply to Greg Kroah-Hartman[ Upstream commit d6423bd03031c020121da26c41a26bd5cc6d0da3 ]
There are several Beckhoff Automation industrial PC boards which use pmc_plt_clk* clocks for ethernet controllers. This adds affected boards to critclk_systems DMI table so the clocks are marked as CLK_CRITICAL and not turned off.
--- drivers/platform/x86/pmc_atom.c | 24 ++++++++++++++++++++++++ 1 file changed, 24 insertions(+)
drivers/platform/x86/pmc_atom.c +24 -0
@@ -413,6 +413,30 @@ static const struct dmi_system_id critclk_systems[] = { DMI_MATCH(DMI_PRODUCT_NAME, "3I380D"), }, }, + { + /* pmc_plt_clk* - are used for ethernet controllers */ + .ident = "Beckhoff CB3163", + .matches = { + DMI_MATCH(DMI_SYS_VENDOR, "Beckhoff Automation"), + DMI_MATCH(DMI_BOARD_NAME, "CB3163"), + }, + }, + { + /* pmc_plt_clk* - are used for ethernet controllers */ + .ident = "Beckhoff CB6263", + .matches = { + DMI_MATCH(DMI_SYS_VENDOR, "Beckhoff Automation"), + DMI_MATCH(DMI_BOARD_NAME, "CB6263"), + }, + }, + { + /* pmc_plt_clk* - are used for ethernet controllers */ + .ident = "Beckhoff CB6363", + .matches = { + DMI_MATCH(DMI_SYS_VENDOR, "Beckhoff Automation"), + DMI_MATCH(DMI_BOARD_NAME, "CB6363"), + }, + }, { /*sentinel*/ } };
Signature · 1 line
2.20.1
Greg Kroah-Hartman
maintainerPATCH 74/115 scsi: bnx2fc: fix incorrect cast to u64 on shift operation
In reply to Greg Kroah-Hartman[ Upstream commit d0c0d902339249c75da85fd9257a86cbb98dfaa5 ]
Currently an int is being shifted and the result is being cast to a u64 which leads to undefined behaviour if the shift is more than 31 bits. Fix this by casting the integer value 1 to u64 before the shift operation.
Addresses-Coverity: ("Bad shift operation")
--- drivers/scsi/bnx2fc/bnx2fc_hwi.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/scsi/bnx2fc/bnx2fc_hwi.c +1 -1
@@ -830,7 +830,7 @@ ret_err_rqe: ((u64 )err_entry->data.err_warn_bitmap_hi <<32 ) | (u64 )err_entry->data.err_warn_bitmap_lo;for (i =0 ; i <BNX2FC_NUM_ERR_BITS ; i++) { -if (err_warn_bit_map & (u64) (1 << i)) { +if (err_warn_bit_map & ((u64 )1 << i)) { err_warn = i;break ; }
Signature · 1 line
2.20.1
Greg Kroah-Hartman
maintainerPATCH 73/115 scsi: myrs: Fix uninitialized variable
In reply to Greg Kroah-Hartman[ Upstream commit 41552199b5518fe26bee0829a28dd1880441b430 ]
drivers/scsi/myrs.c: In function 'myrs_log_event':drivers/scsi/myrs.c:821:24: warning: 'sshdr.sense_key' may be used uninitialized in this function [-Wmaybe-uninitialized]
struct scsi_sense_hdr sshdr;
If ev->ev_code is not 0x1C, sshdr.sense_key may be used uninitialized. Fix this by initializing variable 'sshdr' to 0.
--- drivers/scsi/myrs.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/scsi/myrs.c +1 -1
@@ -818,7 +818,7 @@ static void myrs_log_event(struct myrs_hba *cs, struct myrs_event *ev)unsigned char ev_type, *ev_msg;struct Scsi_Host *shost = cs->host;struct scsi_device *sdev; -struct scsi_sense_hdr sshdr; +struct scsi_sense_hdr sshdr = {0 };unsigned char sense_info[4 ];unsigned char cmd_specific[4 ];
Signature · 1 line
2.20.1
Greg Kroah-Hartman
maintainerPATCH 75/115 drm/amdgpu: keep stolen memory on picasso
In reply to Greg Kroah-Hartman[ Upstream commit 379109351f4f6f2405cf54e7a296055f589c3ad1 ]
otherwise screen corrupts during modprobe.
--- drivers/gpu/drm/amd/amdgpu/gmc_v9_0.c | 1 + 1 file changed, 1 insertion(+)
drivers/gpu/drm/amd/amdgpu/gmc_v9_0.c +1 -0
@@ -715,6 +715,7 @@ static bool gmc_v9_0_keep_stolen_memory(struct amdgpu_device *adev)case CHIP_VEGA10 :return true;case CHIP_RAVEN : +return (adev->pdev->device ==0x15d8 );case CHIP_VEGA12 :case CHIP_VEGA20 :default :
Signature · 1 line
2.20.1
Greg Kroah-Hartman
maintainerPATCH 77/115 selftests: fib_rule_tests: fix local IPv4 address typo
In reply to Greg Kroah-Hartman[ Upstream commit fc82d93e57e3d41f79eff19031588b262fc3d0b6 ]
The IPv4 testing address are all in 192.51.100.0 subnet. It doesn't make sense to set a 198.51.100.1 local address. Should be a typo.
--- tools/testing/selftests/net/fib_rule_tests.sh | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
tools/testing/selftests/net/fib_rule_tests.sh +1 -1
@@ -55,7 +55,7 @@ setup() $IP link add dummy0 type dummy $IP link set dev dummy0 up - $IP address add 198.51.100.1/24 dev dummy0 + $IP address add 192.51.100.1/24 dev dummy0 $IP -6 address add 2001:db8:1::1/64 dev dummy0 set +e
Signature · 1 line
2.20.1
Greg Kroah-Hartman
maintainerPATCH 78/115 selftests/timers: Add missing fflush(stdout) calls
In reply to Greg Kroah-Hartman[ Upstream commit fe48319243a626c860fd666ca032daacc2ba84a5 ]
When running under a pipe, some timer tests would not report output in real-time because stdout flushes were missing after printf()s that lacked a newline. This adds them to restore real-time status output that humans can enjoy.
--- tools/testing/selftests/timers/adjtick.c | 1 + tools/testing/selftests/timers/leapcrash.c | 1 + tools/testing/selftests/timers/mqueue-lat.c | 1 + tools/testing/selftests/timers/nanosleep.c | 1 + tools/testing/selftests/timers/nsleep-lat.c | 1 + tools/testing/selftests/timers/raw_skew.c | 1 + tools/testing/selftests/timers/set-tai.c | 1 + tools/testing/selftests/timers/set-tz.c | 2 ++ tools/testing/selftests/timers/threadtest.c | 1 + tools/testing/selftests/timers/valid-adjtimex.c | 2 ++ 10 files changed, 12 insertions(+)
tools/testing/selftests/timers/adjtick.c +1 -0
@@ -136,6 +136,7 @@ int check_tick_adj(long tickval) eppm =get_ppm_drift ();printf ("%lld usec, %lld ppm" , systick + (systick * eppm /MILLION ), eppm); +fflush (stdout); tx1.modes =0 ;adjtimex (&tx1);
tools/testing/selftests/timers/leapcrash.c +1 -0
@@ -101,6 +101,7 @@ int main(void) }clear_time_state ();printf ("." ); +fflush (stdout); }printf ("[OK]\n" );return ksft_exit_pass ();
tools/testing/selftests/timers/mqueue-lat.c +1 -0
@@ -102,6 +102,7 @@ int main(int argc, char **argv)int ret;printf ("Mqueue latency : " ); +fflush (stdout); ret =mqueue_lat_test ();if (ret <0 ) {
tools/testing/selftests/timers/nanosleep.c +1 -0
@@ -142,6 +142,7 @@ int main(int argc, char **argv)continue ;printf ("Nanosleep %-31s " ,clockstring (clockid)); +fflush (stdout); length =10 ;while (length <= (NSEC_PER_SEC *10 )) {
tools/testing/selftests/timers/nsleep-lat.c +1 -0
@@ -155,6 +155,7 @@ int main(int argc, char **argv)continue ;printf ("nsleep latency %-26s " ,clockstring (clockid)); +fflush (stdout); length =10 ;while (length <= (NSEC_PER_SEC *10 )) {
tools/testing/selftests/timers/raw_skew.c +1 -0
@@ -112,6 +112,7 @@ int main(int argv, char **argc)printf ("WARNING: ADJ_OFFSET in progress, this will cause inaccurate results\n" );printf ("Estimating clock drift: " ); +fflush (stdout);sleep (120 );get_monotonic_and_raw (&mon, &raw);
tools/testing/selftests/timers/set-tai.c +1 -0
@@ -55,6 +55,7 @@ int main(int argc, char **argv)printf ("tai offset started at %i\n" , ret);printf ("Checking tai offsets can be properly set: " ); +fflush (stdout);for (i =1 ; i <=60 ; i++) { ret =set_tai (i); ret =get_tai ();
tools/testing/selftests/timers/set-tz.c +2 -0
@@ -65,6 +65,7 @@ int main(int argc, char **argv)printf ("tz_minuteswest started at %i, dst at %i\n" , min, dst);printf ("Checking tz_minuteswest can be properly set: " ); +fflush (stdout);for (i =-15 *60 ; i <15 *60 ; i +=30 ) { ret =set_tz (i, dst); ret =get_tz_min ();
@@ -76,6 +77,7 @@ int main(int argc, char **argv)printf ("[OK]\n" );printf ("Checking invalid tz_minuteswest values are caught: " ); +fflush (stdout);if (!set_tz (-15 *60 -1 , dst)) {printf ("[FAILED] %i didn't return failure!\n" ,-15 *60 -1 );
tools/testing/selftests/timers/threadtest.c +1 -0
@@ -163,6 +163,7 @@ int main(int argc, char **argv)strftime (buf,255 ,"%a, %d %b %Y %T %z" ,localtime (&start));printf ("%s\n" , buf);printf ("Testing consistency with %i threads for %ld seconds: " , thread_count, runtime); +fflush (stdout);/* spawn */ for (i =0 ; i < thread_count; i++)
tools/testing/selftests/timers/valid-adjtimex.c +2 -0
@@ -123,6 +123,7 @@ int validate_freq(void)/* Set the leap second insert flag */ printf ("Testing ADJ_FREQ... " ); +fflush (stdout);for (i =0 ; i <NUM_FREQ_VALID ; i++) { tx.modes =ADJ_FREQUENCY ; tx.freq = valid_freq[i];
@@ -250,6 +251,7 @@ int set_bad_offset(long sec, long usec, int use_nano)int validate_set_offset (void ) {printf ("Testing ADJ_SETOFFSET... " ); +fflush (stdout);/* Test valid values */ if (set_offset (NSEC_PER_SEC -1 ,1 ))
Signature · 1 line
2.20.1
Greg Kroah-Hartman
maintainerPATCH 79/115 tracing: Prevent hist_field_var_ref() from accessing NULL tracing_map_elts
In reply to Greg Kroah-Hartman[ Upstream commit 55267c88c003a3648567beae7c90512d3e2ab15e ]
hist_field_var_ref() is an implementation of hist_field_fn_t(), which can be called with a null tracing_map_elt elt param when assembling a key in event_hist_trigger().
In the case of hist_field_var_ref() this doesn't make sense, because a variable can only be resolved by looking it up using an already assembled key i.e. a variable can't be used to assemble a key since the key is required in order to access the variable.
Upper layers should prevent the user from constructing a key using a variable in the first place, but in case one slips through, it shouldn't cause a NULL pointer dereference. Also if one does slip through, we want to know about it, so emit a one-time warning in that case.
--- kernel/trace/trace_events_hist.c | 3 +++ 1 file changed, 3 insertions(+)
kernel/trace/trace_events_hist.c +3 -0
@@ -1815,6 +1815,9 @@ static u64 hist_field_var_ref(struct hist_field *hist_field,struct hist_elt_data *elt_data;u64 var_val =0 ; +if (WARN_ON_ONCE (!elt)) +return var_val; + elt_data = elt->private_data; var_val = elt_data->var_ref_vals[hist_field->var_ref_idx];
Signature · 1 line
2.20.1
Greg Kroah-Hartman
maintainerPATCH 80/115 usbnet: ipheth: fix racing condition
In reply to Greg Kroah-Hartman[ Upstream commit 94d250fae48e6f873d8362308f5c4d02cd1b1fd2 ]
Fix a racing condition in ipheth.c that can lead to slow performance.
Bug: In ipheth_tx(), netif_wake_queue() may be called on the callback ipheth_sndbulk_callback(), _before_ netif_stop_queue() is called. When this happens, the queue is stopped longer than it needs to be, thus reducing network performance.
Fix: Move netif_stop_queue() in front of usb_submit_urb(). Now the order is always correct. In case, usb_submit_urb() fails, the queue is woken up again as callback will not fire.
Testing: This racing condition is usually not noticeable, as it has to occur very frequently to slowdown the network. The callback from the USB is usually triggered slow enough, so the situation does not appear. However, on a Ubuntu Linux on VMWare Workstation, running on Windows 10, the we loose the race quite often and the following speedup can be noticed:
Without this patch: Download: 4.10 Mbit/s, Upload: 4.01 Mbit/s With this patch: Download: 36.23 Mbit/s, Upload: 17.61 Mbit/s
--- drivers/net/usb/ipheth.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-)
drivers/net/usb/ipheth.c +2 -1
@@ -437,17 +437,18 @@ static int ipheth_tx(struct sk_buff *skb, struct net_device *net) dev); dev->tx_urb->transfer_flags |=URB_NO_TRANSFER_DMA_MAP ; +netif_stop_queue (net); retval =usb_submit_urb (dev->tx_urb,GFP_ATOMIC );if (retval) {dev_err (&dev->intf->dev,"%s: usb_submit_urb: %d\n" , __func__, retval); dev->net->stats.tx_errors++;dev_kfree_skb_any (skb); +netif_wake_queue (net); }else { dev->net->stats.tx_packets++; dev->net->stats.tx_bytes += skb->len;dev_consume_skb_any (skb); -netif_stop_queue (net); }return NETDEV_TX_OK ;
Signature · 1 line
2.20.1
Greg Kroah-Hartman
maintainerPATCH 82/115 tools/io_uring: fix Makefile for pthread library link
In reply to Greg Kroah-Hartman[ Upstream commit 486f069253c3c738dec62daeb16f7232b2cca065 ]
Currently fails with:
io_uring-bench.o: In function `main':/home/axboe/git/linux-block/tools/io_uring/io_uring-bench.c:560: undefined reference to pthread_create' /home/axboe/git/linux-block/tools/io_uring/io_uring-bench.c:588: undefined reference to pthread_join'
collect2: error: ld returned 1 exit status
Makefile:11: recipe for target 'io_uring-bench' failed
make: *** [io_uring-bench] Error 1
Move -lpthread to the end.
--- tools/io_uring/Makefile | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
tools/io_uring/Makefile +1 -1
@@ -8,7 +8,7 @@ all: io_uring-cp io_uring-bench $(CC) $(CFLAGS) -o $@ $^ io_uring-bench: syscall.o io_uring-bench.o - $(CC) $(CFLAGS) $(LDLIBS) -o $@ $^ + $(CC) $(CFLAGS) -o $@ $^ $(LDLIBS) io_uring-cp: setup.o syscall.o queue.o
Signature · 1 line
2.20.1
Greg Kroah-Hartman
maintainerPATCH 81/115 nvme-pci: use blk-mq mapping for unmanaged irqs
In reply to Greg Kroah-Hartman[ Upstream commit cb9e0e5006064a807b5d722c7e3c42f307193792 ]
If a device is providing a single IRQ vector, the IO queue will share that vector with the admin queue. This is an unmanaged vector, so does not have a valid PCI IRQ affinity. Avoid trying to extract a managed affinity in this case and let blk-mq set up the cpu:queue mapping instead. Otherwise we'd hit the following warning when the device is using MSI:
WARNING: CPU: 4 PID: 7 at drivers/pci/msi.c:1272 pci_irq_get_affinity+0x66/0x80 Modules linked in: nvme nvme_core serio_raw CPU: 4 PID: 7 Comm: kworker/u16:0 Tainted: G W 5.2.0-rc1+ #494 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.12.1-0-ga5cab58e9a3f-prebuilt.qemu.org 04/01/2014 Workqueue: nvme-reset-wq nvme_reset_work [nvme] RIP: 0010:pci_irq_get_affinity+0x66/0x80 Code: 0b 31 c0 c3 83 e2 10 48 c7 c0 b0 83 35 91 74 2a 48 8b 87 d8 03 00 00 48 85 c0 74 0e 48 8b 50 30 48 85 d2 74 05 39 70 14 77 05 <0f> 0b 31 c0 c3 48 63 f6 48 8d 04 76 48 8d 04 c2 f3 c3 48 8b 40 30 RSP: 0000:ffffb5abc01d3cc8 EFLAGS: 00010246 RAX: ffff9536786a39c0 RBX: 0000000000000000 RCX: 0000000000000080 RDX: 0000000000000000 RSI: 0000000000000000 RDI: ffff9536781ed000 RBP: ffff95367346a008 R08: ffff95367d43f080 R09: ffff953678c07800 R10: ffff953678164800 R11: 0000000000000000 R12: 0000000000000000 R13: ffff9536781ed000 R14: 00000000ffffffff R15: ffff95367346a008 FS: 0000000000000000(0000) GS:ffff95367d400000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007fdf814a3ff0 CR3: 000000001a20f000 CR4: 00000000000006e0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Call Trace: blk_mq_pci_map_queues+0x37/0xd0 nvme_pci_map_queues+0x80/0xb0 [nvme] blk_mq_alloc_tag_set+0x133/0x2f0 nvme_reset_work+0x105d/0x1590 [nvme] process_one_work+0x291/0x530 worker_thread+0x218/0x3d0 ? process_one_work+0x530/0x530 kthread+0x111/0x130 ? kthread_park+0x90/0x90 ret_from_fork+0x1f/0x30 ---[ end trace 74587339d93c83c0 ]---
--- drivers/nvme/host/pci.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/nvme/host/pci.c +1 -1
@@ -500,7 +500,7 @@ static int nvme_pci_map_queues(struct blk_mq_tag_set *set)* affinity), so use the regular blk-mq cpu mapping */ map->queue_offset = qoff; -if (i !=HCTX_TYPE_POLL ) +if (i !=HCTX_TYPE_POLL && offset)blk_mq_pci_map_queues (map,to_pci_dev (dev->dev), offset);else blk_mq_map_queues (map);
Signature · 1 line
2.20.1
Greg Kroah-Hartman
maintainerPATCH 83/115 KVM: arm/arm64: Move cc/it checks under hyps Makefile to avoid instrumentation
In reply to Greg Kroah-Hartman[ Upstream commit 623e1528d4090bd1abaf93ec46f047dee9a6fb32 ]
KVM has helpers to handle the condition codes of trapped aarch32 instructions. These are marked __hyp_text and used from HYP, but they aren't built by the 'hyp' Makefile, which has all the runes to avoid ASAN and KCOV instrumentation.
Move this code to a new hyp/aarch32.c to avoid a hyp-panic when starting an aarch32 guest on a host built with the ASAN/KCOV debug options.
--- arch/arm/kvm/hyp/Makefile | 1 + arch/arm64/kvm/hyp/Makefile | 1 + virt/kvm/arm/aarch32.c | 121 -------------------------------- virt/kvm/arm/hyp/aarch32.c | 136 ++++++++++++++++++++++++++++++++++++ 4 files changed, 138 insertions(+), 121 deletions(-) create mode 100644 virt/kvm/arm/hyp/aarch32.c
arch/arm/kvm/hyp/Makefile +1 -0
@@ -11,6 +11,7 @@ CFLAGS_ARMV7VE :=$(call cc-option, -march=armv7ve) obj-$(CONFIG_KVM_ARM_HOST) += $(KVM)/arm/hyp/vgic-v3-sr.o obj-$(CONFIG_KVM_ARM_HOST) += $(KVM)/arm/hyp/timer-sr.o +obj-$(CONFIG_KVM_ARM_HOST) += $(KVM)/arm/hyp/aarch32.o obj-$(CONFIG_KVM_ARM_HOST) += tlb.o obj-$(CONFIG_KVM_ARM_HOST) += cp15-sr.o
arch/arm64/kvm/hyp/Makefile +1 -0
@@ -10,6 +10,7 @@ KVM=../../../../virt/kvm obj-$(CONFIG_KVM_ARM_HOST) += $(KVM)/arm/hyp/vgic-v3-sr.o obj-$(CONFIG_KVM_ARM_HOST) += $(KVM)/arm/hyp/timer-sr.o +obj-$(CONFIG_KVM_ARM_HOST) += $(KVM)/arm/hyp/aarch32.o obj-$(CONFIG_KVM_ARM_HOST) += vgic-v2-cpuif-proxy.o obj-$(CONFIG_KVM_ARM_HOST) += sysreg-sr.o
virt/kvm/arm/aarch32.c +0 -121
127 lines not on this page · raw message
virt/kvm/arm/hyp/aarch32.c new file +136 -0
136 lines not on this page · raw message
Signature · 1 line
2.20.1
Greg Kroah-Hartman
maintainerPATCH 85/115 KVM: selftests: Fix a condition in test_hv_cpuid()
In reply to Greg Kroah-Hartman[ Upstream commit be7fcf1d1701a5266dd36eab4978476f63d1bd57 ]
The code is trying to check that all the padding is zeroed out and it does this:
entry->padding[0] == entry->padding[1] == entry->padding[2] == 0
Assume everything is zeroed correctly, then the first comparison is true, the next comparison is false and false is equal to zero so the overall condition is true. This bug doesn't affect run time very badly, but the code should instead just check that all three paddings are zero individually.
Also the error message was copy and pasted from an earlier error and it wasn't correct.
--- tools/testing/selftests/kvm/x86_64/hyperv_cpuid.c | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-)
tools/testing/selftests/kvm/x86_64/hyperv_cpuid.c +2 -3
@@ -58,9 +58,8 @@ static void test_hv_cpuid(struct kvm_cpuid2 *hv_cpuid_entries,TEST_ASSERT (entry->flags ==0 ,".flags field should be zero" ); -TEST_ASSERT (entry->padding[0 ] == entry->padding[1 ] - == entry->padding[2 ] ==0 , -".index field should be zero" ); +TEST_ASSERT (!entry->padding[0 ] && !entry->padding[1 ] && + !entry->padding[2 ],"padding should be zero" );/* * If needed for debug:
Signature · 1 line
2.20.1
Greg Kroah-Hartman
maintainerPATCH 86/115 kvm: vmx: Fix -Wmissing-prototypes warnings
In reply to Greg Kroah-Hartman[ Upstream commit 4d259965655c92053f3255aca14d81aab1e21219 ]
We get a warning when build kernel W=1:arch/x86/kvm/vmx/vmx.c:6365:6: warning: no previous prototype for ‘vmx_update_host_rsp’ [-Wmissing-prototypes]
void vmx_update_host_rsp(struct vcpu_vmx *vmx, unsigned long host_rsp)
Add the missing declaration to fix this.
--- arch/x86/kvm/vmx/vmx.h | 1 + 1 file changed, 1 insertion(+)
arch/x86/kvm/vmx/vmx.h +1 -0
@@ -314,6 +314,7 @@ void vmx_set_nmi_mask(struct kvm_vcpu *vcpu, bool masked);void vmx_set_virtual_apic_mode (struct kvm_vcpu *vcpu);struct shared_msr_entry *find_msr_entry (struct vcpu_vmx *vmx,u32 msr);void pt_update_intercept_for_msr (struct vcpu_vmx *vmx); +void vmx_update_host_rsp (struct vcpu_vmx *vmx,unsigned long host_rsp);#define POSTED_INTR_ON 0#define POSTED_INTR_SN 1
Signature · 1 line
2.20.1
Greg Kroah-Hartman
maintainerPATCH 87/115 KVM: LAPIC: Fix lapic_timer_advance_ns parameter overflow
In reply to Greg Kroah-Hartman[ Upstream commit 0e6edceb8f18a4e31526d83e6099fef1f29c3af5 ]
After commit c3941d9e0 (KVM: lapic: Allow user to disable adaptive tuning of timer advancement), '-1' enables adaptive tuning starting from default advancment of 1000ns. However, we should expose an int instead of an overflow uint module parameter.
Before patch:
/sys/module/kvm/parameters/lapic_timer_advance_ns:4294967295
After patch:
/sys/module/kvm/parameters/lapic_timer_advance_ns:-1
--- arch/x86/kvm/x86.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
arch/x86/kvm/x86.c +1 -1
@@ -143,7 +143,7 @@ module_param(tsc_tolerance_ppm, uint, S_IRUGO | S_IWUSR);* tuning, i.e. allows priveleged userspace to set an exact advancement time. */ static int __read_mostly lapic_timer_advance_ns =-1 ; -module_param (lapic_timer_advance_ns, uint,S_IRUGO |S_IWUSR ); +module_param (lapic_timer_advance_ns, int,S_IRUGO |S_IWUSR );static bool __read_mostly vector_hashing = true;module_param (vector_hashing, bool,S_IRUGO );
Signature · 1 line
2.20.1
Greg Kroah-Hartman
maintainerPATCH 47/115 f2fs: fix to avoid accessing xattr across the boundary
In reply to Greg Kroah-Hartman[ Upstream commit 2777e654371dd4207a3a7f4fb5fa39550053a080 ]
When we traverse xattr entries via __find_xattr(),
if the raw filesystem content is faked or any hardware failure occurs, out-of-bound error can be detected by KASAN.
Fix the issue by introducing boundary check.
[ 38.402878] c7 1827 BUG: KASAN: slab-out-of-bounds in f2fs_getxattr+0x518/0x68c [ 38.402891] c7 1827 Read of size 4 at addr ffffffc0b6fb35dc by task [ 38.402935] c7 1827 Call trace: [ 38.402952] c7 1827 [<ffffff900809003c>] dump_backtrace+0x0/0x6bc [ 38.402966] c7 1827 [<ffffff9008090030>] show_stack+0x20/0x2c [ 38.402981] c7 1827 [<ffffff900871ab10>] dump_stack+0xfc/0x140 [ 38.402995] c7 1827 [<ffffff9008325c40>] print_address_description+0x80/0x2d8 [ 38.403009] c7 1827 [<ffffff900832629c>] kasan_report_error+0x198/0x1fc [ 38.403022] c7 1827 [<ffffff9008326104>] kasan_report_error+0x0/0x1fc [ 38.403037] c7 1827 [<ffffff9008325000>] __asan_load4+0x1b0/0x1b8 [ 38.403051] c7 1827 [<ffffff90085fcc44>] f2fs_getxattr+0x518/0x68c [ 38.403066] c7 1827 [<ffffff90085fc508>] f2fs_xattr_generic_get+0xb0/0xd0 [ 38.403080] c7 1827 [<ffffff9008395708>] __vfs_getxattr+0x1f4/0x1fc [ 38.403096] c7 1827 [<ffffff9008621bd0>] inode_doinit_with_dentry+0x360/0x938 [ 38.403109] c7 1827 [<ffffff900862d6cc>] selinux_d_instantiate+0x2c/0x38 [ 38.403123] c7 1827 [<ffffff900861b018>] security_d_instantiate+0x68/0x98 [ 38.403136] c7 1827 [<ffffff9008377db8>] d_splice_alias+0x58/0x348 [ 38.403149] c7 1827 [<ffffff900858d16c>] f2fs_lookup+0x608/0x774 [ 38.403163] c7 1827 [<ffffff900835eacc>] lookup_slow+0x1e0/0x2cc [ 38.403177] c7 1827 [<ffffff9008367fe0>] walk_component+0x160/0x520 [ 38.403190] c7 1827 [<ffffff9008369ef4>] path_lookupat+0x110/0x2b4 [ 38.403203] c7 1827 [<ffffff900835dd38>] filename_lookup+0x1d8/0x3a8 [ 38.403216] c7 1827 [<ffffff900835eeb0>] user_path_at_empty+0x54/0x68 [ 38.403229] c7 1827 [<ffffff9008395f44>] SyS_getxattr+0xb4/0x18c [ 38.403241] c7 1827 [<ffffff9008084200>] el0_svc_naked+0x34/0x38
--- fs/f2fs/xattr.c | 36 +++++++++++++++++++++++++++--------- fs/f2fs/xattr.h | 2 ++ 2 files changed, 29 insertions(+), 9 deletions(-)
fs/f2fs/xattr.c +27 -9
@@ -202,12 +202,17 @@ static inline const struct xattr_handler *f2fs_xattr_handler(int index)return handler; } -static struct f2fs_xattr_entry *__find_xattr (void *base_addr,int index, -size_t len,const char *name) +static struct f2fs_xattr_entry *__find_xattr (void *base_addr, +void *last_base_addr,int index, +size_t len,const char *name) {struct f2fs_xattr_entry *entry;list_for_each_xattr (entry, base_addr) { +if ((void *)(entry) +sizeof (__u32) > last_base_addr || + (void *)XATTR_NEXT_ENTRY (entry) > last_base_addr) +return NULL ; +if (entry->e_name_index != index)continue ;if (entry->e_name_len != len)
@@ -297,20 +302,22 @@ static int lookup_all_xattrs(struct inode *inode, struct page *ipage, const char *name, struct f2fs_xattr_entry **xe, void **base_addr, int *base_size) { - void *cur_addr, *txattr_addr, *last_addr = NULL; + void *cur_addr, *txattr_addr, *last_txattr_addr; +void *last_addr =NULL ;nid_t xnid =F2FS_I (inode)->i_xattr_nid; -unsigned int size = xnid ?VALID_XATTR_BLOCK_SIZE :0 ;unsigned int inline_size =inline_xattr_size (inode);int err =0 ; -if (!size && !inline_size) +if (!xnid && !inline_size)return -ENODATA ; - *base_size = inline_size + size +XATTR_PADDING_SIZE ; + *base_size =XATTR_SIZE (xnid, inode) +XATTR_PADDING_SIZE ; txattr_addr =f2fs_kzalloc (F2FS_I_SB (inode), *base_size,GFP_NOFS );if (!txattr_addr)return -ENOMEM ; + last_txattr_addr = (void *)txattr_addr +XATTR_SIZE (xnid, inode); +/* read from inline xattr */ if (inline_size) { err =read_inline_xattr (inode, ipage, txattr_addr);
@@ -337,7 +344,11 @@ static int lookup_all_xattrs(struct inode *inode, struct page *ipage,else cur_addr = txattr_addr; - *xe =__find_xattr (cur_addr, index, len, name); + *xe =__find_xattr (cur_addr, last_txattr_addr, index, len, name); +if (!*xe) { + err = -EFAULT ; + goto out; + } check:if (IS_XATTR_LAST_ENTRY (*xe)) { err = -ENODATA ;
@@ -581,7 +592,8 @@ static int __f2fs_setxattr(struct inode *inode, int index, struct page *ipage, int flags) {struct f2fs_xattr_entry *here, *last; -void *base_addr; +void *base_addr, *last_base_addr; +nid_t xnid =F2FS_I (inode)->i_xattr_nid;int found, newsize;size_t len;__u32 new_hsize;
@@ -605,8 +617,14 @@ static int __f2fs_setxattr(struct inode *inode, int index,if (error)return error; + last_base_addr = (void *)base_addr +XATTR_SIZE (xnid, inode); +/* find entry with wanted name. */ - here =__find_xattr (base_addr, index, len, name); + here =__find_xattr (base_addr, last_base_addr, index, len, name); +if (!here) { + error = -EFAULT ; + goto exit; + } found =IS_XATTR_LAST_ENTRY (here) ?0 :1 ;
fs/f2fs/xattr.h +2 -0
@@ -71,6 +71,8 @@ struct f2fs_xattr_entry { entry = XATTR_NEXT_ENTRY(entry))#define VALID_XATTR_BLOCK_SIZE (PAGE_SIZE - sizeof(struct node_footer))#define XATTR_PADDING_SIZE (sizeof(__u32)) +#define XATTR_SIZE (x,i) (((x) ? VALID_XATTR_BLOCK_SIZE : 0) + \ + (inline_xattr_size(i)))#define MIN_OFFSET (i) XATTR_ALIGN(inline_xattr_size(i) + \ VALID_XATTR_BLOCK_SIZE)
Signature · 1 line
2.20.1
Greg Kroah-Hartman
maintainerPATCH 48/115 drivers/perf: arm_spe: Dont error on high-order pages for aux buf
In reply to Greg Kroah-Hartman[ Upstream commit 14ae42a6f0b13130a97d94d23481128961de5d38 ]
Since commit 5768402fd9c6 ("perf/ring_buffer: Use high order allocations for AUX buffers optimistically"), the perf core tends to back aux buffer allocations with high-order pages with the order encoded in the PagePrivate data. The Arm SPE driver explicitly rejects such pages, causing the perf tool to fail with:
| failed to mmap with 12 (Cannot allocate memory)
In actual fact, we can simply treat these pages just like any other since the perf core takes care to populate the page array appropriately. In theory we could try to map with PMDs where possible, but for now, let's just get things working again.
--- drivers/perf/arm_spe_pmu.c | 10 +--------- 1 file changed, 1 insertion(+), 9 deletions(-)
drivers/perf/arm_spe_pmu.c +1 -9
@@ -855,16 +855,8 @@ static void *arm_spe_pmu_setup_aux(struct perf_event *event, void **pages,if (!pglist) goto out_free_buf; -for (i =0 ; i < nr_pages; ++i) { -struct page *page =virt_to_page (pages[i]); - -if (PagePrivate (page)) { -pr_warn ("unexpected high-order page for auxbuf!" ); - goto out_free_pglist; - } - +for (i =0 ; i < nr_pages; ++i) pglist[i] =virt_to_page (pages[i]); - } buf->base =vmap (pglist, nr_pages,VM_MAP ,PAGE_KERNEL );if (!buf->base)
Signature · 1 line
2.20.1
Greg Kroah-Hartman
maintainerPATCH 49/115 bpf: sockmap, only stop/flush strp if it was enabled at some point
In reply to Greg Kroah-Hartman[ Upstream commit 014894360ec95abe868e94416b3dd6569f6e2c0c ]
If we try to call strp_done on a parser that has never been initialized, because the sockmap user is only using TX side for example we get the following error.
[ 883.422081] WARNING: CPU: 1 PID: 208 at kernel/workqueue.c:3030 __flush_work+0x1ca/0x1e0 ... [ 883.422095] Workqueue: events sk_psock_destroy_deferred [ 883.422097] RIP: 0010:__flush_work+0x1ca/0x1e0
This had been wrapped in a 'if (psock->parser.enabled)' logic which was broken because the strp_done() was never actually being called because we do a strp_stop() earlier in the tear down logic will set parser.enabled to false. This could result in a use after free if work was still in the queue and was resolved by the patch here, 1d79895aef18f ("sk_msg: Always cancel strp work before freeing the psock"). However, calling strp_stop(), done by the patch marked in the fixes tag, only is useful if we never initialized a strp parser program and never initialized the strp to start with. Because if we had initialized a stream parser strp_stop() would have been called by sk_psock_drop() earlier in the tear down process. By forcing the strp to stop we get past the WARNING in strp_done that checks the stopped flag but calling cancel_work_sync on work that has never been initialized is also wrong and generates the warning above.
To fix check if the parser program exists. If the program exists then the strp work has been initialized and must be sync'd and cancelled before free'ing any structures. If no program exists we never initialized the stream parser in the first place so skip the sync/cancel logic implemented by strp_done.
Finally, remove the strp_done its not needed and in the case where we are using the stream parser has already been called.
--- net/core/skmsg.c | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-)
net/core/skmsg.c +4 -2
@@ -554,8 +554,10 @@ static void sk_psock_destroy_deferred(struct work_struct *gc) struct sk_psock *psock = container_of(gc, struct sk_psock, gc);/* No sk_callback_lock since already detached. */ -strp_stop (&psock->parser.strp); -strp_done (&psock->parser.strp); + +/* Parser has been stopped */ +if (psock->progs.skb_parser) +strp_done (&psock->parser.strp);cancel_work_sync (&psock->work);
Signature · 1 line
2.20.1
Greg Kroah-Hartman
maintainerPATCH 41/115 drm/i915/dmc: protect against reading random memory
In reply to Greg Kroah-HartmanFrom: Lucas De Marchi <[email protected]>
commit 326fb6dd1483c985a6ef47db3fa8788bb99e8b83 upstream.
While loading the DMC firmware we were double checking the headers made sense, but in no place we checked that we were actually reading memory we were supposed to. This could be wrong in case the firmware file is truncated or malformed.
Before this patch:
# ls -l /lib/firmware/i915/icl_dmc_ver1_07.bin -rw-r--r-- 1 root root 25716 Feb 1 12:26 icl_dmc_ver1_07.bin # truncate -s 25700 /lib/firmware/i915/icl_dmc_ver1_07.bin # modprobe i915 # dmesg| grep -i dmc [drm:intel_csr_ucode_init [i915]] Loading i915/icl_dmc_ver1_07.bin [drm] Finished loading DMC firmware i915/icl_dmc_ver1_07.bin (v1.7)
i.e. it loads random data. Now it fails like below:
[drm:intel_csr_ucode_init [i915]] Loading i915/icl_dmc_ver1_07.bin [drm:csr_load_work_fn [i915]] *ERROR* Truncated DMC firmware, rejecting. i915 0000:00:02.0: Failed to load DMC firmware i915/icl_dmc_ver1_07.bin. Disabling runtime power management. i915 0000:00:02.0: DMC firmware homepage: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/i915
Before reading any part of the firmware file, validate the input first.
--- drivers/gpu/drm/i915/intel_csr.c | 18 ++++++++++++++++++ 1 file changed, 18 insertions(+)
drivers/gpu/drm/i915/intel_csr.c +18 -0
@@ -300,10 +300,17 @@ static u32 *parse_csr_fw(struct drm_i915u32 dmc_offset =CSR_DEFAULT_FW_OFFSET , readcount =0 , nbytes;u32 i;u32 *dmc_payload; +size_t fsize;if (!fw)return NULL ; + fsize =sizeof (struct intel_css_header ) + +sizeof (struct intel_package_header ) + +sizeof (struct intel_dmc_header ); +if (fsize > fw->size) + goto error_truncated; +/* Extract CSS Header information*/ css_header = (struct intel_css_header *)fw->data; if (sizeof(struct intel_css_header) !=
@@ -363,6 +370,9 @@ static u32 *parse_csr_fw(struct drm_i915/* Convert dmc_offset into number of bytes. By default it is in dwords*/ dmc_offset *=4 ; readcount += dmc_offset; + fsize += dmc_offset; +if (fsize > fw->size) + goto error_truncated;/* Extract dmc_header information. */ dmc_header = (struct intel_dmc_header *)&fw->data[readcount];
@@ -394,6 +404,10 @@ static u32 *parse_csr_fw(struct drm_i915/* fw_size is in dwords, so multiplied by 4 to convert into bytes. */ nbytes = dmc_header->fw_size *4 ; + fsize += nbytes; +if (fsize > fw->size) + goto error_truncated; +if (nbytes > csr->max_fw_size) {DRM_ERROR ("DMC FW too big (%u bytes)\n" , nbytes);return NULL ;
@@ -407,6 +421,10 @@ static u32 *parse_csr_fw(struct drm_i915 }return memcpy (dmc_payload, &fw->data[readcount], nbytes); + +error_truncated: +DRM_ERROR ("Truncated DMC firmware, rejecting.\n" ); +return NULL ; }static void intel_csr_runtime_pm_get (struct drm_i915_private *dev_priv)
Greg Kroah-Hartman
maintainerPATCH 99/115 USB: Fix chipmunk-like voice when using Logitech C270 for recording audio.
In reply to Greg Kroah-HartmanFrom: Marco Zatta <[email protected]>
commit bd21f0222adab64974b7d1b4b8c7ce6b23e9ea4d upstream.
This patch fixes the chipmunk-like voice that manifets randomly when using the integrated mic of the Logitech Webcam HD C270.
The issue was solved initially for this device by commit 2394d67e446b ("USB: add RESET_RESUME for webcams shown to be quirky") but it was then reintroduced by e387ef5c47dd ("usb: Add USB_QUIRK_RESET_RESUME for all Logitech UVC webcams"). This patch is to have the fix back.
--- drivers/usb/core/quirks.c | 3 +++ 1 file changed, 3 insertions(+)
drivers/usb/core/quirks.c +3 -0
@@ -215,6 +215,9 @@ static const struct usb_device_id usb_qu/* Cherry Stream G230 2.0 (G85-231) and 3.0 (G85-232) */ { USB_DEVICE(0x046a, 0x0023), .driver_info = USB_QUIRK_RESET_RESUME }, + /* Logitech HD Webcam C270 */ + { USB_DEVICE(0x046d, 0x0825), .driver_info = USB_QUIRK_RESET_RESUME }, + /* Logitech HD Pro Webcams C920, C920-C, C925e and C930e */ { USB_DEVICE(0x046d, 0x082d), .driver_info = USB_QUIRK_DELAY_INIT }, { USB_DEVICE(0x046d, 0x0841), .driver_info = USB_QUIRK_DELAY_INIT },
Greg Kroah-Hartman
maintainerPATCH 100/115 USB: usb-storage: Add new ID to ums-realtek
In reply to Greg Kroah-HartmanFrom: Kai-Heng Feng <[email protected]>
commit 1a6dd3fea131276a4fc44ae77b0f471b0b473577 upstream.
There is one more Realtek card reader requires ums-realtek to work correctly.
Add the device ID to support it.
--- drivers/usb/storage/unusual_realtek.h | 5 +++++ 1 file changed, 5 insertions(+)
drivers/usb/storage/unusual_realtek.h +5 -0
@@ -17,6 +17,11 @@ UNUSUAL_DEV(0x0bda, 0x0138, 0x0000, 0x99 "USB Card Reader", USB_SC_DEVICE, USB_PR_DEVICE, init_realtek_cr, 0), +UNUSUAL_DEV (0x0bda ,0x0153 ,0x0000 ,0x9999 , +"Realtek" , +"USB Card Reader" , +USB_SC_DEVICE ,USB_PR_DEVICE , init_realtek_cr,0 ), + UNUSUAL_DEV(0x0bda, 0x0158, 0x0000, 0x9999, "Realtek", "USB Card Reader",
Greg Kroah-Hartman
maintainerPATCH 101/115 USB: serial: pl2303: add Allied Telesis VT-Kit3
In reply to Greg Kroah-HartmanFrom: Chris Packham <[email protected]>
commit c5f81656a18b271976a86724dadd8344e54de74e upstream.
This is adds the vendor and device id for the AT-VT-Kit3 which is a pl2303-based device.
--- drivers/usb/serial/pl2303.c | 1 + drivers/usb/serial/pl2303.h | 3 +++ 2 files changed, 4 insertions(+)
drivers/usb/serial/pl2303.c +1 -0
@@ -106,6 +106,7 @@ static const struct usb_device_id id_tab { USB_DEVICE(SANWA_VENDOR_ID, SANWA_PRODUCT_ID) }, { USB_DEVICE(ADLINK_VENDOR_ID, ADLINK_ND6530_PRODUCT_ID) }, { USB_DEVICE(SMART_VENDOR_ID, SMART_PRODUCT_ID) }, + { USB_DEVICE(AT_VENDOR_ID, AT_VTKIT3_PRODUCT_ID) }, { } /* Terminating entry */ };
drivers/usb/serial/pl2303.h +3 -0
@@ -155,3 +155,6 @@#define SMART_VENDOR_ID 0x0b8c#define SMART_PRODUCT_ID 0x2303 +/* Allied Telesis VT-Kit3 */ +#define AT_VENDOR_ID 0x0caa +#define AT_VTKIT3_PRODUCT_ID 0x3001
Greg Kroah-Hartman
maintainerPATCH 102/115 USB: serial: option: add support for Simcom SIM7500/SIM7600 RNDIS mode
In reply to Greg Kroah-HartmanFrom: Jörgen Storvist <[email protected]>
commit 5417a7e482962952e622eabd60cd3600dd65dedf upstream.
Added IDs for Simcom SIM7500/SIM7600 series cellular module in RNDIS mode. Reserved the interface for ADB.
T: Bus=03 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#= 7 Spd=480 MxCh= 0 D: Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1 P: Vendor=1e0e ProdID=9011 Rev=03.18 S: Manufacturer=SimTech, Incorporated S: Product=SimTech, Incorporated S: SerialNumber=0123456789ABCDEF C: #Ifs= 8 Cfg#= 1 Atr=a0 MxPwr=500mA I: If#=0x0 Alt= 0 #EPs= 1 Cls=02(commc) Sub=02 Prot=ff Driver=rndis_host I: If#=0x1 Alt= 0 #EPs= 2 Cls=0a(data ) Sub=00 Prot=00 Driver=rndis_host I: If#=0x2 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=option I: If#=0x3 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=00 Prot=00 Driver=option I: If#=0x4 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=00 Prot=00 Driver=option I: If#=0x5 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=00 Prot=00 Driver=option I: If#=0x6 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=00 Prot=00 Driver=option I: If#=0x7 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=42 Prot=01 Driver=(none)
--- drivers/usb/serial/option.c | 2 ++ 1 file changed, 2 insertions(+)
drivers/usb/serial/option.c +2 -0
@@ -1772,6 +1772,8 @@ static const struct usb_device_id option { USB_DEVICE(ALINK_VENDOR_ID, SIMCOM_PRODUCT_SIM7100E), .driver_info = RSVD(5) | RSVD(6) }, { USB_DEVICE_INTERFACE_CLASS(0x1e0e, 0x9003, 0xff) }, /* Simcom SIM7500/SIM7600 MBIM mode */ + { USB_DEVICE_INTERFACE_CLASS(0x1e0e, 0x9011, 0xff), /* Simcom SIM7500/SIM7600 RNDIS mode */ + .driver_info = RSVD(7) }, { USB_DEVICE(ALCATEL_VENDOR_ID, ALCATEL_PRODUCT_X060S_X200), .driver_info = NCTRL(0) | NCTRL(1) | RSVD(4) }, { USB_DEVICE(ALCATEL_VENDOR_ID, ALCATEL_PRODUCT_X220_X500D),
Greg Kroah-Hartman
maintainerPATCH 103/115 USB: serial: option: add Telit 0x1260 and 0x1261 compositions
In reply to Greg Kroah-HartmanFrom: Daniele Palmas <[email protected]>
commit f3dfd4072c3ee6e287f501a18b5718b185d6a940 upstream.
Added support for Telit LE910Cx 0x1260 and 0x1261 compositions.
--- drivers/usb/serial/option.c | 4 ++++ 1 file changed, 4 insertions(+)
drivers/usb/serial/option.c +4 -0
@@ -1171,6 +1171,10 @@ static const struct usb_device_id option { USB_DEVICE_INTERFACE_CLASS(TELIT_VENDOR_ID, TELIT_PRODUCT_LE920A4_1213, 0xff) }, { USB_DEVICE(TELIT_VENDOR_ID, TELIT_PRODUCT_LE920A4_1214), .driver_info = NCTRL(0) | RSVD(1) | RSVD(2) | RSVD(3) }, + { USB_DEVICE(TELIT_VENDOR_ID, 0x1260), + .driver_info = NCTRL(0) | RSVD(1) | RSVD(2) }, + { USB_DEVICE(TELIT_VENDOR_ID, 0x1261), + .driver_info = NCTRL(0) | RSVD(1) | RSVD(2) }, { USB_DEVICE(TELIT_VENDOR_ID, 0x1900), /* Telit LN940 (QMI) */ .driver_info = NCTRL(0) | RSVD(1) }, { USB_DEVICE_INTERFACE_CLASS(TELIT_VENDOR_ID, 0x1901, 0xff), /* Telit LN940 (MBIM) */
Greg Kroah-Hartman
maintainerPATCH 104/115 tracing/uprobe: Fix NULL pointer dereference in trace_uprobe_create()
In reply to Greg Kroah-HartmanFrom: Eiichi Tsukata <[email protected]>
commit f01098c74b5219f3969d4750eeed1a36bfc038e3 upstream.
Just like the case of commit 8b05a3a7503c ("tracing/kprobes: Fix NULL pointer dereference in trace_kprobe_create()"), writing an incorrectly formatted string to uprobe_events can trigger NULL pointer dereference.
Reporeducer:
# echo r > /sys/kernel/debug/tracing/uprobe_events
dmesg:
BUG: kernel NULL pointer dereference, address: 0000000000000000 #PF: supervisor read access in kernel mode #PF: error_code(0x0000) - not-present page PGD 8000000079d12067 P4D 8000000079d12067 PUD 7b7ab067 PMD 0 Oops: 0000 [#1] PREEMPT SMP PTI CPU: 0 PID: 1903 Comm: bash Not tainted 5.2.0-rc3+ #15 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.12.0-2.fc30 04/01/2014 RIP: 0010:strchr+0x0/0x30 Code: c0 eb 0d 84 c9 74 18 48 83 c0 01 48 39 d0 74 0f 0f b6 0c 07 3a 0c 06 74 ea 19 c0 83 c8 01 c3 31 c0 c3 0f 1f 84 00 00 00 00 00 <0f> b6 07 89 f2 40 38 f0 75 0e eb 13 0f b6 47 01 48 83 c RSP: 0018:ffffb55fc0403d10 EFLAGS: 00010293
RAX: ffff993ffb793400 RBX: 0000000000000000 RCX: ffffffffa4852625
RDX: 0000000000000000 RSI: 000000000000002f RDI: 0000000000000000
RBP: ffffb55fc0403dd0 R08: ffff993ffb793400 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000000
R13: ffff993ff9cc1668 R14: 0000000000000001 R15: 0000000000000000
FS: 00007f30c5147700(0000) GS:ffff993ffda00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000000000000 CR3: 000000007b628000 CR4: 00000000000006f0
Call Trace: trace_uprobe_create+0xe6/0xb10 ? __kmalloc_track_caller+0xe6/0x1c0 ? __kmalloc+0xf0/0x1d0 ? trace_uprobe_create+0xb10/0xb10 create_or_delete_trace_uprobe+0x35/0x90 ? trace_uprobe_create+0xb10/0xb10 trace_run_command+0x9c/0xb0 trace_parse_run_command+0xf9/0x1eb ? probes_open+0x80/0x80 __vfs_write+0x43/0x90 vfs_write+0x14a/0x2a0 ksys_write+0xa2/0x170 do_syscall_64+0x7f/0x200 entry_SYSCALL_64_after_hwframe+0x49/0xbe
--- kernel/trace/trace_uprobe.c | 13 ++++++++++--- 1 file changed, 10 insertions(+), 3 deletions(-)
kernel/trace/trace_uprobe.c +10 -3
@@ -434,10 +434,17 @@ static int trace_uprobe_create(int argc, ret =0 ; ref_ctr_offset =0 ; -/* argc must be >= 1 */ -if (argv[0 ][0 ] =='r' ) +switch (argv[0 ][0 ]) { +case 'r' : is_return = true; -else if (argv[0 ][0 ] !='p' || argc <2 ) +break ; +case 'p' : +break ; +default : +return -ECANCELED ; + } + +if (argc <2 )return -ECANCELED ;if (argv[0 ][1 ] ==':' )
Greg Kroah-Hartman
maintainerPATCH 105/115 timekeeping: Repair ktime_get_coarse*() granularity
In reply to Greg Kroah-HartmanFrom: Thomas Gleixner <[email protected]>
commit e3ff9c3678b4d80e22d2557b68726174578eaf52 upstream.
Jason reported that the coarse ktime based time getters advance only once per second and not once per tick as advertised.
The code reads only the monotonic base time, which advances once per second. The nanoseconds are accumulated on every tick in xtime_nsec up to a second and the regular time getters take this nanoseconds offset into account, but the ktime_get_coarse*() implementation fails to do so.
Add the accumulated xtime_nsec value to the monotonic base time to get the proper per tick advancing coarse tinme.
--- kernel/time/timekeeping.c | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-)
kernel/time/timekeeping.c +3 -2
@@ -807,17 +807,18 @@ ktime_t ktime_get_coarse_with_offset(enustruct timekeeper *tk = &tk_core.timekeeper;unsigned int seq;ktime_t base, *offset = offsets[offs]; +u64 nsecs;WARN_ON (timekeeping_suspended);do { seq =read_seqcount_begin (&tk_core.seq); base =ktime_add (tk->tkr_mono.base, *offset); + nsecs = tk->tkr_mono.xtime_nsec >> tk->tkr_mono.shift; }while (read_seqcount_retry (&tk_core.seq, seq)); -return base; - +return base + nsecs; }EXPORT_SYMBOL_GPL (ktime_get_coarse_with_offset);
Greg Kroah-Hartman
maintainerPATCH 106/115 RAS/CEC: Convert the timer callback to a workqueue
In reply to Greg Kroah-HartmanFrom: Cong Wang <[email protected]>
commit 0ade0b6240c4853cf9725924c46c10f4251639d7 upstream.
cec_timer_fn() is a timer callback which reads ce_arr.array[] and updates its decay values. However, it runs in interrupt context and the mutex protection the CEC uses for that array, is inadequate. Convert the used timer to a workqueue to keep the tasks the CEC performs preemptible and thus low-prio.
[ bp: Rewrite commit message.
s/timer/decay/gi to make it agnostic as to what facility is used. ]
--- drivers/ras/cec.c | 46 ++++++++++++++++++++++------------------------ 1 file changed, 22 insertions(+), 24 deletions(-)
drivers/ras/cec.c +22 -24
@@ -2,6 +2,7 @@#include <linux/mm.h> #include <linux/gfp.h> #include <linux/kernel.h> +#include <linux/workqueue.h> #include <asm/mce.h>
@@ -123,16 +124,12 @@ static u64 dfs_pfn;/* Amount of errors after which we offline */ static unsigned int count_threshold =COUNT_MASK ; -/* -* The timer "decays" element count each timer_interval which is 24hrs by -* default. -*/ - -#define CEC_TIMER_DEFAULT_INTERVAL 24 * 60 * 60/* 24 hrs */ -#define CEC_TIMER_MIN_INTERVAL 1 * 60 * 60/* 1h */ -#define CEC_TIMER_MAX_INTERVAL 30 * 24 * 60 * 60/* one month */ -static struct timer_list cec_timer; -static u64 timer_interval =CEC_TIMER_DEFAULT_INTERVAL ; +/* Each element "decays" each decay_interval which is 24hrs by default. */ +#define CEC_DECAY_DEFAULT_INTERVAL 24 * 60 * 60/* 24 hrs */ +#define CEC_DECAY_MIN_INTERVAL 1 * 60 * 60/* 1h */ +#define CEC_DECAY_MAX_INTERVAL 30 * 24 * 60 * 60/* one month */ +static struct delayed_work cec_work; +static u64 decay_interval =CEC_DECAY_DEFAULT_INTERVAL ;/* * Decrement decay value. We're using DECAY_BITS bits to denote decay of an
@@ -160,20 +157,21 @@ static void do_spring_cleaning(struct ce/* * @interval in seconds */ -static void cec_mod_timer (struct timer_list *t,unsigned long interval) +static void cec_mod_work (unsigned long interval) {unsigned long iv; - iv = interval *HZ + jiffies; - -mod_timer (t,round_jiffies (iv)); + iv = interval *HZ ; +mod_delayed_work (system_wq, &cec_work,round_jiffies (iv)); } -static void cec_timer_fn (struct timer_list *unused) +static void cec_work_fn (struct work_struct *work) { +mutex_lock (&ce_mutex);do_spring_cleaning (&ce_arr); +mutex_unlock (&ce_mutex); -cec_mod_timer (&cec_timer, timer_interval); +cec_mod_work (decay_interval); }/*
@@ -374,15 +372,15 @@ static int decay_interval_set(void *data { *(u64 *)data = val; -if (val <CEC_TIMER_MIN_INTERVAL ) +if (val <CEC_DECAY_MIN_INTERVAL )return -EINVAL ; -if (val >CEC_TIMER_MAX_INTERVAL ) +if (val >CEC_DECAY_MAX_INTERVAL )return -EINVAL ; - timer_interval = val; + decay_interval = val; -cec_mod_timer (&cec_timer, timer_interval); +cec_mod_work (decay_interval);return 0 ; }DEFINE_DEBUGFS_ATTRIBUTE (decay_interval_ops, u64_get, decay_interval_set,"%lld\n" );
@@ -426,7 +424,7 @@ static int array_dump(struct seq_file *mseq_printf (m,"Flags: 0x%x\n" , ca->flags); -seq_printf (m,"Timer interval: %lld seconds\n" , timer_interval); +seq_printf (m,"Decay interval: %lld seconds\n" , decay_interval);seq_printf (m,"Decays: %lld\n" , ca->decays_done);seq_printf (m,"Action threshold: %d\n" , count_threshold);
@@ -472,7 +470,7 @@ static int __init create_debugfs_nodes(v } decay =debugfs_create_file ("decay_interval" ,S_IRUSR |S_IWUSR , d, - &timer_interval, &decay_interval_ops); + &decay_interval, &decay_interval_ops);if (!decay) {pr_warn ("Error creating decay_interval debugfs node!\n" ); goto err;
@@ -508,8 +506,8 @@ void __init cec_init(void)if (create_debugfs_nodes ())return ; -timer_setup (&cec_timer, cec_timer_fn,0 ); -cec_mod_timer (&cec_timer,CEC_TIMER_DEFAULT_INTERVAL ); +INIT_DELAYED_WORK (&cec_work, cec_work_fn); +schedule_delayed_work (&cec_work,CEC_DECAY_DEFAULT_INTERVAL );pr_info ("Correctable Errors collector initialized.\n" ); }
Greg Kroah-Hartman
maintainerPATCH 107/115 RAS/CEC: Fix binary search function
In reply to Greg Kroah-HartmanFrom: Borislav Petkov <[email protected]>
commit f3c74b38a55aefe1004200d15a83f109b510068c upstream.
Switch to using Donald Knuth's binary search algorithm (The Art of Computer Programming, vol. 3, section 6.2.1). This should've been done from the very beginning but the author must've been smoking something very potent at the time.
The problem with the current one was that it would return the wrong element index in certain situations:
https://lkml.kernel.org/r/CAM_iQpVd02zkVJ846cj-Fg1yUNuz6tY5q1Vpj4LrXmE06dPYYg@mail.gmail.com
and the noodling code after the loop was fishy at best.
So switch to using Knuth's binary search. The final result is much cleaner and straightforward.
--- drivers/ras/cec.c | 34 ++++++++++++++++++++-------------- 1 file changed, 20 insertions(+), 14 deletions(-)
drivers/ras/cec.c +20 -14
@@ -181,32 +181,38 @@ static void cec_work_fn(struct work_stru*/ static int __find_elem (struct ce_array *ca,u64 pfn,unsigned int *to) { +int min =0 , max = ca->n -1 ;u64 this_pfn; -int min =0 , max = ca->n; -while (min < max) { -int tmp = (max + min) >>1 ; +while (min <= max) { +int i = (min + max) >>1 ; - this_pfn =PFN (ca->array[tmp]); + this_pfn =PFN (ca->array[i]);if (this_pfn < pfn) - min = tmp +1 ; + min = i +1 ;else if (this_pfn > pfn) - max = tmp; -else { - min = tmp; -break ; + max = i -1 ; +else if (this_pfn == pfn) { +if (to) + *to = i; + +return i; } } +/* +* When the loop terminates without finding @pfn, min has the index of +* the element slot where the new @pfn should be inserted. The loop +* terminates when min > max, which means the min index points to the +* bigger element while the max index to the smaller element, in-between +* which the new @pfn belongs to. +* +* For more details, see exercise 1, Section 6.2.1 in TAOCP, vol. 3. +*/ if (to) *to = min; - this_pfn =PFN (ca->array[min]); - -if (this_pfn == pfn) -return min; -return -ENOKEY ; }
Greg Kroah-Hartman
maintainerPATCH 108/115 x86/microcode, cpuhotplug: Add a microcode loader CPU hotplug callback
In reply to Greg Kroah-HartmanFrom: Borislav Petkov <[email protected]>
commit 78f4e932f7760d965fb1569025d1576ab77557c5 upstream.
Adric Blake reported the following warning during suspend-resume:
Enabling non-boot CPUs ...
x86: Booting SMP configuration:
smpboot: Booting Node 0 Processor 1 APIC 0x2
unchecked MSR access error: WRMSR to 0x10f (tried to write 0x0000000000000000) \
at rIP: 0xffffffff8d267924 (native_write_msr+0x4/0x20)
Call Trace: intel_set_tfa intel_pmu_cpu_starting ? x86_pmu_dead_cpu x86_pmu_starting_cpu cpuhp_invoke_callback ? _raw_spin_lock_irqsave notify_cpu_starting start_secondary secondary_startup_64 microcode: sig=0x806ea, pf=0x80, revision=0x96 microcode: updated to revision 0xb4, date = 2019-04-01 CPU1 is up
The MSR in question is MSR_TFA_RTM_FORCE_ABORT and that MSR is emulated by microcode. The log above shows that the microcode loader callback happens after the PMU restoration, leading to the conjecture that because the microcode hasn't been updated yet, that MSR is not present yet, leading to the #GP.
Add a microcode loader-specific hotplug vector which comes before the PERF vectors and thus executes earlier and makes sure the MSR is present.
--- arch/x86/kernel/cpu/microcode/core.c | 2 +- include/linux/cpuhotplug.h | 1 + 2 files changed, 2 insertions(+), 1 deletion(-)
arch/x86/kernel/cpu/microcode/core.c +1 -1
@@ -876,7 +876,7 @@ int __init microcode_init(void) goto out_ucode_group;register_syscore_ops (&mc_syscore_ops); -cpuhp_setup_state_nocalls (CPUHP_AP_ONLINE_DYN ,"x86/microcode:online" , +cpuhp_setup_state_nocalls (CPUHP_AP_MICROCODE_LOADER ,"x86/microcode:online" , mc_cpu_online, mc_cpu_down_prep);pr_info ("Microcode Update Driver: v%s." ,DRIVER_VERSION );
include/linux/cpuhotplug.h +1 -0
@@ -101,6 +101,7 @@ enum cpuhp_state {CPUHP_AP_IRQ_BCM2836_STARTING ,CPUHP_AP_IRQ_MIPS_GIC_STARTING ,CPUHP_AP_ARM_MVEBU_COHERENCY , +CPUHP_AP_MICROCODE_LOADER ,CPUHP_AP_PERF_X86_AMD_UNCORE_STARTING ,CPUHP_AP_PERF_X86_STARTING , CPUHP_AP_PERF_X86_AMD_IBS_STARTING,
Greg Kroah-Hartman
maintainerPATCH 91/115 KVM: s390: fix memory slot handling for KVM_SET_USER_MEMORY_REGION
In reply to Greg Kroah-Hartman[ Upstream commit 19ec166c3f39fe1d3789888a74cc95544ac266d4 ]
kselftests exposed a problem in the s390 handling for memory slots. Right now we only do proper memory slot handling for creation of new memory slots. Neither MOVE, nor DELETION are handled properly. Let us implement those.
--- arch/s390/kvm/kvm-s390.c | 35 +++++++++++++++++++++-------------- 1 file changed, 21 insertions(+), 14 deletions(-)
arch/s390/kvm/kvm-s390.c +21 -14
@@ -4413,21 +4413,28 @@ void kvm_arch_commit_memory_region(struct kvm *kvm,const struct kvm_memory_slot *new, enum kvm_mr_change change) { - int rc; - -/* If the basics of the memslot do not change, we do not want -* to update the gmap. Every update causes several unnecessary -* segment translation exceptions. This is usually handled just -* fine by the normal fault handler + gmap, but it will also -* cause faults on the prefix page of running guest CPUs. -*/ -if (old->userspace_addr == mem->userspace_addr && - old->base_gfn *PAGE_SIZE == mem->guest_phys_addr && - old->npages *PAGE_SIZE == mem->memory_size) -return ; + int rc = 0; - rc =gmap_map_segment (kvm->arch.gmap, mem->userspace_addr, - mem->guest_phys_addr, mem->memory_size); +switch (change) { +case KVM_MR_DELETE : + rc =gmap_unmap_segment (kvm->arch.gmap, old->base_gfn *PAGE_SIZE , + old->npages *PAGE_SIZE ); +break ; +case KVM_MR_MOVE : + rc =gmap_unmap_segment (kvm->arch.gmap, old->base_gfn *PAGE_SIZE , + old->npages *PAGE_SIZE ); +if (rc) +break ; +/* FALLTHROUGH */ +case KVM_MR_CREATE : + rc =gmap_map_segment (kvm->arch.gmap, mem->userspace_addr, + mem->guest_phys_addr, mem->memory_size); +break ; +case KVM_MR_FLAGS_ONLY : +break ; +default : +WARN (1 ,"Unknown KVM MR CHANGE: %d\n" , change); + }if (rc)pr_warn ("failed to commit memory region\n" );return ;
Signature · 1 line
2.20.1
Greg Kroah-Hartman
maintainerPATCH 109/115 x86/kasan: Fix boot with 5-level paging and KASAN
In reply to Greg Kroah-HartmanFrom: Andrey Ryabinin <[email protected]>
commit f3176ec9420de0c385023afa3e4970129444ac2f upstream.
Since commit d52888aa2753 ("x86/mm: Move LDT remap out of KASLR region on 5-level paging") kernel doesn't boot with KASAN on 5-level paging machines. The bug is actually in early_p4d_offset() and introduced by commit 12a8cc7fcf54 ("x86/kasan: Use the same shadow offset for 4- and 5-level paging")
early_p4d_offset() tries to convert pgd_val(*pgd) value to a physical address. This doesn't make sense because pgd_val() already contains the physical address.
It did work prior to commit d52888aa2753 because the result of "__pa_nodebug(pgd_val(*pgd)) & PTE_PFN_MASK" was the same as "pgd_val(*pgd) & PTE_PFN_MASK". __pa_nodebug() just set some high bits which were masked out by applying PTE_PFN_MASK.
After the change of the PAGE_OFFSET offset in commit d52888aa2753 __pa_nodebug(pgd_val(*pgd)) started to return a value with more high bits set and PTE_PFN_MASK wasn't enough to mask out all of them. So it returns a wrong not even canonical address and crashes on the attempt to dereference it.
Switch back to pgd_val() & PTE_PFN_MASK to cure the issue.
--- arch/x86/mm/kasan_init_64.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
arch/x86/mm/kasan_init_64.c +1 -1
@@ -199,7 +199,7 @@ static inline p4d_t *early_p4d_offset(pgif (!pgtable_l5_enabled ())return (p4d_t *)pgd; - p4d =__pa_nodebug (pgd_val (*pgd)) &PTE_PFN_MASK ; + p4d =pgd_val (*pgd) &PTE_PFN_MASK ; p4d += __START_KERNEL_map - phys_base;return (p4d_t *)p4d +p4d_index (addr); }
Greg Kroah-Hartman
maintainerPATCH 110/115 x86/mm/KASLR: Compute the size of the vmemmap section properly
In reply to Greg Kroah-HartmanFrom: Baoquan He <[email protected]>
commit 00e5a2bbcc31d5fea853f8daeba0f06c1c88c3ff upstream.
The size of the vmemmap section is hardcoded to 1 TB to support the maximum amount of system RAM in 4-level paging mode - 64 TB.
However, 1 TB is not enough for vmemmap in 5-level paging mode. Assuming the size of struct page is 64 Bytes, to support 4 PB system RAM in 5-level, 64 TB of vmemmap area is needed:
4 * 1000^5 PB / 4096 bytes page size * 64 bytes per page struct / 1000^4 TB = 62.5 TB.
This hardcoding may cause vmemmap to corrupt the following cpu_entry_area section, if KASLR puts vmemmap very close to it and the actual vmemmap size is bigger than 1 TB.
So calculate the actual size of the vmemmap region needed and then align it up to 1 TB boundary.
In 4-level paging mode it is always 1 TB. In 5-level it's adjusted on demand. The current code reserves 0.5 PB for vmemmap on 5-level. With this change, the space can be saved and thus used to increase entropy for the randomization.
[ bp: Spell out how the 64 TB needed for vmemmap is computed and massage commit
message. ]
--- arch/x86/mm/kaslr.c | 11 ++++++++++- 1 file changed, 10 insertions(+), 1 deletion(-)
arch/x86/mm/kaslr.c +10 -1
@@ -52,7 +52,7 @@ static __initdata struct kaslr_memory_re } kaslr_regions[] = { { &page_offset_base, 0 }, { &vmalloc_base, 0 }, - { &vmemmap_base, 1 }, + { &vmemmap_base, 0 }, }; /* Get size in bytes used by the memory region */
@@ -78,6 +78,7 @@ void __init kernel_randomize_memory(voidunsigned long rand, memory_tb;struct rnd_state rand_state;unsigned long remain_entropy; +unsigned long vmemmap_size; vaddr_start =pgtable_l5_enabled () ? __PAGE_OFFSET_BASE_L5 : __PAGE_OFFSET_BASE_L4; vaddr = vaddr_start;
@@ -109,6 +110,14 @@ void __init kernel_randomize_memory(voidif (memory_tb < kaslr_regions[0 ].size_tb) kaslr_regions[0 ].size_tb = memory_tb; +/* +* Calculate the vmemmap region size in TBs, aligned to a TB +* boundary. +*/ + vmemmap_size = (kaslr_regions[0 ].size_tb << (TB_SHIFT -PAGE_SHIFT )) * +sizeof (struct page ); + kaslr_regions[2 ].size_tb =DIV_ROUND_UP (vmemmap_size,1UL <<TB_SHIFT ); +/* Calculate entropy available between regions */ remain_entropy = vaddr_end - vaddr_start;for (i =0 ; i <ARRAY_SIZE (kaslr_regions); i++)
Greg Kroah-Hartman
maintainerPATCH 111/115 x86/resctrl: Prevent NULL pointer dereference when local MBM is disabled
In reply to Greg Kroah-HartmanFrom: Prarit Bhargava <[email protected]>
commit c7563e62a6d720aa3b068e26ddffab5f0df29263 upstream.
Booting with kernel parameter "rdt=cmt,mbmtotal,memlocal,l3cat,mba" and executing "mount -t resctrl resctrl -o mba_MBps /sys/fs/resctrl" results in a NULL pointer dereference on systems which do not have local MBM support enabled..
BUG: kernel NULL pointer dereference, address: 0000000000000020 PGD 0 P4D 0 Oops: 0000 [#1] SMP PTI CPU: 0 PID: 722 Comm: kworker/0:3 Not tainted 5.2.0-0.rc3.git0.1.el7_UNSUPPORTED.x86_64 #2 Workqueue: events mbm_handle_overflow RIP: 0010:mbm_handle_overflow+0x150/0x2b0
Only enter the bandwith update loop if the system has local MBM enabled.
--- arch/x86/kernel/cpu/resctrl/monitor.c | 3 +++ 1 file changed, 3 insertions(+)
arch/x86/kernel/cpu/resctrl/monitor.c +3 -0
@@ -368,6 +368,9 @@ static void update_mba_bw(struct rdtgroustruct list_head *head;struct rdtgroup *entry; +if (!is_mbm_local_enabled ()) +return ; + r_mba = &rdt_resources_all[RDT_RESOURCE_MBA ]; closid = rgrp->closid; rmid = rgrp->mon.rmid;
Greg Kroah-Hartman
maintainerPATCH 112/115 drm/edid: abstract override/firmware EDID retrieval
In reply to Greg Kroah-HartmanFrom: Jani Nikula <[email protected]>
commit 56a2b7f2a39a8d4b16a628e113decde3d7400879 upstream.
Abstract the debugfs override and the firmware EDID retrieval function. We'll be needing it in the follow-up. No functional changes.
--- drivers/gpu/drm/drm_edid.c | 25 +++++++++++++++++-------- 1 file changed, 17 insertions(+), 8 deletions(-)
drivers/gpu/drm/drm_edid.c +17 -8
@@ -1580,6 +1580,20 @@ static void connector_bad_edid(struct dr } } +/* Get override or firmware EDID */ +static struct edid *drm_get_override_edid (struct drm_connector *connector) +{ +struct edid *override =NULL ; + +if (connector->override_edid) + override =drm_edid_duplicate (connector->edid_blob_ptr->data); + +if (!override) + override =drm_load_edid_firmware (connector); + +return IS_ERR (override) ?NULL : override; +} +/** * drm_do_get_edid - get EDID data using a custom EDID block read function * @connector: connector we're probing
@@ -1607,15 +1621,10 @@ struct edid *drm_do_get_edid(struct drm_ {int i, j =0 , valid_extensions =0 ;u8 *edid, *new; -struct edid *override =NULL ; - -if (connector->override_edid) - override =drm_edid_duplicate (connector->edid_blob_ptr->data); - -if (!override) - override =drm_load_edid_firmware (connector); +struct edid *override; -if (!IS_ERR_OR_NULL (override)) + override =drm_get_override_edid (connector); +if (override)return override;if ((edid =kmalloc (EDID_LENGTH ,GFP_KERNEL )) ==NULL )
Greg Kroah-Hartman
maintainerPATCH 113/115 drm: add fallback override/firmware EDID modes workaround
In reply to Greg Kroah-HartmanFrom: Jani Nikula <[email protected]>
commit 48eaeb7664c76139438724d520a1ea4a84a3ed92 upstream.
We've moved the override and firmware EDID (simply "override EDID" from now on) handling to the low level drm_do_get_edid() function in order to transparently use the override throughout the stack. The idea is that you get the override EDID via the ->get_modes() hook.
Unfortunately, there are scenarios where the DDC probe in drm_get_edid() called via ->get_modes() fails, although the preceding ->detect() succeeds.
In the case reported by Paul Wise, the ->detect() hook, intel_crt_detect(), relies on hotplug detect, bypassing the DDC. In the case reported by Ilpo Järvinen, there is no ->detect() hook, which is interpreted as connected. The subsequent DDC probe reached via ->get_modes() fails, and we don't even look at the override EDID, resulting in no modes being added.
Because drm_get_edid() is used via ->detect() all over the place, we can't trivially remove the DDC probe, as it leads to override EDID effectively meaning connector forcing. The goal is that connector forcing and override EDID remain orthogonal.
Generally, the underlying problem here is the conflation of ->detect() and ->get_modes() via drm_get_edid(). The former should just detect, and the latter should just get the modes, typically via reading the EDID. As long as drm_get_edid() is used in ->detect(), it needs to retain the DDC probe. Or such users need to have a separate DDC probe step first.
The EDID caching between ->detect() and ->get_modes() done by some drivers is a further complication that prevents us from making drm_do_get_edid() adapt to the two cases.
Work around the regression by falling back to a separate attempt at getting the override EDID at drm_helper_probe_single_connector_modes() level. With a working DDC and override EDID, it'll never be called; the override EDID will come via ->get_modes(). There will still be a failing DDC probe attempt in the cases that require the fallback.
v2:
- Call drm_connector_update_edid_property (Paul)
- Update commit message about EDID caching (Daniel)
Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=107583
--- drivers/gpu/drm/drm_edid.c | 30 ++++++++++++++++++++++++++++++ drivers/gpu/drm/drm_probe_helper.c | 7 +++++++ include/drm/drm_edid.h | 1 + 3 files changed, 38 insertions(+)
drivers/gpu/drm/drm_edid.c +30 -0
@@ -1595,6 +1595,36 @@ static struct edid *drm_get_override_edi }/** +* drm_add_override_edid_modes - add modes from override/firmware EDID +* @connector: connector we're probing +* +* Add modes from the override/firmware EDID, if available. Only to be used from +* drm_helper_probe_single_connector_modes() as a fallback for when DDC probe +* failed during drm_get_edid() and caused the override/firmware EDID to be +* skipped. +* +* Return: The number of modes added or 0 if we couldn't find any. +*/ +int drm_add_override_edid_modes (struct drm_connector *connector) +{ +struct edid *override; +int num_modes =0 ; + + override =drm_get_override_edid (connector); +if (override) { +drm_connector_update_edid_property (connector, override); + num_modes =drm_add_edid_modes (connector, override); +kfree (override); + +DRM_DEBUG_KMS ("[CONNECTOR:%d:%s] adding %d modes via fallback override/firmware EDID\n" , + connector->base.id, connector->name, num_modes); + } + +return num_modes; +} +EXPORT_SYMBOL (drm_add_override_edid_modes); + +/** * drm_do_get_edid - get EDID data using a custom EDID block read function * @connector: connector we're probing * @get_edid_block: EDID block read function
drivers/gpu/drm/drm_probe_helper.c +7 -0
@@ -479,6 +479,13 @@ retry: count = (*connector_funcs->get_modes)(connector); +/* +* Fallback for when DDC probe failed in drm_get_edid() and thus skipped +* override/firmware EDID. +*/ +if (count ==0 && connector->status == connector_status_connected) + count =drm_add_override_edid_modes (connector); +if (count ==0 && connector->status == connector_status_connected) count =drm_add_modes_noedid (connector,1024 ,768 ); count +=drm_helper_probe_add_cmdline_mode (connector);
include/drm/drm_edid.h +1 -0
@@ -465,6 +465,7 @@ struct edid *drm_get_edid_switcheroo(str struct i2c_adapter *adapter);struct edid *drm_edid_duplicate (const struct edid *edid);int drm_add_edid_modes (struct drm_connector *connector,struct edid *edid); +int drm_add_override_edid_modes (struct drm_connector *connector);u8 drm_match_cea_mode (const struct drm_display_mode *to_match);enum hdmi_picture_aspect drm_get_cea_aspect_ratio (const u8 video_code);
Greg Kroah-Hartman
maintainerPATCH 92/115 kvm: selftests: aarch64: dirty_log_test: fix unaligned memslot size
In reply to Greg Kroah-Hartman[ Upstream commit bffed38d4fb536c5d5d6c37846a7fb8fde1452fa ]
The memory slot size must be aligned to the host's page size. When testing a guest with a 4k page size on a host with a 64k page size, then 3 guest pages are not host page size aligned. Since we just need a nearly arbitrary number of extra pages to ensure the memslot is not aligned to a 64 host-page boundary for this test, then we can use 16, as that's 64k aligned, but not 64 * 64k aligned.
--- tools/testing/selftests/kvm/dirty_log_test.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
tools/testing/selftests/kvm/dirty_log_test.c +1 -1
@@ -292,7 +292,7 @@ static void run_test(enum vm_guest_mode mode, unsigned long iterations,* A little more than 1G of guest page sized pages. Cover the * case where the size is not aligned to 64 pages. */ - guest_num_pages = (1ul << (30 - guest_page_shift)) +3 ; + guest_num_pages = (1ul << (30 - guest_page_shift)) +16 ; host_page_size =getpagesize (); host_num_pages = (guest_num_pages * guest_page_size) / host_page_size + !!((guest_num_pages * guest_page_size) % host_page_size);
Signature · 1 line
2.20.1
Greg Kroah-Hartman
maintainerPATCH 93/115 kvm: selftests: aarch64: fix default vm mode
In reply to Greg Kroah-Hartman[ Upstream commit 55eda003f02f075bab0223a188e548dbf3ac8dfe ]
VM_MODE_P52V48_4K is not a valid mode for AArch64. Replace its use in vm_create_default() with a mode that works and represents a good AArch64 default. (We didn't ever see a problem with this because we don't have any unit tests using vm_create_default(), but it's good to get it fixed in advance.)
--- tools/testing/selftests/kvm/lib/aarch64/processor.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
tools/testing/selftests/kvm/lib/aarch64/processor.c +1 -1
@@ -226,7 +226,7 @@ struct kvm_vm *vm_create_default(uint32_t vcpuid, uint64_t extra_mem_pages,uint64_t extra_pg_pages = (extra_mem_pages / ptrs_per_4k_pte) *2 ;struct kvm_vm *vm; - vm =vm_create (VM_MODE_P52V48_4K ,DEFAULT_GUEST_PHY_PAGES + extra_pg_pages,O_RDWR ); + vm =vm_create (VM_MODE_P40V48_4K ,DEFAULT_GUEST_PHY_PAGES + extra_pg_pages,O_RDWR );kvm_vm_elf_load (vm, program_invocation_name,0 ,0 );vm_vcpu_add_default (vm, vcpuid, guest_code);
Signature · 1 line
2.20.1
Greg Kroah-Hartman
maintainerPATCH 94/115 tools/kvm_stat: fix fields filter for child events
In reply to Greg Kroah-Hartman[ Upstream commit 883d25e70b2f699fed9017e509d1ef8e36229b89 ]
The fields filter would not work with child fields, as the respective parents would not be included. No parents displayed == no childs displayed. To reproduce, run on s390 (would work on other platforms, too, but would require a different filter name):
- Run 'kvm_stat -d'
- Press 'f'
- Enter 'instruct'
Notice that events like instruction_diag_44 or instruction_diag_500 are not displayed - the output remains empty.
With this patch, we will filter by matching events and their parents. However, consider the following example where we filter by instruction_diag_44:
kvm statistics - summary
regex filter: instruction_diag_44
Event Total %Total CurAvg/s
exit_instruction 276 100.0 12
instruction_diag_44 256 92.8 11
Total 276 12Note that the parent ('exit_instruction') displays the total events, but the childs listed do not match its total (256 instead of 276). This is intended (since we're filtering all but one child), but might be confusing on first sight.
--- tools/kvm/kvm_stat/kvm_stat | 16 ++++++++++++---- tools/kvm/kvm_stat/kvm_stat.txt | 2 ++ 2 files changed, 14 insertions(+), 4 deletions(-)
tools/kvm/kvm_stat/kvm_stat +12 -4
@@ -575,8 +575,12 @@ class TracepointProvider(Provider): def update_fields(self, fields_filter): """Refresh fields, applying fields_filter""" self.fields = [field for field in self._get_available_fields() - if self.is_field_wanted(fields_filter, field) or - ARCH.tracepoint_is_child(field)] + if self.is_field_wanted(fields_filter, field)] + # add parents for child fields - otherwise we won't see any output! + for field in self._fields: + parent = ARCH.tracepoint_is_child(field) + if (parent and parent not in self._fields): + self.fields.append(parent) @staticmethod def _get_online_cpus():
@@ -735,8 +739,12 @@ class DebugfsProvider(Provider): def update_fields(self, fields_filter): """Refresh fields, applying fields_filter""" self._fields = [field for field in self._get_available_fields() - if self.is_field_wanted(fields_filter, field) or - ARCH.debugfs_is_child(field)] + if self.is_field_wanted(fields_filter, field)] + # add parents for child fields - otherwise we won't see any output! + for field in self._fields: + parent = ARCH.debugfs_is_child(field) + if (parent and parent not in self._fields): + self.fields.append(parent) @property def fields(self):
tools/kvm/kvm_stat/kvm_stat.txt +2 -0
@@ -34,6 +34,8 @@ INTERACTIVE COMMANDS *c*:: clear filter *f*:: filter by regular expression + :: *Note*: Child events pull in their parents, and parents' stats summarize + all child events, not just the filtered ones *g*:: filter by guest name/PID
Signature · 1 line
2.20.1
Greg Kroah-Hartman
maintainerPATCH 95/115 drm/vmwgfx: integer underflow in vmw_cmd_dx_set_shader() leading to an invalid read
In reply to Greg Kroah-HartmanFrom: Murray McAllister <[email protected]>
commit 5ed7f4b5eca11c3c69e7c8b53e4321812bc1ee1e upstream.
If SVGA_3D_CMD_DX_SET_SHADER is called with a shader ID
of SVGA3D_INVALID_ID, and a shader type of SVGA3D_SHADERTYPE_INVALID, the calculated binding.shader_slot will be 4294967295, leading to an out-of-bounds read in vmw_binding_loc() when the offset is calculated.
--- drivers/gpu/drm/vmwgfx/vmwgfx_execbuf.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-)
drivers/gpu/drm/vmwgfx/vmwgfx_execbuf.c +2 -1
@@ -2351,7 +2351,8 @@ static int vmw_cmd_dx_set_shader(struct cmd =container_of (header,typeof (*cmd), header); -if (cmd->body.type >=SVGA3D_SHADERTYPE_DX10_MAX ) { +if (cmd->body.type >=SVGA3D_SHADERTYPE_DX10_MAX || + cmd->body.type <SVGA3D_SHADERTYPE_MIN ) {DRM_ERROR ("Illegal shader type %u.\n" , (unsigned ) cmd->body.type);return -EINVAL ;
Greg Kroah-Hartman
maintainerPATCH 96/115 drm/vmwgfx: NULL pointer dereference from vmw_cmd_dx_view_define()
In reply to Greg Kroah-HartmanFrom: Murray McAllister <[email protected]>
commit bcd6aa7b6cbfd6f985f606c6f76046d782905820 upstream.
If SVGA_3D_CMD_DX_DEFINE_RENDERTARGET_VIEW is called with a surface ID of SVGA3D_INVALID_ID, the srf struct will remain NULL after vmw_cmd_res_check(), leading to a null pointer dereference in vmw_view_add().
--- drivers/gpu/drm/vmwgfx/vmwgfx_execbuf.c | 4 ++++ 1 file changed, 4 insertions(+)
drivers/gpu/drm/vmwgfx/vmwgfx_execbuf.c +4 -0
@@ -2588,6 +2588,10 @@ static int vmw_cmd_dx_view_define(structif (view_type == vmw_view_max)return -EINVAL ; cmd =container_of (header,typeof (*cmd), header); +if (unlikely (cmd->sid ==SVGA3D_INVALID_ID )) { +DRM_ERROR ("Invalid surface id.\n" ); +return -EINVAL ; + } ret =vmw_cmd_res_check (dev_priv, sw_context, vmw_res_surface, user_surface_converter, &cmd->sid, &srf);
Greg Kroah-Hartman
maintainerPATCH 97/115 usb: dwc2: Fix DMA cache alignment issues
In reply to Greg Kroah-HartmanFrom: Martin Schiller <[email protected]>
commit 4a4863bf2e7932e584a3a462d3c6daf891142ddc upstream.
Insert a padding between data and the stored_xfer_buffer pointer to ensure they are not on the same cache line.
Otherwise, the stored_xfer_buffer gets corrupted for IN URBs on non-cache-coherent systems. (In my case: Lantiq xRX200 MIPS)
--- drivers/usb/dwc2/hcd.c | 10 +++++++--- 1 file changed, 7 insertions(+), 3 deletions(-)
drivers/usb/dwc2/hcd.c +7 -3
@@ -2664,8 +2664,10 @@ static void dwc2_free_dma_aligned_bufferreturn ;/* Restore urb->transfer_buffer from the end of the allocated area */ -memcpy (&stored_xfer_buffer, urb->transfer_buffer + - urb->transfer_buffer_length,sizeof (urb->transfer_buffer)); +memcpy (&stored_xfer_buffer, +PTR_ALIGN (urb->transfer_buffer + urb->transfer_buffer_length, +dma_get_cache_alignment ()), +sizeof (urb->transfer_buffer));if (usb_urb_dir_in (urb)) {if (usb_pipeisoc (urb->pipe))
@@ -2697,6 +2699,7 @@ static int dwc2_alloc_dma_aligned_buffer* DMA */ kmalloc_size = urb->transfer_buffer_length + + (dma_get_cache_alignment () -1 ) +sizeof (urb->transfer_buffer); kmalloc_ptr =kmalloc (kmalloc_size, mem_flags);
@@ -2707,7 +2710,8 @@ static int dwc2_alloc_dma_aligned_buffer* Position value of original urb->transfer_buffer pointer to the end * of allocation for later referencing */ -memcpy (kmalloc_ptr + urb->transfer_buffer_length, +memcpy (PTR_ALIGN (kmalloc_ptr + urb->transfer_buffer_length, +dma_get_cache_alignment ()), &urb->transfer_buffer,sizeof (urb->transfer_buffer));if (usb_urb_dir_out (urb))
Greg Kroah-Hartman
maintainerPATCH 98/115 usb: dwc2: host: Fix wMaxPacketSize handling (fix webcam regression)
In reply to Greg Kroah-HartmanFrom: Douglas Anderson <[email protected]>
commit babd183915e91a64e976b9e8ab682bb56624df76 upstream.
In commit abb621844f6a ("usb: ch9: make usb_endpoint_maxp() return only packet size") the API to usb_endpoint_maxp() changed. It used to just return wMaxPacketSize but after that commit it returned wMaxPacketSize with the high bits (the multiplier) masked off. If you wanted to get the multiplier it was now up to your code to call the new usb_endpoint_maxp_mult() which was introduced in
commit 541b6fe63023 ("usb: add helper to extract bits 12:11 of wMaxPacketSize").
Prior to the API change most host drivers were updated, but no update was made to dwc2. Presumably it was assumed that dwc2 was too simplistic to use the multiplier and thus just didn't support a certain class of USB devices. However, it turns out that dwc2 did use the multiplier and many devices using it were working quite nicely. That means that many USB devices have been broken since the API change. One such device is a Logitech HD Pro Webcam C920.
Specifically, though dwc2 didn't directly call usb_endpoint_maxp(), it did call usb_maxpacket() which in turn called usb_endpoint_maxp().
Let's update dwc2 to work properly with the new API.
--- drivers/usb/dwc2/hcd.c | 29 +++++++++++++++++------------ drivers/usb/dwc2/hcd.h | 20 +++++++++++--------- drivers/usb/dwc2/hcd_intr.c | 5 +++-- drivers/usb/dwc2/hcd_queue.c | 10 ++++++---- 4 files changed, 37 insertions(+), 27 deletions(-)
drivers/usb/dwc2/hcd.c +17 -12
@@ -2796,7 +2796,7 @@ static int dwc2_assign_and_init_hc(struc chan->dev_addr =dwc2_hcd_get_dev_addr (&urb->pipe_info); chan->ep_num =dwc2_hcd_get_ep_num (&urb->pipe_info); chan->speed = qh->dev_speed; - chan->max_packet =dwc2_max_packet (qh->maxp); + chan->max_packet = qh->maxp; chan->xfer_started =0 ; chan->halt_status =DWC2_HC_XFER_NO_HALT_STATUS ;
@@ -2874,7 +2874,7 @@ static int dwc2_assign_and_init_hc(struc* This value may be modified when the transfer is started * to reflect the actual transfer length */ - chan->multi_count =dwc2_hb_mult (qh->maxp); + chan->multi_count = qh->maxp_mult;if (hsotg->params.dma_desc_enable) { chan->desc_list_addr = qh->desc_list_dma;
@@ -3994,19 +3994,21 @@ static struct dwc2_hcd_urb *dwc2_hcd_urbstatic void dwc2_hcd_urb_set_pipeinfo (struct dwc2_hsotg *hsotg,struct dwc2_hcd_urb *urb,u8 dev_addr, -u8 ep_num,u8 ep_type,u8 ep_dir,u16 mps) +u8 ep_num,u8 ep_type,u8 ep_dir, +u16 maxp,u16 maxp_mult) {if (dbg_perio () || ep_type ==USB_ENDPOINT_XFER_BULK || ep_type ==USB_ENDPOINT_XFER_CONTROL )dev_vdbg (hsotg->dev, -"addr=%d, ep_num=%d, ep_dir=%1x, ep_type=%1x, mps=%d\n" , - dev_addr, ep_num, ep_dir, ep_type, mps); +"addr=%d, ep_num=%d, ep_dir=%1x, ep_type=%1x, maxp=%d (%d mult)\n" , + dev_addr, ep_num, ep_dir, ep_type, maxp, maxp_mult); urb->pipe_info.dev_addr = dev_addr; urb->pipe_info.ep_num = ep_num; urb->pipe_info.pipe_type = ep_type; urb->pipe_info.pipe_dir = ep_dir; - urb->pipe_info.mps = mps; + urb->pipe_info.maxp = maxp; + urb->pipe_info.maxp_mult = maxp_mult; }/*
@@ -4097,8 +4099,9 @@ void dwc2_hcd_dump_state(struct dwc2_hsodwc2_hcd_is_pipe_in (&urb->pipe_info) ? "IN" : "OUT");dev_dbg (hsotg->dev, -" Max packet size: %d\n" , -dwc2_hcd_get_mps (&urb->pipe_info)); +" Max packet size: %d (%d mult)\n" , +dwc2_hcd_get_maxp (&urb->pipe_info), +dwc2_hcd_get_maxp_mult (&urb->pipe_info));dev_dbg (hsotg->dev," transfer_buffer: %p\n" , urb->buf);
@@ -4665,8 +4668,10 @@ static void dwc2_dump_urb_info(struct us }dev_vdbg (hsotg->dev," Speed: %s\n" , speed); -dev_vdbg (hsotg->dev," Max packet size: %d\n" , -usb_maxpacket (urb->dev, urb->pipe,usb_pipeout (urb->pipe))); +dev_vdbg (hsotg->dev," Max packet size: %d (%d mult)\n" , +usb_endpoint_maxp (&urb->ep->desc), +usb_endpoint_maxp_mult (&urb->ep->desc)); +dev_vdbg (hsotg->dev," Data buffer length: %d\n" , urb->transfer_buffer_length); dev_vdbg(hsotg->dev, " Transfer buffer: %p, Transfer DMA: %08lx\n",
@@ -4749,8 +4754,8 @@ static int _dwc2_hcd_urb_enqueue(structdwc2_hcd_urb_set_pipeinfo (hsotg, dwc2_urb,usb_pipedevice (urb->pipe),usb_pipeendpoint (urb->pipe), ep_type,usb_pipein (urb->pipe), -usb_maxpacket (urb->dev, urb->pipe, - !(usb_pipein (urb->pipe)))); +usb_endpoint_maxp (&ep->desc), +usb_endpoint_maxp_mult (&ep->desc)); buf = urb->transfer_buffer;
drivers/usb/dwc2/hcd.h +11 -9
@@ -171,7 +171,8 @@ struct dwc2_hcd_pipe_info {u8 ep_num;u8 pipe_type;u8 pipe_dir; -u16 mps; +u16 maxp; +u16 maxp_mult; };struct dwc2_hcd_iso_packet_desc {
@@ -264,6 +265,7 @@ struct dwc2_hs_transfer_time {* - USB_ENDPOINT_XFER_ISOC * @ep_is_in: Endpoint direction * @maxp: Value from wMaxPacketSize field of Endpoint Descriptor +* @maxp_mult: Multiplier for maxp * @dev_speed: Device speed. One of the following values: * - USB_SPEED_LOW * - USB_SPEED_FULL
@@ -340,6 +342,7 @@ struct dwc2_qh {u8 ep_type;u8 ep_is_in;u16 maxp; +u16 maxp_mult;u8 dev_speed;u8 data_toggle;u8 ping_state;
@@ -503,9 +506,14 @@ static inline u8 dwc2_hcd_get_pipe_type(return pipe->pipe_type; } -static inline u16 dwc2_hcd_get_mps (struct dwc2_hcd_pipe_info *pipe) +static inline u16 dwc2_hcd_get_maxp (struct dwc2_hcd_pipe_info *pipe) +{ +return pipe->maxp; +} + +static inline u16 dwc2_hcd_get_maxp_mult (struct dwc2_hcd_pipe_info *pipe) { -return pipe->mps; +return pipe->maxp_mult; }static inline u8 dwc2_hcd_get_dev_addr (struct dwc2_hcd_pipe_info *pipe)
@@ -620,12 +628,6 @@ static inline bool dbg_urb(struct urb *ustatic inline bool dbg_perio (void ) {return false; }#endif -/* High bandwidth multiplier as encoded in highspeed endpoint descriptors */ -#define dwc2_hb_mult (wmaxpacketsize) (1 + (((wmaxpacketsize) >> 11) & 0x03)) - -/* Packet size for any kind of endpoint descriptor */ -#define dwc2_max_packet (wmaxpacketsize) ((wmaxpacketsize) & 0x07ff) -/* * Returns true if frame1 index is greater than frame2 index. The comparison * is done modulo FRLISTEN_64_SIZE. This accounts for the rollover of the
drivers/usb/dwc2/hcd_intr.c +3 -2
@@ -1617,8 +1617,9 @@ static void dwc2_hc_ahberr_intr(struct ddev_err (hsotg->dev," Speed: %s\n" , speed); -dev_err (hsotg->dev," Max packet size: %d\n" , -dwc2_hcd_get_mps (&urb->pipe_info)); +dev_err (hsotg->dev," Max packet size: %d (mult %d)\n" , +dwc2_hcd_get_maxp (&urb->pipe_info), +dwc2_hcd_get_maxp_mult (&urb->pipe_info));dev_err (hsotg->dev," Data buffer length: %d\n" , urb->length);dev_err (hsotg->dev," Transfer buffer: %p, Transfer DMA: %08lx\n" , urb->buf, (unsigned long )urb->dma);
drivers/usb/dwc2/hcd_queue.c +6 -4
@@ -708,7 +708,7 @@ static void dwc2_hs_pmap_unschedule(strustatic int dwc2_uframe_schedule_split (struct dwc2_hsotg *hsotg,struct dwc2_qh *qh) { -int bytecount =dwc2_hb_mult (qh->maxp) *dwc2_max_packet (qh->maxp); +int bytecount = qh->maxp_mult * qh->maxp;int ls_search_slice;int err =0 ;int host_interval_in_sched;
@@ -1332,7 +1332,7 @@ static int dwc2_check_max_xfer_size(struu32 max_channel_xfer_size;int status =0 ; - max_xfer_size =dwc2_max_packet (qh->maxp) *dwc2_hb_mult (qh->maxp); + max_xfer_size = qh->maxp * qh->maxp_mult; max_channel_xfer_size = hsotg->params.max_transfer_size;if (max_xfer_size > max_channel_xfer_size) {
@@ -1517,8 +1517,9 @@ static void dwc2_qh_init(struct dwc2_hsou32 prtspd = (hprt &HPRT0_SPD_MASK ) >>HPRT0_SPD_SHIFT ;bool do_split = (prtspd ==HPRT0_SPD_HIGH_SPEED && dev_speed !=USB_SPEED_HIGH ); -int maxp =dwc2_hcd_get_mps (&urb->pipe_info); -int bytecount =dwc2_hb_mult (maxp) *dwc2_max_packet (maxp); +int maxp =dwc2_hcd_get_maxp (&urb->pipe_info); +int maxp_mult =dwc2_hcd_get_maxp_mult (&urb->pipe_info); +int bytecount = maxp_mult * maxp;char *speed, *type;/* Initialize QH */
@@ -1531,6 +1532,7 @@ static void dwc2_qh_init(struct dwc2_hso qh->data_toggle =DWC2_HC_PID_DATA0 ; qh->maxp = maxp; + qh->maxp_mult = maxp_mult;INIT_LIST_HEAD (&qh->qtd_list);INIT_LIST_HEAD (&qh->qh_list_entry);
Greg Kroah-Hartman
maintainerPATCH 89/115 KVM: x86/pmu: mask the result of rdpmc according to the width of the counters
In reply to Greg Kroah-Hartman[ Upstream commit 0e6f467ee28ec97f68c7b74e35ec1601bb1368a7 ]
This patch will simplify the changes in the next, by enforcing the masking of the counters to RDPMC and RDMSR.
--- arch/x86/kvm/pmu.c | 10 +++------- arch/x86/kvm/pmu.h | 3 ++- arch/x86/kvm/pmu_amd.c | 2 +- arch/x86/kvm/vmx/pmu_intel.c | 13 +++++++++---- 4 files changed, 15 insertions(+), 13 deletions(-)
arch/x86/kvm/pmu.c +3 -7
@@ -283,7 +283,7 @@ int kvm_pmu_rdpmc(struct kvm_vcpu *vcpu, unsigned idx, u64 *data)bool fast_mode = idx & (1u <<31 );struct kvm_pmu *pmu =vcpu_to_pmu (vcpu);struct kvm_pmc *pmc; -u64 ctr_val; +u64 mask = fast_mode ? ~0u : ~0ull ;if (!pmu->version)return 1 ;
@@ -291,15 +291,11 @@ int kvm_pmu_rdpmc(struct kvm_vcpu *vcpu, unsigned idx, u64 *data)if (is_vmware_backdoor_pmc (idx))return kvm_pmu_rdpmc_vmware (vcpu, idx, data); - pmc = kvm_x86_ops->pmu_ops->msr_idx_to_pmc (vcpu, idx); + pmc = kvm_x86_ops->pmu_ops->msr_idx_to_pmc (vcpu, idx, &mask);if (!pmc)return 1 ; - ctr_val =pmc_read_counter (pmc); -if (fast_mode) - ctr_val = (u32 )ctr_val; - - *data = ctr_val; + *data =pmc_read_counter (pmc) & mask;return 0 ; }
arch/x86/kvm/pmu.h +2 -1
@@ -25,7 +25,8 @@ struct kvm_pmu_ops {unsigned (*find_fixed_event)(int idx);bool (*pmc_is_enabled)(struct kvm_pmc *pmc);struct kvm_pmc *(*pmc_idx_to_pmc)(struct kvm_pmu *pmu,int pmc_idx); -struct kvm_pmc *(*msr_idx_to_pmc)(struct kvm_vcpu *vcpu,unsigned idx); +struct kvm_pmc *(*msr_idx_to_pmc)(struct kvm_vcpu *vcpu,unsigned idx, +u64 *mask);int (*is_valid_msr_idx)(struct kvm_vcpu *vcpu,unsigned idx);bool (*is_valid_msr)(struct kvm_vcpu *vcpu,u32 msr);int (*get_msr)(struct kvm_vcpu *vcpu,u32 msr,u64 *data);
arch/x86/kvm/pmu_amd.c +1 -1
@@ -186,7 +186,7 @@ static int amd_is_valid_msr_idx(struct kvm_vcpu *vcpu, unsigned idx) }/* idx is the ECX register of RDPMC instruction */ -static struct kvm_pmc *amd_msr_idx_to_pmc (struct kvm_vcpu *vcpu,unsigned idx) +static struct kvm_pmc *amd_msr_idx_to_pmc (struct kvm_vcpu *vcpu,unsigned idx,u64 *mask) {struct kvm_pmu *pmu =vcpu_to_pmu (vcpu);struct kvm_pmc *counters;
arch/x86/kvm/vmx/pmu_intel.c +9 -4
@@ -126,7 +126,7 @@ static int intel_is_valid_msr_idx(struct kvm_vcpu *vcpu, unsigned idx) }static struct kvm_pmc *intel_msr_idx_to_pmc (struct kvm_vcpu *vcpu, -unsigned idx) +unsigned idx,u64 *mask) {struct kvm_pmu *pmu =vcpu_to_pmu (vcpu);bool fixed = idx & (1u <<30 );
@@ -138,6 +138,7 @@ static struct kvm_pmc *intel_msr_idx_to_pmc(struct kvm_vcpu *vcpu,if (fixed && idx >= pmu->nr_arch_fixed_counters)return NULL ; counters = fixed ? pmu->fixed_counters : pmu->gp_counters; + *mask &= pmu->counter_bitmask[fixed ?KVM_PMC_FIXED :KVM_PMC_GP ];return &counters[idx]; }
@@ -183,9 +184,13 @@ static int intel_pmu_get_msr(struct kvm_vcpu *vcpu, u32 msr, u64 *data) *data = pmu->global_ovf_ctrl;return 0 ;default : -if ((pmc =get_gp_pmc (pmu, msr,MSR_IA32_PERFCTR0 )) || - (pmc =get_fixed_pmc (pmu, msr))) { - *data =pmc_read_counter (pmc); +if ((pmc =get_gp_pmc (pmu, msr,MSR_IA32_PERFCTR0 ))) { +u64 val =pmc_read_counter (pmc); + *data = val & pmu->counter_bitmask[KVM_PMC_GP ]; +return 0 ; + }else if ((pmc =get_fixed_pmc (pmu, msr))) { +u64 val =pmc_read_counter (pmc); + *data = val & pmu->counter_bitmask[KVM_PMC_FIXED ];return 0 ; }else if ((pmc =get_gp_pmc (pmu, msr,MSR_P6_EVNTSEL0 ))) { *data = pmc->eventsel;
Signature · 1 line
2.20.1
Greg Kroah-Hartman
maintainerPATCH 115/115 powerpc/64s: Fix THP PMD collapse serialisation
In reply to Greg Kroah-HartmanFrom: Nicholas Piggin <[email protected]>
commit 33258a1db165cf43a9e6382587ad06e9b7f8187c upstream.
Commit 1b2443a547f9 ("powerpc/book3s64: Avoid multiple endian conversion in pte helpers") changed the actual bitwise tests in pte_access_permitted by using pte_write() and pte_present() helpers rather than raw bitwise testing _PAGE_WRITE and _PAGE_PRESENT bits.
The pte_present() change now returns true for PTEs which are !_PAGE_PRESENT and _PAGE_INVALID, which is the combination used by pmdp_invalidate() to synchronize access from lock-free lookups. pte_access_permitted() is used by pmd_access_permitted(), so allowing GUP lock free access to proceed with such PTEs breaks this synchronisation.
This bug has been observed on a host using the hash page table MMU, with random crashes and corruption in guests, usually together with bad PMD messages in the host.
Fix this by adding an explicit check in pmd_access_permitted(), and documenting the condition explicitly.
The pte_write() change should be okay, and would prevent GUP from falling back to the slow path when encountering savedwrite PTEs, which matches what x86 (that does not implement savedwrite) does.
--- arch/powerpc/include/asm/book3s/64/pgtable.h | 30 +++++++++++++++++++++++++++ arch/powerpc/mm/pgtable-book3s64.c | 3 ++ 2 files changed, 33 insertions(+)
arch/powerpc/include/asm/book3s/64/pgtable.h +30 -0
@@ -875,6 +875,23 @@ static inline int pmd_present(pmd_t pmd)return false; } +static inline int pmd_is_serializing (pmd_t pmd) +{ +/* +* If the pmd is undergoing a split, the _PAGE_PRESENT bit is clear +* and _PAGE_INVALID is set (see pmd_present, pmdp_invalidate). +* +* This condition may also occur when flushing a pmd while flushing +* it (see ptep_modify_prot_start), so callers must ensure this +* case is fine as well. +*/ +if ((pmd_raw (pmd) &cpu_to_be64 (_PAGE_PRESENT | _PAGE_INVALID)) == +cpu_to_be64 (_PAGE_INVALID)) +return true; + +return false; +} +static inline int pmd_bad (pmd_t pmd) {if (radix_enabled ())
@@ -1090,6 +1107,19 @@ static inline int pmd_protnone(pmd_t pmd#define pmd_access_permitted pmd_access_permittedstatic inline bool pmd_access_permitted (pmd_t pmd,bool write) { +/* +* pmdp_invalidate sets this combination (which is not caught by +* !pte_present() check in pte_access_permitted), to prevent +* lock-free lookups, as part of the serialize_against_pte_lookup() +* synchronisation. +* +* This also catches the case where the PTE's hardware PRESENT bit is +* cleared while TLB is flushed, which is suboptimal but should not +* be frequent. +*/ +if (pmd_is_serializing (pmd)) +return false; +return pte_access_permitted (pmd_pte (pmd), write); }
arch/powerpc/mm/pgtable-book3s64.c +3 -0
@@ -116,6 +116,9 @@ pmd_t pmdp_invalidate(struct vm_area_str/* * This ensures that generic code that rely on IRQ disabling * to prevent a parallel THP split work as expected. +* +* Marking the entry with _PAGE_INVALID && ~_PAGE_PRESENT requires +* a special case check in pmd_access_permitted. */ serialize_against_pte_lookup (vma->vm_mm);return __pmd (old_pmd);
Greg Kroah-Hartman
maintainerPATCH 114/115 powerpc: Fix kexec failure on book3s/32
In reply to Greg Kroah-HartmanFrom: Christophe Leroy <[email protected]>
commit 6c284228eb356a1ec62a704b4d2329711831eaed upstream.
In the old days, _PAGE_EXEC didn't exist on 6xx aka book3s/32. Therefore, allthough __mapin_ram_chunk() was already mapping kernel text with PAGE_KERNEL_TEXT and the rest with PAGE_KERNEL, the entire memory was executable. Part of the memory (first 512kbytes) was mapped with BATs instead of page table, but it was also entirely mapped as executable.
In commit 385e89d5b20f ("powerpc/mm: add exec protection on powerpc 603"), we started adding exec protection to some 6xx, namely the 603, for pages mapped via pagetables.
Then, in commit 63b2bc619565 ("powerpc/mm/32s: Use BATs for STRICT_KERNEL_RWX"), the exec protection was extended to BAT mapped memory, so that really only the kernel text could be executed.
The problem here is that kexec is based on copying some code into upper part of memory then executing it from there in order to install a fresh new kernel at its definitive location.
However, the code is position independant and first part of it is just there to deactivate the MMU and jump to the second part. So it is possible to run this first part inplace instead of running the copy. Once the MMU is off, there is no protection anymore and the second part of the code will just run as before.
--- arch/powerpc/include/asm/kexec.h | 3 +++ arch/powerpc/kernel/machine_kexec_32.c | 4 +++- 2 files changed, 6 insertions(+), 1 deletion(-)
arch/powerpc/include/asm/kexec.h +3 -0
@@ -94,6 +94,9 @@ static inline bool kdump_in_progress(voireturn crashing_cpu >=0 ; } +void relocate_new_kernel (unsigned long indirection_page,unsigned long reboot_code_buffer, +unsigned long start_address)__noreturn ; +#ifdef CONFIG_KEXEC_FILE extern const struct kexec_file_ops kexec_elf64_ops;
arch/powerpc/kernel/machine_kexec_32.c +3 -1
@@ -30,7 +30,6 @@ typedef void (*relocate_new_kernel_t)(*/ void default_machine_kexec (struct kimage *image) { -extern const unsigned char relocate_new_kernel[];extern const unsigned int relocate_new_kernel_size;unsigned long page_list;unsigned long reboot_code_buffer, reboot_code_buffer_phys;
@@ -58,6 +57,9 @@ void default_machine_kexec(struct kimage reboot_code_buffer + KEXEC_CONTROL_PAGE_SIZE);printk (KERN_INFO "Bye!\n" ); +if (!IS_ENABLED (CONFIG_FSL_BOOKE ) && !IS_ENABLED (CONFIG_44x)) +relocate_new_kernel (page_list, reboot_code_buffer_phys, image->start); +/* now call it */ rnk = (relocate_new_kernel_t ) reboot_code_buffer; (*rnk)(page_list, reboot_code_buffer_phys, image->start);
Greg Kroah-Hartman
maintainerPATCH 90/115 KVM: x86/pmu: do not mask the value that is written to fixed PMUs
In reply to Greg Kroah-Hartman[ Upstream commit 2924b52117b2812e9633d5ea337333299166d373 ]
According to the SDM, for MSR_IA32_PERFCTR0/1 "the lower-order 32 bits of each MSR may be written with any value, and the high-order 8 bits are sign-extended according to the value of bit 31", but the fixed counters in real hardware are limited to the width of the fixed counters ("bits beyond the width of the fixed-function counter are reserved and must be written as zeros"). Fix KVM to do the same.
--- arch/x86/kvm/vmx/pmu_intel.c | 13 ++++++++----- 1 file changed, 8 insertions(+), 5 deletions(-)
arch/x86/kvm/vmx/pmu_intel.c +8 -5
@@ -240,11 +240,14 @@ static int intel_pmu_set_msr(struct kvm_vcpu *vcpu, struct msr_data *msr_info) }break ;default : -if ((pmc =get_gp_pmc (pmu, msr,MSR_IA32_PERFCTR0 )) || - (pmc =get_fixed_pmc (pmu, msr))) { -if (!msr_info->host_initiated) - data = (s64 )(s32 )data; - pmc->counter += data -pmc_read_counter (pmc); +if ((pmc =get_gp_pmc (pmu, msr,MSR_IA32_PERFCTR0 ))) { +if (msr_info->host_initiated) + pmc->counter = data; +else + pmc->counter = (s32 )data; +return 0 ; + }else if ((pmc =get_fixed_pmc (pmu, msr))) { + pmc->counter = data;return 0 ; }else if ((pmc =get_gp_pmc (pmu, msr,MSR_P6_EVNTSEL0 ))) {if (data == pmc->eventsel)
Signature · 1 line
2.20.1
Greg Kroah-Hartman
maintainerPATCH 50/115 bpf: sockmap remove duplicate queue free
In reply to Greg Kroah-Hartman[ Upstream commit c42253cc88206fd0e9868c8b2fd7f9e79f9e0e03 ]
In tcp bpf remove we free the cork list and purge the ingress msg list. However we do this before the ref count reaches zero so it could be possible some other access is in progress. In this case (tcp close and/or tcp_unhash) we happen to also hold the sock lock so no path exists but lets fix it otherwise it is extremely fragile and breaks the reference counting rules. Also we already check the cork list and ingress msg queue and free them once the ref count reaches zero so its wasteful to check twice.
--- net/ipv4/tcp_bpf.c | 2 -- 1 file changed, 2 deletions(-)
net/ipv4/tcp_bpf.c +0 -2
@@ -528,8 +528,6 @@ static void tcp_bpf_remove(struct sock *sk, struct sk_psock *psock) {struct sk_psock_link *link; -sk_psock_cork_free (psock); -__sk_psock_purge_ingress_msg (psock);while ((link =sk_psock_link_pop (psock))) {sk_psock_unlink (sk, link);sk_psock_free_link (link);
Signature · 1 line
2.20.1
Greg Kroah-Hartman
maintainerPATCH 46/115 Drivers: misc: fix out-of-bounds access in function param_set_kgdbts_var
In reply to Greg Kroah-Hartman[ Upstream commit b281218ad4311a0342a40cb02fb17a363df08b48 ]
There is an out-of-bounds access to "config[len - 1]" array when the variable "len" is zero.
See commit dada6a43b040 ("kgdboc: fix KASAN global-out-of-bounds bug in param_set_kgdboc_var()") for details.
--- drivers/misc/kgdbts.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
drivers/misc/kgdbts.c +2 -2
@@ -1135,7 +1135,7 @@ static void kgdbts_put_char(u8 chr)static int param_set_kgdbts_var (const char *kmessage,const struct kernel_param *kp) { -int len =strlen (kmessage); +size_t len =strlen (kmessage);if (len >=MAX_CONFIG_LEN ) {printk (KERN_ERR "kgdbts: config string too long\n" );
@@ -1155,7 +1155,7 @@ static int param_set_kgdbts_var(const char *kmessage,strcpy (config, kmessage);/* Chop out \n char as a result of echo */ -if (config[len -1 ] =='\n' ) +if (len && config[len -1 ] =='\n' ) config[len -1 ] ='\0' ;/* Go and configure with the new params. */
Signature · 1 line
2.20.1
Greg Kroah-Hartman
maintainerPATCH 88/115 KVM: x86: do not spam dmesg with VMCS/VMCB dumps
In reply to Greg Kroah-Hartman[ Upstream commit 6f2f84532c153d32a5e53b6083b06a3e24368d30 ]
Userspace can easily set up invalid processor state in such a way that dmesg will be filled with VMCS or VMCB dumps. Disable this by default using a module parameter.
--- arch/x86/kvm/svm.c | 9 ++++++++- arch/x86/kvm/vmx/vmx.c | 26 +++++++++++++++++++------- 2 files changed, 27 insertions(+), 8 deletions(-)
arch/x86/kvm/svm.c +8 -1
@@ -379,6 +379,9 @@ module_param(vgif, int, 0444);static int sev =IS_ENABLED (CONFIG_AMD_MEM_ENCRYPT_ACTIVE_BY_DEFAULT );module_param (sev, int,0444 ); +static bool __read_mostly dump_invalid_vmcb =0 ; +module_param (dump_invalid_vmcb, bool,0644 ); +static u8 rsm_ins_bytes[] ="\x0f\xaa" ;static void svm_set_cr0 (struct kvm_vcpu *vcpu,unsigned long cr0);
@@ -4834,6 +4837,11 @@ static void dump_vmcb(struct kvm_vcpu *vcpu)struct vmcb_control_area *control = &svm->vmcb->control;struct vmcb_save_area *save = &svm->vmcb->save; +if (!dump_invalid_vmcb) { +pr_warn_ratelimited ("set kvm_amd.dump_invalid_vmcb=1 to dump internal KVM state.\n" ); +return ; + } +pr_err ("VMCB Control Area:\n" );pr_err ("%-20s%04x\n" ,"cr_read:" , control->intercept_cr &0xffff );pr_err ("%-20s%04x\n" ,"cr_write:" , control->intercept_cr >>16 );
@@ -4992,7 +5000,6 @@ static int handle_exit(struct kvm_vcpu *vcpu) kvm_run->exit_reason =KVM_EXIT_FAIL_ENTRY ; kvm_run->fail_entry.hardware_entry_failure_reason = svm->vmcb->control.exit_code; -pr_err ("KVM: FAILED VMRUN WITH VMCB:\n" );dump_vmcb (vcpu);return 0 ; }
arch/x86/kvm/vmx/vmx.c +19 -7
@@ -114,6 +114,9 @@ static u64 __read_mostly host_xss;bool __read_mostly enable_pml =1 ;module_param_named (pml, enable_pml, bool,S_IRUGO ); +static bool __read_mostly dump_invalid_vmcs =0 ; +module_param (dump_invalid_vmcs, bool,0644 ); +#define MSR_BITMAP_MODE_X2APIC 1#define MSR_BITMAP_MODE_X2APIC_APICV 2
@@ -5605,15 +5608,24 @@ static void vmx_dump_dtsel(char *name, uint32_t limit)void dump_vmcs (void ) { -u32 vmentry_ctl =vmcs_read32 (VM_ENTRY_CONTROLS ); -u32 vmexit_ctl =vmcs_read32 (VM_EXIT_CONTROLS ); -u32 cpu_based_exec_ctrl =vmcs_read32 (CPU_BASED_VM_EXEC_CONTROL ); -u32 pin_based_exec_ctrl =vmcs_read32 (PIN_BASED_VM_EXEC_CONTROL ); -u32 secondary_exec_control =0 ; -unsigned long cr4 =vmcs_readl (GUEST_CR4 ); -u64 efer =vmcs_read64 (GUEST_IA32_EFER ); +u32 vmentry_ctl, vmexit_ctl; +u32 cpu_based_exec_ctrl, pin_based_exec_ctrl, secondary_exec_control; +unsigned long cr4; +u64 efer;int i, n; +if (!dump_invalid_vmcs) { +pr_warn_ratelimited ("set kvm_intel.dump_invalid_vmcs=1 to dump internal KVM state.\n" ); +return ; + } + + vmentry_ctl =vmcs_read32 (VM_ENTRY_CONTROLS ); + vmexit_ctl =vmcs_read32 (VM_EXIT_CONTROLS ); + cpu_based_exec_ctrl =vmcs_read32 (CPU_BASED_VM_EXEC_CONTROL ); + pin_based_exec_ctrl =vmcs_read32 (PIN_BASED_VM_EXEC_CONTROL ); + cr4 =vmcs_readl (GUEST_CR4 ); + efer =vmcs_read64 (GUEST_IA32_EFER ); + secondary_exec_control =0 ;if (cpu_has_secondary_exec_ctrls ()) secondary_exec_control =vmcs_read32 (SECONDARY_VM_EXEC_CONTROL );
Signature · 1 line
2.20.1
Greg Kroah-Hartman
maintainerPATCH 84/115 KVM: nVMX: really fix the size checks on KVM_SET_NESTED_STATE
In reply to Greg Kroah-Hartman[ Upstream commit db80927ea1977a845230a161df643b48fd1e1ea4 ]
The offset for reading the shadow VMCS is sizeof(*kvm_state)+VMCS12_SIZE, so the correct size must be that plus sizeof(*vmcs12). This could lead to KVM reading garbage data from userspace and not reporting an error, but is otherwise not sensitive.
--- arch/x86/kvm/vmx/nested.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
arch/x86/kvm/vmx/nested.c +1 -1
@@ -5467,7 +5467,7 @@ static int vmx_set_nested_state(struct kvm_vcpu *vcpu, vmcs12->vmcs_link_pointer != -1ull) {struct vmcs12 *shadow_vmcs12 =get_shadow_vmcs12 (vcpu); -if (kvm_state->size <sizeof (*kvm_state) +2 *sizeof (*vmcs12)) +if (kvm_state->size <sizeof (*kvm_state) +VMCS12_SIZE +sizeof (*vmcs12))return -EINVAL ; if (copy_from_user(shadow_vmcs12,
Signature · 1 line
2.20.1
Greg Kroah-Hartman
maintainerPATCH 45/115 Revert "ALSA: seq: Protect in-kernel ioctl calls with mutex"
In reply to Greg Kroah-Hartman[ Upstream commit f0654ba94e33699b295ce4f3dc73094db6209035 ]
This reverts commit feb689025fbb6f0aa6297d3ddf97de945ea4ad32.
The fix attempt was incorrect, leading to the mutex deadlock through the close of OSS sequencer client. The proper fix needs more consideration, so let's revert it now.
--- sound/core/seq/seq_clientmgr.c | 9 ++------- 1 file changed, 2 insertions(+), 7 deletions(-)
sound/core/seq/seq_clientmgr.c +2 -7
@@ -2337,19 +2337,14 @@ int snd_seq_kernel_client_ctl(int clientid, unsigned int cmd, void *arg) {const struct ioctl_handler *handler;struct snd_seq_client *client; -int err; client =clientptr (clientid);if (client ==NULL )return -ENXIO ;for (handler = ioctl_handlers; handler->cmd >0 ; ++handler) { -if (handler->cmd == cmd) { -mutex_lock (&client->ioctl_mutex); - err = handler->func (client, arg); -mutex_unlock (&client->ioctl_mutex); -return err; - } +if (handler->cmd == cmd) +return handler->func (client, arg); } pr_debug("ALSA: seq unknown ioctl() 0x%x (type='%c', number=0x%02x)\n",
Signature · 1 line
2.20.1
Greg Kroah-Hartman
maintainerPATCH 76/115 libnvdimm: Fix compilation warnings with W=1
In reply to Greg Kroah-Hartman[ Upstream commit c01dafad77fea8d64c4fdca0a6031c980842ad65 ]
Several places (dimm_devs.c, core.c etc) include label.h but only label.c uses NSINDEX_SIGNATURE, so move its definition to label.c instead.
In file included from drivers/nvdimm/dimm_devs.c:23:drivers/nvdimm/label.h:41:19: warning: 'NSINDEX_SIGNATURE' defined but not used [-Wunused-const-variable=]
Also, some places abuse "/**" which is only reserved for the kernel-doc.
drivers/nvdimm/bus.c:648: warning: cannot understand function prototype:
'struct attribute_group nd_device_attribute_group = ' drivers/nvdimm/bus.c:677: warning: cannot understand function prototype:
'struct attribute_group nd_numa_attribute_group = '
Those are just some member assignments for the "struct attribute_group" instances and it can't be expressed in the kernel-doc.
--- drivers/nvdimm/bus.c | 4 ++-- drivers/nvdimm/label.c | 2 ++ drivers/nvdimm/label.h | 2 -- 3 files changed, 4 insertions(+), 4 deletions(-)
drivers/nvdimm/bus.c +2 -2
@@ -642,7 +642,7 @@ static struct attribute *nd_device_attributes[] = { NULL, }; -/** +/* * nd_device_attribute_group - generic attributes for all devices on an nd bus */ struct attribute_group nd_device_attribute_group = {
@@ -671,7 +671,7 @@ static umode_t nd_numa_attr_visible(struct kobject *kobj, struct attribute *a,return a->mode; } -/** +/* * nd_numa_attribute_group - NUMA attributes for all devices on an nd bus */ struct attribute_group nd_numa_attribute_group = {
drivers/nvdimm/label.c +2 -0
@@ -25,6 +25,8 @@ static guid_t nvdimm_btt2_guid;static guid_t nvdimm_pfn_guid;static guid_t nvdimm_dax_guid; +static const char NSINDEX_SIGNATURE [] ="NAMESPACE_INDEX\0" ; +static u32 best_seq (u32 a,u32 b) { a &=NSINDEX_SEQ_MASK ;
drivers/nvdimm/label.h +0 -2
@@ -38,8 +38,6 @@ enum { ND_NSINDEX_INIT = 0x1, }; -static const char NSINDEX_SIGNATURE [] ="NAMESPACE_INDEX\0" ; -/** * struct nd_namespace_index - label set superblock * @sig: NAMESPACE_INDEX\0
Signature · 1 line
2.20.1
Greg Kroah-Hartman
maintainerPATCH 69/115 nvme: release namespace SRCU protection before performing controller ioctls
In reply to Greg Kroah-Hartman[ Upstream commit 5fb4aac756acacf260b9ebd88747251effa3a2f2 ]
Holding the SRCU critical section protecting the namespace list can cause deadlocks when using the per-namespace admin passthrough ioctl to delete as namespace. Release it earlier when performing per-controller ioctls to avoid that.
--- drivers/nvme/host/core.c | 25 ++++++++++++++++++++----- 1 file changed, 20 insertions(+), 5 deletions(-)
drivers/nvme/host/core.c +20 -5
@@ -1395,14 +1395,31 @@ static int nvme_ioctl(struct block_device *bdev, fmode_t mode,if (unlikely (!ns))return -EWOULDBLOCK ; +/* +* Handle ioctls that apply to the controller instead of the namespace +* seperately and drop the ns SRCU reference early. This avoids a +* deadlock when deleting namespaces using the passthrough interface. +*/ +if (cmd ==NVME_IOCTL_ADMIN_CMD ||is_sed_ioctl (cmd)) { +struct nvme_ctrl *ctrl = ns->ctrl; + +nvme_get_ctrl (ns->ctrl); +nvme_put_ns_from_disk (head, srcu_idx); + +if (cmd ==NVME_IOCTL_ADMIN_CMD ) + ret =nvme_user_cmd (ctrl,NULL , argp); +else + ret =sed_ioctl (ctrl->opal_dev, cmd, argp); + +nvme_put_ctrl (ctrl); +return ret; + } +switch (cmd) {case NVME_IOCTL_ID :force_successful_syscall_return (); ret = ns->head->ns_id;break ; -case NVME_IOCTL_ADMIN_CMD : - ret =nvme_user_cmd (ns->ctrl,NULL , argp); -break ;case NVME_IOCTL_IO_CMD : ret =nvme_user_cmd (ns->ctrl, ns, argp);break ;
@@ -1412,8 +1429,6 @@ static int nvme_ioctl(struct block_device *bdev, fmode_t mode,default :if (ns->ndev) ret =nvme_nvm_ioctl (ns, cmd, arg); -else if (is_sed_ioctl (cmd)) - ret =sed_ioctl (ns->ctrl->opal_dev, cmd, argp);else ret = -ENOTTY ; }
Signature · 1 line
2.20.1
Greg Kroah-Hartman
maintainerPATCH 43/115 ALSA: seq: Protect in-kernel ioctl calls with mutex
In reply to Greg Kroah-Hartman[ Upstream commit feb689025fbb6f0aa6297d3ddf97de945ea4ad32 ]
ALSA OSS sequencer calls the ioctl function indirectly via snd_seq_kernel_client_ctl(). While we already applied the protection against races between the normal ioctls and writes via the client's ioctl_mutex, this code path was left untouched. And this seems to be the cause of still remaining some rare UAF as spontaneously triggered by syzkaller.
For the sake of robustness, wrap the ioctl_mutex also for the call via snd_seq_kernel_client_ctl(), too.
--- sound/core/seq/seq_clientmgr.c | 9 +++++++-- 1 file changed, 7 insertions(+), 2 deletions(-)
sound/core/seq/seq_clientmgr.c +7 -2
@@ -2343,14 +2343,19 @@ int snd_seq_kernel_client_ctl(int clientid, unsigned int cmd, void *arg) {const struct ioctl_handler *handler;struct snd_seq_client *client; +int err; client =clientptr (clientid);if (client ==NULL )return -ENXIO ;for (handler = ioctl_handlers; handler->cmd >0 ; ++handler) { -if (handler->cmd == cmd) -return handler->func (client, arg); +if (handler->cmd == cmd) { +mutex_lock (&client->ioctl_mutex); + err = handler->func (client, arg); +mutex_unlock (&client->ioctl_mutex); +return err; + } } pr_debug("ALSA: seq unknown ioctl() 0x%x (type='%c', number=0x%02x)\n",
Signature · 1 line
2.20.1
Greg Kroah-Hartman
maintainerPATCH 56/115 scsi: lpfc: correct rcu unlock issue in lpfc_nvme_info_show
In reply to Greg Kroah-Hartman[ Upstream commit 79080d349f7f58a2e86c56043a3d04184d5f294a ]
Many of the exit cases were not releasing the rcu read lock. Corrected the exit paths.
--- drivers/scsi/lpfc/lpfc_attr.c | 32 +++++++++++++++++++------------- 1 file changed, 19 insertions(+), 13 deletions(-)
drivers/scsi/lpfc/lpfc_attr.c +19 -13
@@ -338,7 +338,7 @@ lpfc_nvme_info_show(struct device *dev, struct device_attribute *attr, phba->sli4_hba.io_xri_max, lpfc_sli4_get_els_iocb_cnt(phba));if (strlcat (buf, tmp,PAGE_SIZE ) >=PAGE_SIZE ) - goto buffer_done; + goto rcu_unlock_buf_done;/* Port state is only one of two values for now. */ if (localport->port_id)
@@ -354,7 +354,7 @@ lpfc_nvme_info_show(struct device *dev, struct device_attribute *attr,wwn_to_u64 (vport->fc_nodename.u.wwn), localport->port_id, statep);if (strlcat (buf, tmp,PAGE_SIZE ) >=PAGE_SIZE ) - goto buffer_done; + goto rcu_unlock_buf_done;list_for_each_entry (ndlp, &vport->fc_nodes, nlp_listp) { nrport =NULL ;
@@ -381,39 +381,39 @@ lpfc_nvme_info_show(struct device *dev, struct device_attribute *attr,/* Tab in to show lport ownership. */ if (strlcat (buf,"NVME RPORT " ,PAGE_SIZE ) >=PAGE_SIZE ) - goto buffer_done; + goto rcu_unlock_buf_done;if (phba->brd_no >=10 ) {if (strlcat (buf," " ,PAGE_SIZE ) >=PAGE_SIZE ) - goto buffer_done; + goto rcu_unlock_buf_done; }scnprintf (tmp,sizeof (tmp),"WWPN x%llx " , nrport->port_name);if (strlcat (buf, tmp,PAGE_SIZE ) >=PAGE_SIZE ) - goto buffer_done; + goto rcu_unlock_buf_done;scnprintf (tmp,sizeof (tmp),"WWNN x%llx " , nrport->node_name);if (strlcat (buf, tmp,PAGE_SIZE ) >=PAGE_SIZE ) - goto buffer_done; + goto rcu_unlock_buf_done;scnprintf (tmp,sizeof (tmp),"DID x%06x " , nrport->port_id);if (strlcat (buf, tmp,PAGE_SIZE ) >=PAGE_SIZE ) - goto buffer_done; + goto rcu_unlock_buf_done;/* An NVME rport can have multiple roles. */ if (nrport->port_role &FC_PORT_ROLE_NVME_INITIATOR ) {if (strlcat (buf,"INITIATOR " ,PAGE_SIZE ) >=PAGE_SIZE ) - goto buffer_done; + goto rcu_unlock_buf_done; }if (nrport->port_role &FC_PORT_ROLE_NVME_TARGET ) {if (strlcat (buf,"TARGET " ,PAGE_SIZE ) >=PAGE_SIZE ) - goto buffer_done; + goto rcu_unlock_buf_done; }if (nrport->port_role &FC_PORT_ROLE_NVME_DISCOVERY ) {if (strlcat (buf,"DISCSRVC " ,PAGE_SIZE ) >=PAGE_SIZE ) - goto buffer_done; + goto rcu_unlock_buf_done; } if (nrport->port_role & ~(FC_PORT_ROLE_NVME_INITIATOR | FC_PORT_ROLE_NVME_TARGET |
@@ -421,12 +421,12 @@ lpfc_nvme_info_show(struct device *dev, struct device_attribute *attr,scnprintf (tmp,sizeof (tmp),"UNKNOWN ROLE x%x" , nrport->port_role);if (strlcat (buf, tmp,PAGE_SIZE ) >=PAGE_SIZE ) - goto buffer_done; + goto rcu_unlock_buf_done; }scnprintf (tmp,sizeof (tmp),"%s\n" , statep);if (strlcat (buf, tmp,PAGE_SIZE ) >=PAGE_SIZE ) - goto buffer_done; + goto rcu_unlock_buf_done; }rcu_read_unlock ();
@@ -488,7 +488,13 @@ lpfc_nvme_info_show(struct device *dev, struct device_attribute *attr, atomic_read(&lport->cmpl_fcp_err));strlcat (buf, tmp,PAGE_SIZE ); -buffer_done: +/* RCU is already unlocked. */ + goto buffer_done; + + rcu_unlock_buf_done: +rcu_read_unlock (); + + buffer_done: len =strnlen (buf,PAGE_SIZE );if (unlikely (len >= (PAGE_SIZE -1 ))) {
Signature · 1 line
2.20.1
Greg Kroah-Hartman
maintainerPATCH 39/115 drm/i915/dsi: Use a fuzzy check for burst mode clock check
In reply to Greg Kroah-HartmanFrom: Hans de Goede <[email protected]>
commit f9a99131ce18d9dddcaa14ec2c436e42f0bbee5e upstream.
Prior to this commit we fail to init the DSI panel on the GPD MicroPC:
https://www.indiegogo.com/projects/gpd-micropc-6-inch-handheld-industry-laptop#/
The problem is intel_dsi_vbt_init() failing with the following error:
*ERROR* Burst mode freq is less than computed
The pclk in the VBT panel modeline is 70000, together with 24 bpp and 4 lines this results in a bitrate value of 70000 * 24 / 4 = 420000. But the target_burst_mode_freq in the VBT is 418000.
This commit works around this problem by adding an intel_fuzzy_clock_check when target_burst_mode_freq < bitrate and setting target_burst_mode_freq to bitrate when that checks succeeds, fixing the panel not working.
--- drivers/gpu/drm/i915/intel_display.c | 2 +- drivers/gpu/drm/i915/intel_drv.h | 1 + drivers/gpu/drm/i915/intel_dsi_vbt.c | 11 +++++++++++ 3 files changed, 13 insertions(+), 1 deletion(-)
drivers/gpu/drm/i915/intel_display.c +1 -1
@@ -11757,7 +11757,7 @@ encoder_retry:return 0 ; } -static bool intel_fuzzy_clock_check (int clock1,int clock2) +bool intel_fuzzy_clock_check (int clock1,int clock2) {int diff;
drivers/gpu/drm/i915/intel_drv.h +1 -0
@@ -1707,6 +1707,7 @@ int vlv_force_pll_on(struct drm_i915_pri const struct dpll *dpll);void vlv_force_pll_off (struct drm_i915_private *dev_priv,enum pipe pipe);int lpt_get_iclkip (struct drm_i915_private *dev_priv); +bool intel_fuzzy_clock_check (int clock1,int clock2);/* modesetting asserts */ void assert_panel_unlocked(struct drm_i915_private *dev_priv,
drivers/gpu/drm/i915/intel_dsi_vbt.c +11 -0
@@ -871,6 +871,17 @@ bool intel_dsi_vbt_init(struct intel_dsiif (mipi_config->target_burst_mode_freq) {u32 bitrate =intel_dsi_bitrate (intel_dsi); +/* +* Sometimes the VBT contains a slightly lower clock, +* then the bitrate we have calculated, in this case +* just replace it with the calculated bitrate. +*/ +if (mipi_config->target_burst_mode_freq < bitrate && +intel_fuzzy_clock_check ( + mipi_config->target_burst_mode_freq, + bitrate)) + mipi_config->target_burst_mode_freq = bitrate; +if (mipi_config->target_burst_mode_freq < bitrate) {DRM_ERROR ("Burst mode freq is less than computed\n" );return false;
Greg Kroah-Hartman
maintainerPATCH 31/115 bcache: fix stack corruption by PRECEDING_KEY()
In reply to Greg Kroah-HartmanFrom: Coly Li <[email protected]>
commit 31b90956b124240aa8c63250243ae1a53585c5e2 upstream.
Recently people report bcache code compiled with gcc9 is broken, one of the buggy behavior I observe is that two adjacent 4KB I/Os should merge into one but they don't. Finally it turns out to be a stack corruption caused by macro PRECEDING_KEY().
See how PRECEDING_KEY() is defined in bset.h,
437 #define PRECEDING_KEY(_k) \
438 ({ \
439 struct bkey *_ret = NULL; \
440 \
441 if (KEY_INODE(_k) || KEY_OFFSET(_k)) { \
442 _ret = &KEY(KEY_INODE(_k), KEY_OFFSET(_k), 0); \
443 \
444 if (!_ret->low) \
445 _ret->high--; \
446 _ret->low--; \
447 } \
448 \
449 _ret; \450 })
At line 442, _ret points to address of a on-stack variable combined by KEY(), the life range of this on-stack variable is in line 442-446, once _ret is returned to bch_btree_insert_key(), the returned address points to an invalid stack address and this address is overwritten in the following called bch_btree_iter_init(). Then argument 'search' of bch_btree_iter_init() points to some address inside stackframe of bch_btree_iter_init(), exact address depends on how the compiler allocates stack space. Now the stack is corrupted.
--- drivers/md/bcache/bset.c | 16 +++++++++++++--- drivers/md/bcache/bset.h | 34 ++++++++++++++++++++-------------- 2 files changed, 33 insertions(+), 17 deletions(-)
drivers/md/bcache/bset.c +13 -3
@@ -887,12 +887,22 @@ unsigned int bch_btree_insert_key(structstruct bset *i =bset_tree_last (b)->data;struct bkey *m, *prev =NULL ;struct btree_iter iter; +struct bkey preceding_key_on_stack =ZERO_KEY ; +struct bkey *preceding_key_p = &preceding_key_on_stack;BUG_ON (b->ops->is_extents && !KEY_SIZE (k)); - m =bch_btree_iter_init (b, &iter, b->ops->is_extents - ?PRECEDING_KEY (&START_KEY (k)) - :PRECEDING_KEY (k)); +/* +* If k has preceding key, preceding_key_p will be set to address +* of k's preceding key; otherwise preceding_key_p will be set +* to NULL inside preceding_key(). +*/ +if (b->ops->is_extents) +preceding_key (&START_KEY (k), &preceding_key_p); +else +preceding_key (k, &preceding_key_p); + + m =bch_btree_iter_init (b, &iter, preceding_key_p);if (b->ops->insert_fixup (b, k, &iter, replace_key))return status;
drivers/md/bcache/bset.h +20 -14
@@ -434,20 +434,26 @@ static inline bool bch_cut_back(const streturn __bch_cut_back (where, k); } -#define PRECEDING_KEY (_k) \ -({ \ - struct bkey *_ret = NULL; \ - \ - if (KEY_INODE(_k) || KEY_OFFSET(_k)) { \ - _ret = &KEY(KEY_INODE(_k), KEY_OFFSET(_k), 0); \ - \ - if (!_ret->low) \ - _ret->high--; \ - _ret->low--; \ - } \ - \ - _ret; \ -}) +/* +* Pointer '*preceding_key_p' points to a memory object to store preceding +* key of k. If the preceding key does not exist, set '*preceding_key_p' to +* NULL. So the caller of preceding_key() needs to take care of memory +* which '*preceding_key_p' pointed to before calling preceding_key(). +* Currently the only caller of preceding_key() is bch_btree_insert_key(), +* and it points to an on-stack variable, so the memory release is handled +* by stackframe itself. +*/ +static inline void preceding_key (struct bkey *k,struct bkey **preceding_key_p) +{ +if (KEY_INODE (k) ||KEY_OFFSET (k)) { + (**preceding_key_p) =KEY (KEY_INODE (k),KEY_OFFSET (k),0 ); +if (!(*preceding_key_p)->low) + (*preceding_key_p)->high--; + (*preceding_key_p)->low--; + }else { + (*preceding_key_p) =NULL ; + } +}static inline bool bch_ptr_invalid (struct btree_keys *b,const struct bkey *k) {
Greg Kroah-Hartman
maintainerPATCH 29/115 Smack: Restore the smackfsdef mount option and add missing prefixes
In reply to Greg Kroah-HartmanFrom: Casey Schaufler <[email protected]>
commit 6e7739fc938c1ec58d321f70ea41d9548a4cca0f upstream.
The 5.1 mount system rework changed the smackfsdef mount option to smackfsdefault. This fixes the regression by making smackfsdef treated the same way as smackfsdefault.
Also fix the smack_param_specs[] to have "smack" prefixes on all the names. This isn't visible to a user unless they either:
(a) Try to mount a filesystem that's converted to the internal mount API and that implements the ->parse_monolithic() context operation - and only then if they call security_fs_context_parse_param() rather than security_sb_eat_lsm_opts().
There are no examples of this upstream yet, but nfs will probably want to do this for nfs2 or nfs3.
(b) Use fsconfig() to configure the filesystem - in which case security_fs_context_parse_param() will be called.
This issue is that smack_sb_eat_lsm_opts() checks for the "smack" prefix on the options, but smack_fs_context_parse_param() does not.
--- security/smack/smack_lsm.c | 12 +++++++----- 1 file changed, 7 insertions(+), 5 deletions(-)
security/smack/smack_lsm.c +7 -5
@@ -67,6 +67,7 @@ static struct {int len;int opt; } smk_mount_opts[] = { + {"smackfsdef", sizeof("smackfsdef") - 1, Opt_fsdefault}, A(fsdefault), A(fsfloor), A(fshat), A(fsroot), A(fstransmute) }; #undef A
@@ -681,11 +682,12 @@ static int smack_fs_context_dup(struct f }static const struct fs_parameter_spec smack_param_specs[] = { -fsparam_string ("fsdefault" , Opt_fsdefault), -fsparam_string ("fsfloor" , Opt_fsfloor), -fsparam_string ("fshat" , Opt_fshat), -fsparam_string ("fsroot" , Opt_fsroot), -fsparam_string ("fstransmute" , Opt_fstransmute), +fsparam_string ("smackfsdef" , Opt_fsdefault), +fsparam_string ("smackfsdefault" , Opt_fsdefault), +fsparam_string ("smackfsfloor" , Opt_fsfloor), +fsparam_string ("smackfshat" , Opt_fshat), +fsparam_string ("smackfsroot" , Opt_fsroot), +fsparam_string ("smackfstransmute" , Opt_fstransmute), {} };
Greg Kroah-Hartman
maintainerPATCH 21/115 io_uring: fix memory leak of UNIX domain socket inode
In reply to Greg Kroah-HartmanFrom: Eric Biggers <[email protected]>
commit 355e8d26f719c207aa2e00e6f3cfab3acf21769b upstream.
Opening and closing an io_uring instance leaks a UNIX domain socket inode. This is because the ->file of the io_uring instance's internal UNIX domain socket is set to point to the io_uring file, but then sock_release() sees the non-NULL ->file and assumes the inode reference is held by the file so doesn't call iput(). That's not the case here, since the reference is still meant to be held by the socket; the actual inode of the io_uring file is different.
Fix this leak by NULL-ing out ->file before releasing the socket.
--- fs/io_uring.c | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-)
fs/io_uring.c +3 -1
@@ -2633,8 +2633,10 @@ static void io_ring_ctx_free(struct io_rio_sqe_files_unregister (ctx);#if defined(CONFIG_UNIX ) -if (ctx->ring_sock) +if (ctx->ring_sock) { + ctx->ring_sock->file =NULL ;/* so that iput() is called */ sock_release (ctx->ring_sock); + }#endif io_mem_free (ctx->sq_ring);
Greg Kroah-Hartman
maintainerPATCH 17/115 selinux: log raw contexts as untrusted strings
In reply to Greg Kroah-HartmanFrom: Ondrej Mosnacek <[email protected]>
commit aff7ed4851680d0d28ad9f52cd2f99213e1371b2 upstream.
These strings may come from untrusted sources (e.g. file xattrs) so they need to be properly escaped.
Reproducer:
# setenforce 0
# touch /tmp/test
# setfattr -n security.selinux -v 'kuřecí řízek' /tmp/test
# runcon system_u:system_r:sshd_t:s0 cat /tmp/test
(look at the generated AVCs)Actual result:
type=AVC [...] trawcon=kuřecí řízek
Expected result:
type=AVC [...] trawcon=6B75C5996563C3AD20C599C3AD7A656B
--- security/selinux/avc.c | 10 ++++++++-- 1 file changed, 8 insertions(+), 2 deletions(-)
security/selinux/avc.c +8 -2
@@ -739,14 +739,20 @@ static void avc_audit_post_callback(stru rc =security_sid_to_context_inval (sad->state, sad->ssid, &scontext, &scontext_len);if (!rc && scontext) { -audit_log_format (ab," srawcon=%s" , scontext); +if (scontext_len && scontext[scontext_len -1 ] =='\0' ) + scontext_len--; +audit_log_format (ab," srawcon=" ); +audit_log_n_untrustedstring (ab, scontext, scontext_len);kfree (scontext); } rc =security_sid_to_context_inval (sad->state, sad->tsid, &scontext, &scontext_len);if (!rc && scontext) { -audit_log_format (ab," trawcon=%s" , scontext); +if (scontext_len && scontext[scontext_len -1 ] =='\0' ) + scontext_len--; +audit_log_format (ab," trawcon=" ); +audit_log_n_untrustedstring (ab, scontext, scontext_len);kfree (scontext); } }
Greg Kroah-Hartman
maintainerPATCH 16/115 ALSA: firewire-motu: fix destruction of data for isochronous resources
In reply to Greg Kroah-HartmanFrom: Takashi Sakamoto <[email protected]>
commit 0e3fb6995bfabb23c172e8b883bf5ac57102678e upstream.
The data for isochronous resources is not destroyed in expected place. This commit fixes the bug.
--- sound/firewire/motu/motu-stream.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
sound/firewire/motu/motu-stream.c +1 -1
@@ -345,7 +345,7 @@ static void destroy_stream(struct snd_mo }amdtp_stream_destroy (stream); -fw_iso_resources_free (resources); +fw_iso_resources_destroy (resources); }int snd_motu_stream_init_duplex (struct snd_motu *motu)
stable-rc/linux-5.1.y boot: 118 boots: 1 failed, 117 passed (v5.1.11-116-ga1610563f19b)
stable-rc/linux-5.1.y boot: 118 boots: 1 failed, 117 passed (v5.1.11-116-ga1610563f19b)
Full Boot Summary: https://kernelci.org/boot/all/job/stable-rc/branch/linux-5.1.y/kernel/v5.1.11-116-ga1610563f19b/
Full Build Summary: https://kernelci.org/build/stable-rc/branch/linux-5.1.y/kernel/v5.1.11-116-ga1610563f19b/
Tree: stable-rc
Branch: linux-5.1.y
Git Describe: v5.1.11-116-ga1610563f19b
Git Commit: a1610563f19b8c84324c5b490e57ffd1f1bb62be
Git URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git
Tested: 70 unique boards, 24 SoC families, 15 builds out of 209
Boot Failure Detected:
arm:
multi_v7_defconfig:
gcc-8:
bcm4708-smartrg-sr400ac: 1 failed lab---
For more info write to <[email protected]>
Quoted 10 lines · Greg Kroah-Hartman
This is the start of the stable review cycle for the 5.1.12 release. There are 115 patches in this series, all will be posted as a response to this one. If anyone has any issues with these being applied, please let me know.
Responses should be made by Wed 19 Jun 2019 09:06:21 PM UTC. Anything received after that time might be too late.
The whole patch series can be found in one patch at:
Quoted 8 lines
https://www.kernel.org/pub/linux/kernel/v5.x/stable-review/patch-5.1.12-rc1.gzor in the git tree and branch at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.gitlinux-5.1.y
and the diffstat can be found below.thanks,
greg k-h
Results from Linaro’s test farm.
No regressions on arm64, arm, x86_64, and i386.
NOTE:kernel/workqueue.c:3030 __flush_work+0x2c2/0x2d0
Kernel warning is been fixed by below patch.
Quoted 2 lines
John Fastabend <[email protected]>
bpf: sockmap, only stop/flush strp if it was enabled at some point
Summary
------------------------------------------------------------------------
kernel: 5.1.12-rc1
git repo: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git
git branch: linux-5.1.y
git commit: 760bc74bb0d3cb65cdc8af61a564384ba10374ac
git describe: v5.1.11-116-g760bc74bb0d3
Test details: https://qa-reports.linaro.org/lkft/linux-stable-rc-5.1-oe/build/v5.1.11-116-g760bc74bb0d3
No regressions (compared to build v5.1.11)
No fixes (compared to build v5.1.11)
Ran 22821 total tests in the following environments and test suites.
Environments
--------------
- dragonboard-410c
- hi6220-hikey
- i386
- juno-r2
- qemu_arm
- qemu_arm64
- qemu_i386
- qemu_x86_64
- x15
- x86
Test Suites
-----------
* build
* install-android-platform-tools-r2600
* libgpiod
* ltp-containers-tests
* kselftest
* libhugetlbfs
* ltp-cap_bounds-tests
* ltp-commands-tests
* ltp-cpuhotplug-tests
* ltp-cve-tests
* ltp-dio-tests
* ltp-fcntl-locktests-tests
* ltp-filecaps-tests
* ltp-fs-tests
* ltp-fs_bind-tests
* ltp-fs_perms_simple-tests
* ltp-fsx-tests
* ltp-hugetlb-tests
* ltp-io-tests
* ltp-ipc-tests
* ltp-math-tests
* ltp-mm-tests
* ltp-nptl-tests
* ltp-pty-tests
* ltp-sched-tests
* ltp-securebits-tests
* ltp-syscalls-tests
* ltp-timers-tests
* network-basic-tests
* perf
* spectre-meltdown-checker-test
* v4l2-compliance
* ltp-open-posix-tests
* kvm-unit-tests
* kselftest-vsyscall-mode-native
* kselftest-vsyscall-mode-none
Signature · 2 lines
Linaro LKFT https://lkft.linaro.org
Greg Kroah-Hartman
maintainerQuoted 19 lines · Naresh Kamboju
Quoted 17 lines · Greg Kroah-Hartman
This is the start of the stable review cycle for the 5.1.12 release. There are 115 patches in this series, all will be posted as a response to this one. If anyone has any issues with these being applied, please let me know.
Responses should be made by Wed 19 Jun 2019 09:06:21 PM UTC. Anything received after that time might be too late.
The whole patch series can be found in one patch at:
https://www.kernel.org/pub/linux/kernel/v5.x/stable-review/patch-5.1.12-rc1.gzor in the git tree and branch at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.gitlinux-5.1.y
and the diffstat can be found below.thanks,
Quoted 11 lines
Quoted 1 line
greg k-h
Results from Linaro’s test farm.
No regressions on arm64, arm,x86_64, and i386.NOTE:
kernel/workqueue.c:3030__flush_work+0x2c2/0x2d0
Kernel warning is been fixed by below patch.Quoted 2 lines
John Fastabend <[email protected]>
bpf: sockmap, only stop/flush strp if it was enabled at some point
What is the git commit id for this patch?
thanks,
greg k-h
Quoted 9 lines · Greg Kroah-Hartman
This is the start of the stable review cycle for the 5.1.12 release. There are 115 patches in this series, all will be posted as a response to this one. If anyone has any issues with these being applied, please let me know.
Responses should be made by Wed 19 Jun 2019 09:06:21 PM UTC. Anything received after that time might be too late.
The whole patch series can be found in one patch at:
Quoted 9 lines
https://www.kernel.org/pub/linux/kernel/v5.x/stable-review/patch-5.1.12-rc1.gzor in the git tree and branch at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.gitlinux-5.1.y
and the diffstat can be found below.thanks,
greg k-h
Compiled and booted on my test system. No dmesg regressions.
thanks,
-- Shuah
Greg Kroah-Hartman
maintainerQuoted 15 lines · shuah
Quoted 14 lines · Greg Kroah-Hartman
This is the start of the stable review cycle for the 5.1.12 release. There are 115 patches in this series, all will be posted as a response to this one. If anyone has any issues with these being applied, please let me know.
Responses should be made by Wed 19 Jun 2019 09:06:21 PM UTC. Anything received after that time might be too late.
The whole patch series can be found in one patch at:
https://www.kernel.org/pub/linux/kernel/v5.x/stable-review/patch-5.1.12-rc1.gzor in the git tree and branch at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.gitlinux-5.1.y
and the diffstat can be found below.
Quoted 6 lines
Quoted 4 lines
thanks,
greg k-h
Compiled and booted on my test system. No dmesg regressions.
Thanks for testing these and letting me know.
greg k-h
Quoted 8 lines · Greg Kroah-Hartman
This is the start of the stable review cycle for the 5.1.12 release. There are 115 patches in this series, all will be posted as a response to this one. If anyone has any issues with these being applied, please let me know.
Responses should be made by Wed 19 Jun 2019 09:06:21 PM UTC. Anything received after that time might be too late.
Build results:
total: 159 pass: 159 fail: 0 Qemu test results: total: 366 pass: 366 fail: 0
Guenter
Re: [PATCH 5.1 003/115] HID: input: make sure the wheel high resolution multiplier is set
In reply to Greg Kroah-HartmanUhm - could someone please "clue me in" here?
When I look into:
'move all the pending queues back to their "real" places'
https://git.kernel.org/pub/scm/linux/kernel/git/stable/stable-queue.git/commit/?id=c5da0df8985ac2f29ffdaba77bae201121bc0e10
I can find both the "d43c17ead879ba7c076dc2f5fd80cd76047c9ff4" patch, "HID: input: make sure the wheel high resolution multiplier is set" and the "39b3c3a5fbc5d744114e497d35bf0c12f798c134" patch, "HID: input: fix assignment of .value".
I take this to mean that these patches are "in the stable-queue". But then, these patches are not "in the kernel".
So then, how do these patches go from being "in the stable-queue" to being "in the kernel"?
To the "uninitiated" and "naive", as I am, to outward appearances, the patches are "just sitting there". How do the patches get selected for inclusion into the "next" kernel revision?
Thanks
James
Greg Kroah-Hartman
maintainerRe: [PATCH 5.1 003/115] HID: input: make sure the wheel high resolution multiplier is set
Quoted 6 lines · James Feeney
Uhm - could someone please "clue me in" here?
When I look into:
'move all the pending queues back to their "real" places'
https://git.kernel.org/pub/scm/linux/kernel/git/stable/stable-queue.git/commit/?id=c5da0df8985ac2f29ffdaba77bae201121bc0e10
No need to worry about that patch, that was done because my scripts normally assume specific directory locations of the patch queues, and I had to do a kernel release that did not include the existing pending patches.
Quoted 3 lines
I can find both the "
d43c17ead879ba7c076dc2f5fd80cd76047c9ff4" patch, "HID: input: make sure the wheel high resolution multiplier is set" and the "39b3c3a5fbc5d744114e497d35bf0c12f798c134" patch, "HID: input: fix assignment of .value".I take this to mean that these patches are "in the stable-queue". But then, these patches are not "in the kernel".
Yes.
Quoted 1 line
So then, how do these patches go from being "in the stable-queue" to being "in the kernel"?
I apply them when I do the release in a few hours/days.
Quoted 3 lines
To the "uninitiated" and "naive", as I am, to outward appearances, the patches are "just sitting there". How do the patches get selected for inclusion into the "next" kernel revision?
I already selected them, sent emails saying they were selected and to what specific branches they were selected to. Then when the -rc releases happen so that people can do one final round of testing and object if I messed anything up, they get sent out again (which you responded to here.)
If all goes well, when the "deadling" passes (usually 2 days +-2 days depending on stuff), I'll do a realease and apply the patches "for real" to the different kernel branches and cut a release.
Then I start all over again...
I understand that seeing a git tree of patches in a quilt series is odd, but it is very powerful and works very very well for what we do here.
Does that help?
greg k-h
Greg Kroah-Hartman
maintainerQuoted 17 lines · Naresh Kamboju
Quoted 15 lines · Greg Kroah-Hartman
This is the start of the stable review cycle for the 5.1.12 release. There are 115 patches in this series, all will be posted as a response to this one. If anyone has any issues with these being applied, please let me know.
Responses should be made by Wed 19 Jun 2019 09:06:21 PM UTC. Anything received after that time might be too late.
The whole patch series can be found in one patch at:
https://www.kernel.org/pub/linux/kernel/v5.x/stable-review/patch-5.1.12-rc1.gzor in the git tree and branch at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.gitlinux-5.1.y
and the diffstat can be found below.
Quoted 6 lines
Quoted 3 lines
thanks,
greg k-h
Results from Linaro’s test farm.
No regressions on arm64, arm,x86_64, and i386.
Thanks for testing all of these and letting me know.
greg k-h
Greg Kroah-Hartman
maintainerQuoted 6 lines · Guenter Roeck
Quoted 5 lines · Greg Kroah-Hartman
This is the start of the stable review cycle for the 5.1.12 release. There are 115 patches in this series, all will be posted as a response to this one. If anyone has any issues with these being applied, please let me know.
Quoted 8 lines
Quoted 3 lines
Responses should be made by Wed 19 Jun 2019 09:06:21 PM UTC. Anything received after that time might be too late.
Build results:
total: 159 pass: 159 fail: 0 Qemu test results: total: 366 pass: 366 fail: 0
Wonderful, thanks for testing and letting me know.
greg k-h
Quoted 14 lines · Greg Kroah-Hartman
This is the start of the stable review cycle for the 5.1.12 release. There are 115 patches in this series, all will be posted as a response to this one. If anyone has any issues with these being applied, please let me know.
Responses should be made by Wed 19 Jun 2019 09:06:21 PM UTC. Anything received after that time might be too late.
The whole patch series can be found in one patch at:
https://www.kernel.org/pub/linux/kernel/v5.x/stable-review/patch-5.1.12-rc1.gzor in the git tree and branch at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.gitlinux-5.1.y
and the diffstat can be found below.
Quoted 5 lines
thanks,
greg k-h
-------------
Compiled and booted. No regressions x86_64.
THX
Quoted 26 lines · Greg Kroah-Hartman
Quoted 24 lines · Naresh Kamboju
Quoted 10 lines · Greg Kroah-Hartman
This is the start of the stable review cycle for the 5.1.12 release. There are 115 patches in this series, all will be posted as a response to this one. If anyone has any issues with these being applied, please let me know.
Responses should be made by Wed 19 Jun 2019 09:06:21 PM UTC. Anything received after that time might be too late.
The whole patch series can be found in one patch at:
Quoted 8 lines
https://www.kernel.org/pub/linux/kernel/v5.x/stable-review/patch-5.1.12-rc1.gzor in the git tree and branch at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.gitlinux-5.1.y
and the diffstat can be found below.thanks,
greg k-h
Results from Linaro’s test farm.
No regressions on arm64, arm,x86_64, and i386.
Quoted 8 lines
Quoted 6 lines
NOTE:
kernel/workqueue.c:3030__flush_work+0x2c2/0x2d0
Kernel warning is been fixed by below patch.Quoted 2 lines
John Fastabend <[email protected]>
bpf: sockmap, only stop/flush strp if it was enabled at some pointWhat is the git commit id for this patch?
Upstream commit 014894360ec95abe868e94416b3dd6569f6e2c0c
- Naresh
Jon Hunter
maintainerQuoted 9 lines · Greg Kroah-Hartman
This is the start of the stable review cycle for the 5.1.12 release. There are 115 patches in this series, all will be posted as a response to this one. If anyone has any issues with these being applied, please let me know.
Responses should be made by Wed 19 Jun 2019 09:06:21 PM UTC. Anything received after that time might be too late.
The whole patch series can be found in one patch at:
Quoted 8 lines
https://www.kernel.org/pub/linux/kernel/v5.x/stable-review/patch-5.1.12-rc1.gzor in the git tree and branch at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.gitlinux-5.1.y
and the diffstat can be found below.thanks,
greg k-h
All tests are passing for Tegra ...
Test results for stable-v5.1:
12 builds: 12 pass, 0 fail
22 boots: 22 pass, 0 fail
32 tests: 32 pass, 0 failLinux version: 5.1.12-rc1-g760bc74bb0d3
Boards tested: tegra124-jetson-tk1, tegra186-p2771-0000,
tegra194-p2972-0000, tegra20-ventana,
tegra210-p2371-2180, tegra30-cardhu-a04Cheers
Jon
Signature · 1 line
nvpublic
Greg Kroah-Hartman
maintainerQuoted 32 lines · Naresh Kamboju
Quoted 30 lines · Greg Kroah-Hartman
Quoted 28 lines · Naresh Kamboju
Quoted 10 lines · Greg Kroah-Hartman
This is the start of the stable review cycle for the 5.1.12 release. There are 115 patches in this series, all will be posted as a response to this one. If anyone has any issues with these being applied, please let me know.
Responses should be made by Wed 19 Jun 2019 09:06:21 PM UTC. Anything received after that time might be too late.
The whole patch series can be found in one patch at:
Quoted 8 lines
https://www.kernel.org/pub/linux/kernel/v5.x/stable-review/patch-5.1.12-rc1.gzor in the git tree and branch at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.gitlinux-5.1.y
and the diffstat can be found below.thanks,
greg k-h
Results from Linaro’s test farm.
No regressions on arm64, arm,x86_64, and i386.NOTE:
kernel/workqueue.c:3030__flush_work+0x2c2/0x2d0
Kernel warning is been fixed by below patch.
Quoted 6 lines
Quoted 4 lines
Quoted 2 lines
Quoted 2 lines
John Fastabend <[email protected]>
bpf: sockmap, only stop/flush strp if it was enabled at some pointWhat is the git commit id for this patch?
Upstream commit 014894360ec95abe868e94416b3dd6569f6e2c0c
Ah, it's been fixed, not that a fix is needed to be backported, sorry for the confusion.
greg k-h
Greg Kroah-Hartman
maintainerQuoted 15 lines · Jiunn Chang
Quoted 14 lines · Greg Kroah-Hartman
This is the start of the stable review cycle for the 5.1.12 release. There are 115 patches in this series, all will be posted as a response to this one. If anyone has any issues with these being applied, please let me know.
Responses should be made by Wed 19 Jun 2019 09:06:21 PM UTC. Anything received after that time might be too late.
The whole patch series can be found in one patch at:
https://www.kernel.org/pub/linux/kernel/v5.x/stable-review/patch-5.1.12-rc1.gzor in the git tree and branch at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.gitlinux-5.1.y
and the diffstat can be found below.
Quoted 7 lines
Quoted 5 lines
thanks,
greg k-h
-------------
Compiled and booted. No regressions
x86_64.
Thanks for testing!
greg k-h
Re: [PATCH 5.1 043/115] ALSA: seq: Protect in-kernel ioctl calls with mutex
In reply to Greg Kroah-HartmanHi!
Quoted 11 lines
[ Upstream commit
feb689025fbb6f0aa6297d3ddf97de945ea4ad32]ALSA OSS sequencer calls the ioctl function indirectly via
snd_seq_kernel_client_ctl(). While we already applied the protection against races between the normal ioctls and writes via the client'sioctl_mutex, this code path was left untouched. And this seems to be the cause of still remaining some rare UAF as spontaneously triggered by syzkaller.For the sake of robustness, wrap the
ioctl_mutexalso for the call viasnd_seq_kernel_client_ctl(), too.
This is reverted with patch after the next one. Should simply this and the revert be deleted from the queue?
Thanks,
Pavel
Quoted 26 lines
sound/core/seq/seq_clientmgr.c +7
-2@@ -2343,14 +2343,19 @@ int snd_seq_kernel_client_ctl(int clientid, unsigned int cmd, void *arg) {const struct ioctl_handler *handler;struct snd_seq_client *client; +int err; client =clientptr (clientid);if (client ==NULL )return -ENXIO ;for (handler = ioctl_handlers; handler->cmd >0 ; ++handler) { -if (handler->cmd == cmd) -return handler->func (client, arg); +if (handler->cmd == cmd) { +mutex_lock (&client->ioctl_mutex); + err = handler->func (client, arg); +mutex_unlock (&client->ioctl_mutex); +return err; + } } pr_debug("ALSA: seq unknown ioctl() 0x%x (type='%c', number=0x%02x)\n",
Signature · 2 lines
(english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html