This reverts commit f5a26acf0162477af6ee4c11b4fb9cffe5d3e257
Mike writes:
It seems that commit f5a26acf0162 ("pinctrl: intel: Initialize GPIO
properly when used through irqchip") can cause problems on some Skylake
systems with Sunrisepoint PCH-H. Namely on certain systems it may turn
the backlight PWM pin from native mode to GPIO which makes the screen
blank during boot.
The actual reason is that GPIO numbering used in BIOS is using "Windows"
numbers meaning that they don't match the hardware 1:1 and because of
this a wrong pin (backlight PWM) is picked and switched to GPIO mode.
There is a proper fix for this but since it has quite many dependencies
on commits that cannot be considered stable material, I suggest we
revert commit f5a26acf0162 from stable trees 4.9, 4.14 and 4.15 to
prevent the backlight issue.
Reported-by: Mika Westerberg <email address hidden>
Fixes: f5a26acf0162 ("pinctrl: intel: Initialize GPIO properly when used through irqchip")
Cc: Daniel Drake <email address hidden>
Cc: Chris Chiu <email address hidden>
Cc: Linus Walleij <email address hidden>
Signed-off-by: Greg Kroah-Hartman <email address hidden>
Signed-off-by: Kamal Mostafa <email address hidden>
Signed-off-by: Khalid Elmously <email address hidden>
This laptop doesn't have a working hardware kill switch and thus the
wifi and bluetooth might become hard blocked without an option to revert
this state at runtime.
Signed-off-by: Johannes Wienke <email address hidden>
Signed-off-by: Joseph Salisbury <email address hidden>
Acked-by: Kleber Souza <email address hidden>
Acked-by: Stefan Bader <email address hidden>
Signed-off-by: Khalid Elmously <email address hidden>
9bf1741...
by
Hans de Goede <email address hidden>
Bluetooth: btusb: Add Dell XPS 13 9360 to btusb_needs_reset_resume_table
When kernel is executing hv_eject_device_work(), hpdev->state value must
be hv_pcichild_ejecting; any other value would consist in a bug,
therefore replace the bogus check with an explicit WARN_ON() on the
condition failure detection.
Signed-off-by: Dexuan Cui <email address hidden>
[<email address hidden>: updated commit log]
Signed-off-by: Lorenzo Pieralisi <email address hidden>
Reviewed-by: Michael Kelley <email address hidden>
Acked-by: Haiyang Zhang <email address hidden>
Cc: Vitaly Kuznetsov <email address hidden>
Cc: Jack Morgenstein <email address hidden>
Cc: Stephen Hemminger <email address hidden>
Cc: K. Y. Srinivasan <email address hidden>
(cherry picked from commit fca288c0153b2b97114b9081bc3c33c3735145b6)
Signed-off-by: Marcelo Henrique Cerri <email address hidden>
Acked-by: Stefan Bader <email address hidden>
Acked-by: Colin Ian King <email address hidden>
Signed-off-by: Khalid Elmously <email address hidden>
If there is pending work in hv_pci_devices_present() we just need to add
the new dr entry into the dr_list. Add a check to detect pending work
items and update the code to skip queuing work if pending work items
are detected.
Signed-off-by: Dexuan Cui <email address hidden>
[<email address hidden>: updated commit log]
Signed-off-by: Lorenzo Pieralisi <email address hidden>
Reviewed-by: Michael Kelley <email address hidden>
Acked-by: Haiyang Zhang <email address hidden>
Cc: Vitaly Kuznetsov <email address hidden>
Cc: Jack Morgenstein <email address hidden>
Cc: Stephen Hemminger <email address hidden>
Cc: K. Y. Srinivasan <email address hidden>
(cherry picked from commit 948373b3ed1bcf05a237c24675b84804315aff14)
Signed-off-by: Marcelo Henrique Cerri <email address hidden>
Acked-by: Stefan Bader <email address hidden>
Acked-by: Colin Ian King <email address hidden>
Signed-off-by: Khalid Elmously <email address hidden>
WHen registering a new binfmt_misc handler, it is possible to overflow
the offset to get a negative value, which might crash the system, or
possibly leak kernel data.
Here is a crash log when 2500000000 was used as an offset:
Use kstrtoint instead of simple_strtoul. It will work as the code
already set the delimiter byte to '\0' and we only do it when the field
is not empty.
Tested with offsets -1, 2500000000, UINT_MAX and INT_MAX. Also tested
with examples documented at Documentation/admin-guide/binfmt-misc.rst
and other registrations from packages on Ubuntu.
Link: http://<email address hidden>
Fixes: 1da177e4c3f4 ("Linux-2.6.12-rc2")
Signed-off-by: Thadeu Lima de Souza Cascardo <email address hidden>
Reviewed-by: Andrew Morton <email address hidden>
Cc: Alexander Viro <email address hidden>
Cc: <email address hidden>
Signed-off-by: Andrew Morton <email address hidden>
Signed-off-by: Linus Torvalds <email address hidden>
(cherry picked from commit 5cc41e099504b77014358b58567c5ea6293dd220)
Signed-off-by: Thadeu Lima de Souza Cascardo <email address hidden>
Acked-by: Marcelo Henrique Cerri <email address hidden>
Acked-by: Stefan Bader <email address hidden>
Signed-off-by: Khalid Elmously <email address hidden>
compat: fix 4-byte infoleak via uninitialized struct field
Commit 3a4d44b61625 ("ntp: Move adjtimex related compat syscalls to
native counterparts") removed the memset() in compat_get_timex(). Since
then, the compat adjtimex syscall can invoke do_adjtimex() with an
uninitialized ->tai.
If do_adjtimex() doesn't write to ->tai (e.g. because the arguments are
invalid), compat_put_timex() then copies the uninitialized ->tai field
to userspace.
