[PATCH 4.17 44/45] crypto: vmx - Remove overly verbose printk from AES XTS init

4.17-stable review patch. If anyone has any objections, please let me know. -- From: Michael Ellerman commit 730f23b66095a700e2f0786abda6bca011b31558 upstream. In p8_aes_xts_init() we do a printk(KERN_INFO ...) to report the fallback implementation we're using. However with a

[PATCH 4.17 44/45] crypto: vmx - Remove overly verbose printk from AES XTS init

4.17-stable review patch. If anyone has any objections, please let me know. -- From: Michael Ellerman commit 730f23b66095a700e2f0786abda6bca011b31558 upstream. In p8_aes_xts_init() we do a printk(KERN_INFO ...) to report the fallback implementation we're using. However with a

[PATCH 4.17 22/45] usb: gadget: udc: renesas_usb3: should call devm_phy_get() before add udc

4.17-stable review patch. If anyone has any objections, please let me know. -- From: Yoshihiro Shimoda commit 003bc1dee216b1fb8e02040a95672bea0f1fe797 upstream. This patch fixes an issue that this driver cannot call phy_init() if a gadget driver is alreadly loaded because

[PATCH 4.17 22/45] usb: gadget: udc: renesas_usb3: should call devm_phy_get() before add udc

4.17-stable review patch. If anyone has any objections, please let me know. -- From: Yoshihiro Shimoda commit 003bc1dee216b1fb8e02040a95672bea0f1fe797 upstream. This patch fixes an issue that this driver cannot call phy_init() if a gadget driver is alreadly loaded because

[PATCH 4.17 24/45] usb: gadget: udc: renesas_usb3: disable the controllers irqs for reconnecting

4.17-stable review patch. If anyone has any objections, please let me know. -- From: Yoshihiro Shimoda commit bd6bce004d78b867ba0c6d3712f1c5b50398af9a upstream. This patch fixes an issue that reconnection is possible to fail because unexpected state handling happens by the

Re: Requirement to get BAR pci_bus_address in user space

On Thu, 14 Jun 2018 16:18:15 +0530 Srinath Mannam wrote: > Hi Sinan Kaya, > > Here are the details, > > The issue is, For CMB cards SQs are allocated inside device BAR memory > which is different from normal cards. > In Normal cards SQ memory allocated at host side. > In both the cases

[PATCH 4.17 24/45] usb: gadget: udc: renesas_usb3: disable the controllers irqs for reconnecting

4.17-stable review patch. If anyone has any objections, please let me know. -- From: Yoshihiro Shimoda commit bd6bce004d78b867ba0c6d3712f1c5b50398af9a upstream. This patch fixes an issue that reconnection is possible to fail because unexpected state handling happens by the

Re: Requirement to get BAR pci_bus_address in user space

On Thu, 14 Jun 2018 16:18:15 +0530 Srinath Mannam wrote: > Hi Sinan Kaya, > > Here are the details, > > The issue is, For CMB cards SQs are allocated inside device BAR memory > which is different from normal cards. > In Normal cards SQ memory allocated at host side. > In both the cases

[PATCH 4.17 26/45] tty/serial: atmel: use port->name as name in request_irq()

4.17-stable review patch. If anyone has any objections, please let me know. -- From: Sebastian Andrzej Siewior commit 9594b5be7ec110ed11acec58fa94f3f293668c85 upstream. I was puzzled while looking at /proc/interrupts and random things showed up between reboots. This occurred

[PATCH 4.17 26/45] tty/serial: atmel: use port->name as name in request_irq()

4.17-stable review patch. If anyone has any objections, please let me know. -- From: Sebastian Andrzej Siewior commit 9594b5be7ec110ed11acec58fa94f3f293668c85 upstream. I was puzzled while looking at /proc/interrupts and random things showed up between reboots. This occurred

[PATCH 4.17 28/45] serial: 8250: omap: Fix idling of clocks for unused uarts

4.17-stable review patch. If anyone has any objections, please let me know. -- From: Tony Lindgren commit 13dc04d0e5fdc25c8f713ad23fdce51cf2bf96ba upstream. I noticed that unused UARTs won't necessarily idle properly always unless at least one byte tx transfer is done first.

[PATCH 4.17 28/45] serial: 8250: omap: Fix idling of clocks for unused uarts

4.17-stable review patch. If anyone has any objections, please let me know. -- From: Tony Lindgren commit 13dc04d0e5fdc25c8f713ad23fdce51cf2bf96ba upstream. I noticed that unused UARTs won't necessarily idle properly always unless at least one byte tx transfer is done first.

[PATCH 4.17 27/45] serial: samsung: fix maxburst parameter for DMA transactions

4.17-stable review patch. If anyone has any objections, please let me know. -- From: Marek Szyprowski commit aa2f80e752c75e593b3820f42c416ed9458fa73e upstream. The best granularity of residue that DMA engine can report is in the BURST units, so the serial driver must use

[PATCH 4.17 27/45] serial: samsung: fix maxburst parameter for DMA transactions

4.17-stable review patch. If anyone has any objections, please let me know. -- From: Marek Szyprowski commit aa2f80e752c75e593b3820f42c416ed9458fa73e upstream. The best granularity of residue that DMA engine can report is in the BURST units, so the serial driver must use

[PATCH 4.17 19/45] usb: gadget: udc: renesas_usb3: fix double phy_put()

4.17-stable review patch. If anyone has any objections, please let me know. -- From: Yoshihiro Shimoda commit 8223b2f89ca63e203dcb54148e30d94979f17b0b upstream. This patch fixes an issue that this driver cause double phy_put() calling. This driver must not call phy_put() in

[PATCH 4.17 19/45] usb: gadget: udc: renesas_usb3: fix double phy_put()

4.17-stable review patch. If anyone has any objections, please let me know. -- From: Yoshihiro Shimoda commit 8223b2f89ca63e203dcb54148e30d94979f17b0b upstream. This patch fixes an issue that this driver cause double phy_put() calling. This driver must not call phy_put() in

[PATCH 4.16 10/43] NFC: pn533: dont send USB data off of the stack

4.16-stable review patch. If anyone has any objections, please let me know. -- From: Greg Kroah-Hartman commit dbafc28955fa6779dc23d1607a0fee5e509a278b upstream. It's amazing that this driver ever worked, but now that x86 doesn't allow USB data to be sent off of the stack, it

[PATCH 4.16 10/43] NFC: pn533: dont send USB data off of the stack

4.16-stable review patch. If anyone has any objections, please let me know. -- From: Greg Kroah-Hartman commit dbafc28955fa6779dc23d1607a0fee5e509a278b upstream. It's amazing that this driver ever worked, but now that x86 doesn't allow USB data to be sent off of the stack, it

[PATCH 4.16 01/43] netfilter: nf_tables: fix NULL pointer dereference on nft_ct_helper_obj_dump()

4.16-stable review patch. If anyone has any objections, please let me know. -- From: Taehee Yoo commit b71534583f22d08c3e3563bf5100aeb5f5c9fbe5 upstream. In the nft_ct_helper_obj_dump(), always priv->helper4 is dereferenced. But if family is ipv6, priv->helper6 should be

[PATCH 4.16 01/43] netfilter: nf_tables: fix NULL pointer dereference on nft_ct_helper_obj_dump()

4.16-stable review patch. If anyone has any objections, please let me know. -- From: Taehee Yoo commit b71534583f22d08c3e3563bf5100aeb5f5c9fbe5 upstream. In the nft_ct_helper_obj_dump(), always priv->helper4 is dereferenced. But if family is ipv6, priv->helper6 should be

[PATCH 4.16 11/43] usbip: vhci_sysfs: fix potential Spectre v1

4.16-stable review patch. If anyone has any objections, please let me know. -- From: Gustavo A. R. Silva commit a0d6ec88090d7b1b008429c44532a388e29bb1bd upstream. pdev_nr and rhport can be controlled by user-space, hence leading to a potential exploitation of the Spectre

[PATCH 4.16 11/43] usbip: vhci_sysfs: fix potential Spectre v1

4.16-stable review patch. If anyone has any objections, please let me know. -- From: Gustavo A. R. Silva commit a0d6ec88090d7b1b008429c44532a388e29bb1bd upstream. pdev_nr and rhport can be controlled by user-space, hence leading to a potential exploitation of the Spectre

[PATCH 4.16 12/43] usb-storage: Add support for FL_ALWAYS_SYNC flag in the UAS driver

4.16-stable review patch. If anyone has any objections, please let me know. -- From: Alexander Kappner commit 8c4e97ddfe73a0958bb0abf7e6a3bc4cc3e04936 upstream. The ALWAYS_SYNC flag is currently honored by the usb-storage driver but not UAS and is required to work around

[PATCH 4.16 12/43] usb-storage: Add support for FL_ALWAYS_SYNC flag in the UAS driver

4.16-stable review patch. If anyone has any objections, please let me know. -- From: Alexander Kappner commit 8c4e97ddfe73a0958bb0abf7e6a3bc4cc3e04936 upstream. The ALWAYS_SYNC flag is currently honored by the usb-storage driver but not UAS and is required to work around

[PATCH 4.16 13/43] usb-storage: Add compatibility quirk flags for G-Technologies G-Drive

4.16-stable review patch. If anyone has any objections, please let me know. -- From: Alexander Kappner commit ca7d9515d0e6825351ce106066cea1f60e40b1c8 upstream. The "G-Drive" (sold by G-Technology) external USB 3.0 drive hangs on write access under UAS and usb-storage: [

[PATCH 4.16 13/43] usb-storage: Add compatibility quirk flags for G-Technologies G-Drive

4.16-stable review patch. If anyone has any objections, please let me know. -- From: Alexander Kappner commit ca7d9515d0e6825351ce106066cea1f60e40b1c8 upstream. The "G-Drive" (sold by G-Technology) external USB 3.0 drive hangs on write access under UAS and usb-storage: [

bitmap namespace conflict

Hi! There is a potential name space collision with bitmap API vs. MD bitmaps (whatever it is). Since I'm about to submit some extension to bitmap API, I would like as a preparatory patch to rename all bitmap_* in drivers/md to md_bitmap_* to avoid real conflict with my patch series [1], i.e.

bitmap namespace conflict

Hi! There is a potential name space collision with bitmap API vs. MD bitmaps (whatever it is). Since I'm about to submit some extension to bitmap API, I would like as a preparatory patch to rename all bitmap_* in drivers/md to md_bitmap_* to avoid real conflict with my patch series [1], i.e.

[PATCH 4.16 17/43] usb: typec: wcove: Remove dependency on HW FSM

4.16-stable review patch. If anyone has any objections, please let me know. -- From: Heikki Krogerus commit 05826ff135ee083d28c006fbde6e810f17437166 upstream. The USB Type-C PHY in Intel WhiskeyCove PMIC has build-in USB Type-C state machine which we were relying on to

[PATCH 4.16 15/43] phy: qcom-qusb2: Fix crash if nvmem cell not specified

4.16-stable review patch. If anyone has any objections, please let me know. -- From: Manu Gautam commit 0b4555e776ba0712c6fafb98b226b21fd05d2427 upstream. Driver currently crashes due to NULL pointer deference while updating PHY tune register if nvmem cell is NULL. Since,

[PATCH 4.16 17/43] usb: typec: wcove: Remove dependency on HW FSM

4.16-stable review patch. If anyone has any objections, please let me know. -- From: Heikki Krogerus commit 05826ff135ee083d28c006fbde6e810f17437166 upstream. The USB Type-C PHY in Intel WhiskeyCove PMIC has build-in USB Type-C state machine which we were relying on to

[PATCH 4.16 15/43] phy: qcom-qusb2: Fix crash if nvmem cell not specified

4.16-stable review patch. If anyone has any objections, please let me know. -- From: Manu Gautam commit 0b4555e776ba0712c6fafb98b226b21fd05d2427 upstream. Driver currently crashes due to NULL pointer deference while updating PHY tune register if nvmem cell is NULL. Since,

[PATCH 4.16 18/43] usb: gadget: function: printer: avoid wrong list handling in printer_write()

4.16-stable review patch. If anyone has any objections, please let me know. -- From: Yoshihiro Shimoda commit 4a014a7339f441b0851ce012f469c0fadac61c81 upstream. When printer_write() calls usb_ep_queue(), a udc driver (e.g. renesas_usbhs driver) may call

[PATCH 4.16 18/43] usb: gadget: function: printer: avoid wrong list handling in printer_write()

4.16-stable review patch. If anyone has any objections, please let me know. -- From: Yoshihiro Shimoda commit 4a014a7339f441b0851ce012f469c0fadac61c81 upstream. When printer_write() calls usb_ep_queue(), a udc driver (e.g. renesas_usbhs driver) may call

[PATCH 4.16 20/43] usb: gadget: udc: renesas_usb3: should remove debugfs

4.16-stable review patch. If anyone has any objections, please let me know. -- From: Yoshihiro Shimoda commit 1990cf7c21ea185cec98c6d45a82c04481261e35 upstream. This patch fixes an issue that this driver doesn't remove its debugfs. Fixes: 43ba968b00ea ("usb: gadget: udc:

[PATCH 4.16 20/43] usb: gadget: udc: renesas_usb3: should remove debugfs

4.16-stable review patch. If anyone has any objections, please let me know. -- From: Yoshihiro Shimoda commit 1990cf7c21ea185cec98c6d45a82c04481261e35 upstream. This patch fixes an issue that this driver doesn't remove its debugfs. Fixes: 43ba968b00ea ("usb: gadget: udc:

[PATCH 4.16 21/43] usb: gadget: udc: renesas_usb3: should call pm_runtime_enable() before add udc

4.16-stable review patch. If anyone has any objections, please let me know. -- From: Yoshihiro Shimoda commit d998844016b24a8d71b9aa5eae7e51d70f2de438 upstream. This patch fixes an issue that this driver causes panic if a gadget driver is already loaded because

[PATCH 4.16 21/43] usb: gadget: udc: renesas_usb3: should call pm_runtime_enable() before add udc

4.16-stable review patch. If anyone has any objections, please let me know. -- From: Yoshihiro Shimoda commit d998844016b24a8d71b9aa5eae7e51d70f2de438 upstream. This patch fixes an issue that this driver causes panic if a gadget driver is already loaded because

Re: [alsa-devel] [PATCH] ASoC: codecs: PCM1789: include gpio/consumer.h

On Wed, May 30, 2018 at 11:53 PM, Arnd Bergmann wrote: > When CONFIG_GPIOLIB is disabled, this codec fails to build > because gpio/consumer.h is not included implicitly. > > sound/soc/codecs/pcm1789.c: In function 'pcm1789_common_init': > sound/soc/codecs/pcm1789.c:247:19: error: implicit

[PATCH 4.16 25/43] serial: sh-sci: Stop using printk format %pCr

4.16-stable review patch. If anyone has any objections, please let me know. -- From: Geert Uytterhoeven commit d63c16f8e1ab761775275adcf54f4bef7c330295 upstream. Printk format "%pCr" will be removed soon, as clk_get_rate() must not be called in atomic context. Replace it by

Re: [alsa-devel] [PATCH] ASoC: codecs: PCM1789: include gpio/consumer.h

On Wed, May 30, 2018 at 11:53 PM, Arnd Bergmann wrote: > When CONFIG_GPIOLIB is disabled, this codec fails to build > because gpio/consumer.h is not included implicitly. > > sound/soc/codecs/pcm1789.c: In function 'pcm1789_common_init': > sound/soc/codecs/pcm1789.c:247:19: error: implicit

[PATCH 4.16 25/43] serial: sh-sci: Stop using printk format %pCr

4.16-stable review patch. If anyone has any objections, please let me know. -- From: Geert Uytterhoeven commit d63c16f8e1ab761775275adcf54f4bef7c330295 upstream. Printk format "%pCr" will be removed soon, as clk_get_rate() must not be called in atomic context. Replace it by

[PATCH 4.16 24/43] usb: gadget: udc: renesas_usb3: disable the controllers irqs for reconnecting

4.16-stable review patch. If anyone has any objections, please let me know. -- From: Yoshihiro Shimoda commit bd6bce004d78b867ba0c6d3712f1c5b50398af9a upstream. This patch fixes an issue that reconnection is possible to fail because unexpected state handling happens by the

[PATCH 4.16 24/43] usb: gadget: udc: renesas_usb3: disable the controllers irqs for reconnecting

4.16-stable review patch. If anyone has any objections, please let me know. -- From: Yoshihiro Shimoda commit bd6bce004d78b867ba0c6d3712f1c5b50398af9a upstream. This patch fixes an issue that reconnection is possible to fail because unexpected state handling happens by the

[PATCH 4.16 26/43] tty/serial: atmel: use port->name as name in request_irq()

4.16-stable review patch. If anyone has any objections, please let me know. -- From: Sebastian Andrzej Siewior commit 9594b5be7ec110ed11acec58fa94f3f293668c85 upstream. I was puzzled while looking at /proc/interrupts and random things showed up between reboots. This occurred

[PATCH 4.16 26/43] tty/serial: atmel: use port->name as name in request_irq()

4.16-stable review patch. If anyone has any objections, please let me know. -- From: Sebastian Andrzej Siewior commit 9594b5be7ec110ed11acec58fa94f3f293668c85 upstream. I was puzzled while looking at /proc/interrupts and random things showed up between reboots. This occurred

[PATCH 4.16 23/43] usb: gadget: udc: renesas_usb3: should fail if devm_phy_get() returns error

4.16-stable review patch. If anyone has any objections, please let me know. -- From: Yoshihiro Shimoda commit 0259068f63f23a665ded28647f2f9cdb6b20dc72 upstream. This patch fixes an issue that this driver ignores errors other than the non-existence of the device, f.e. a memory

[PATCH 4.16 23/43] usb: gadget: udc: renesas_usb3: should fail if devm_phy_get() returns error

4.16-stable review patch. If anyone has any objections, please let me know. -- From: Yoshihiro Shimoda commit 0259068f63f23a665ded28647f2f9cdb6b20dc72 upstream. This patch fixes an issue that this driver ignores errors other than the non-existence of the device, f.e. a memory

[PATCH 4.16 28/43] serial: 8250: omap: Fix idling of clocks for unused uarts

4.16-stable review patch. If anyone has any objections, please let me know. -- From: Tony Lindgren commit 13dc04d0e5fdc25c8f713ad23fdce51cf2bf96ba upstream. I noticed that unused UARTs won't necessarily idle properly always unless at least one byte tx transfer is done first.

[PATCH 4.16 28/43] serial: 8250: omap: Fix idling of clocks for unused uarts

4.16-stable review patch. If anyone has any objections, please let me know. -- From: Tony Lindgren commit 13dc04d0e5fdc25c8f713ad23fdce51cf2bf96ba upstream. I noticed that unused UARTs won't necessarily idle properly always unless at least one byte tx transfer is done first.

[PATCH 4.16 03/43] blkdev_report_zones_ioctl(): Use vmalloc() to allocate large buffers

4.16-stable review patch. If anyone has any objections, please let me know. -- From: Bart Van Assche commit 327ea4adcfa37194739f1ec7c70568944d292281 upstream. Avoid that complaints similar to the following appear in the kernel log if the number of zones is sufficiently large:

[PATCH 4.16 03/43] blkdev_report_zones_ioctl(): Use vmalloc() to allocate large buffers

4.16-stable review patch. If anyone has any objections, please let me know. -- From: Bart Van Assche commit 327ea4adcfa37194739f1ec7c70568944d292281 upstream. Avoid that complaints similar to the following appear in the kernel log if the number of zones is sufficiently large:

Re: [PATCH] selftests: gpio: gpio-mockup-chardev GPIOHANDLE_REQUEST_OUTPUT fix

On Wed, Jun 6, 2018 at 7:44 PM, Rafael David Tinoco wrote: > Following logic from commit: 22f6592b23, GPIOHANDLE_REQUEST_OUTPUT > should handle errors same way as GPIOHANDLE_REQUEST_INPUT does, or else > the following error occurs: > > gpio-mockup-chardev: gpio line<0> test flag<0x2> value<0>:

Re: [PATCH] selftests: gpio: gpio-mockup-chardev GPIOHANDLE_REQUEST_OUTPUT fix

On Wed, Jun 6, 2018 at 7:44 PM, Rafael David Tinoco wrote: > Following logic from commit: 22f6592b23, GPIOHANDLE_REQUEST_OUTPUT > should handle errors same way as GPIOHANDLE_REQUEST_INPUT does, or else > the following error occurs: > > gpio-mockup-chardev: gpio line<0> test flag<0x2> value<0>:

[PATCH 4.16 07/43] kvm: nVMX: Enforce cpl=0 for VMX instructions

4.16-stable review patch. If anyone has any objections, please let me know. -- From: Felix Wilhelm commit 727ba748e110b4de50d142edca9d6a9b7e6111d8 upstream. VMX instructions executed inside a L1 VM will always trigger a VM exit even when executed with cpl 3. This means we

[PATCH 4.16 07/43] kvm: nVMX: Enforce cpl=0 for VMX instructions

4.16-stable review patch. If anyone has any objections, please let me know. -- From: Felix Wilhelm commit 727ba748e110b4de50d142edca9d6a9b7e6111d8 upstream. VMX instructions executed inside a L1 VM will always trigger a VM exit even when executed with cpl 3. This means we

[PATCH 4.16 09/43] staging: android: ion: Switch to pr_warn_once in ion_buffer_destroy

4.16-stable review patch. If anyone has any objections, please let me know. -- From: Laura Abbott commit 45ad559a29629cb1c64ee636563c69b71524f077 upstream. Syzbot reported yet another warning with Ion: WARNING: CPU: 0 PID: 1467 at drivers/staging/android/ion/ion.c:122

[PATCH 4.16 09/43] staging: android: ion: Switch to pr_warn_once in ion_buffer_destroy

4.16-stable review patch. If anyone has any objections, please let me know. -- From: Laura Abbott commit 45ad559a29629cb1c64ee636563c69b71524f077 upstream. Syzbot reported yet another warning with Ion: WARNING: CPU: 0 PID: 1467 at drivers/staging/android/ion/ion.c:122

Re: Restartable Sequences system call merged into Linux

On 06/14/2018 04:36 PM, Mathieu Desnoyers wrote: - On Jun 14, 2018, at 10:00 AM, Florian Weimer fwei...@redhat.com wrote: On 06/14/2018 03:49 PM, Pavel Machek wrote: Hi! - rseq_preempt(): on preemption, the scheduler sets the TIF_NOTIFY_RESUME thread flag, so

Re: Restartable Sequences system call merged into Linux

On 06/14/2018 04:36 PM, Mathieu Desnoyers wrote: - On Jun 14, 2018, at 10:00 AM, Florian Weimer fwei...@redhat.com wrote: On 06/14/2018 03:49 PM, Pavel Machek wrote: Hi! - rseq_preempt(): on preemption, the scheduler sets the TIF_NOTIFY_RESUME thread flag, so

[PATCH 4.16 30/43] tty: pl011: Avoid spuriously stuck-off interrupts

4.16-stable review patch. If anyone has any objections, please let me know. -- From: Dave Martin commit 4a7e625ce50412a7711efa0f2ef0b96ce3826759 upstream. Commit 9b96fbacda34 ("serial: PL011: clear pending interrupts") clears the RX and receive timeout interrupts on pl011

[PATCH 4.16 30/43] tty: pl011: Avoid spuriously stuck-off interrupts

4.16-stable review patch. If anyone has any objections, please let me know. -- From: Dave Martin commit 4a7e625ce50412a7711efa0f2ef0b96ce3826759 upstream. Commit 9b96fbacda34 ("serial: PL011: clear pending interrupts") clears the RX and receive timeout interrupts on pl011

[PATCH 4.16 42/43] crypto: vmx - Remove overly verbose printk from AES XTS init

4.16-stable review patch. If anyone has any objections, please let me know. -- From: Michael Ellerman commit 730f23b66095a700e2f0786abda6bca011b31558 upstream. In p8_aes_xts_init() we do a printk(KERN_INFO ...) to report the fallback implementation we're using. However with a

[PATCH 4.16 42/43] crypto: vmx - Remove overly verbose printk from AES XTS init

4.16-stable review patch. If anyone has any objections, please let me know. -- From: Michael Ellerman commit 730f23b66095a700e2f0786abda6bca011b31558 upstream. In p8_aes_xts_init() we do a printk(KERN_INFO ...) to report the fallback implementation we're using. However with a

[PATCH 4.16 00/43] 4.16.16-stable review

This is the start of the stable review cycle for the 4.16.16 release. There are 43 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 Sat Jun 16 13:21:17 UTC 2018. Anything

[PATCH 4.16 00/43] 4.16.16-stable review

This is the start of the stable review cycle for the 4.16.16 release. There are 43 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 Sat Jun 16 13:21:17 UTC 2018. Anything

Re: Requirement to get BAR pci_bus_address in user space

On Thu, Jun 14, 2018 at 04:18:15PM +0530, Srinath Mannam wrote: > The issue is, For CMB cards SQs are allocated inside device BAR memory > which is different from normal cards. > In Normal cards SQ memory allocated at host side. > In both the cases physical address of CQ memory is programmed in

Re: Requirement to get BAR pci_bus_address in user space

On Thu, Jun 14, 2018 at 04:18:15PM +0530, Srinath Mannam wrote: > The issue is, For CMB cards SQs are allocated inside device BAR memory > which is different from normal cards. > In Normal cards SQ memory allocated at host side. > In both the cases physical address of CQ memory is programmed in

[PATCH 4.16 43/43] crypto: omap-sham - fix memleak

4.16-stable review patch. If anyone has any objections, please let me know. -- From: Bin Liu commit 9dbc8a0328efa485a6f5b68b867f9f523a3fbeff upstream. Fixes: 8043bb1ae03cb ("crypto: omap-sham - convert driver logic to use sgs for data xmit") The memory pages freed in

[PATCH 4.16 43/43] crypto: omap-sham - fix memleak

4.16-stable review patch. If anyone has any objections, please let me know. -- From: Bin Liu commit 9dbc8a0328efa485a6f5b68b867f9f523a3fbeff upstream. Fixes: 8043bb1ae03cb ("crypto: omap-sham - convert driver logic to use sgs for data xmit") The memory pages freed in

[PATCH 4.16 41/43] crypto: vmx - Remove overly verbose printk from AES init routines

4.16-stable review patch. If anyone has any objections, please let me know. -- From: Michael Ellerman commit 1411b5218adbcf1d45ddb260db5553c52e8d917c upstream. In the vmx AES init routines we do a printk(KERN_INFO ...) to report the fallback implementation we're using.

[PATCH 4.16 41/43] crypto: vmx - Remove overly verbose printk from AES init routines

4.16-stable review patch. If anyone has any objections, please let me know. -- From: Michael Ellerman commit 1411b5218adbcf1d45ddb260db5553c52e8d917c upstream. In the vmx AES init routines we do a printk(KERN_INFO ...) to report the fallback implementation we're using.

[PATCH 4.14 01/36] netfilter: nf_tables: fix NULL pointer dereference on nft_ct_helper_obj_dump()

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Taehee Yoo commit b71534583f22d08c3e3563bf5100aeb5f5c9fbe5 upstream. In the nft_ct_helper_obj_dump(), always priv->helper4 is dereferenced. But if family is ipv6, priv->helper6 should be

[PATCH 4.16 40/43] crypto: cavium - Limit result reading attempts

4.16-stable review patch. If anyone has any objections, please let me know. -- From: Jan Glauber commit c782a8c43e94ba6c09e9de2d69b5e3a5840ce61c upstream. After issuing a request an endless loop was used to read the completion state from memory which is asynchronously updated

[PATCH 4.14 01/36] netfilter: nf_tables: fix NULL pointer dereference on nft_ct_helper_obj_dump()

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Taehee Yoo commit b71534583f22d08c3e3563bf5100aeb5f5c9fbe5 upstream. In the nft_ct_helper_obj_dump(), always priv->helper4 is dereferenced. But if family is ipv6, priv->helper6 should be

[PATCH 4.16 40/43] crypto: cavium - Limit result reading attempts

4.16-stable review patch. If anyone has any objections, please let me know. -- From: Jan Glauber commit c782a8c43e94ba6c09e9de2d69b5e3a5840ce61c upstream. After issuing a request an endless loop was used to read the completion state from memory which is asynchronously updated

[PATCH 4.16 31/43] kvm: x86: use correct privilege level for sgdt/sidt/fxsave/fxrstor access

4.16-stable review patch. If anyone has any objections, please let me know. -- From: Paolo Bonzini commit 3c9fa24ca7c9c47605672916491f79e8ccacb9e6 upstream. The functions that were used in the emulation of fxrstor, fxsave, sgdt and sidt were originally meant for task

[PATCH 4.16 31/43] kvm: x86: use correct privilege level for sgdt/sidt/fxsave/fxrstor access

4.16-stable review patch. If anyone has any objections, please let me know. -- From: Paolo Bonzini commit 3c9fa24ca7c9c47605672916491f79e8ccacb9e6 upstream. The functions that were used in the emulation of fxrstor, fxsave, sgdt and sidt were originally meant for task

[PATCH 4.14 03/36] af_key: Always verify length of provided sadb_key

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Kevin Easton commit 4b66af2d6356a00e94bcdea3e7fea324e8b5c6f4 upstream. Key extensions (struct sadb_key) include a user-specified number of key bits. The kernel uses that number to determine

[PATCH 4.14 03/36] af_key: Always verify length of provided sadb_key

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Kevin Easton commit 4b66af2d6356a00e94bcdea3e7fea324e8b5c6f4 upstream. Key extensions (struct sadb_key) include a user-specified number of key bits. The kernel uses that number to determine

Re: Restartable Sequences system call merged into Linux

- On Jun 14, 2018, at 10:00 AM, Florian Weimer fwei...@redhat.com wrote: > On 06/14/2018 03:49 PM, Pavel Machek wrote: >> Hi! >> > - rseq_preempt(): on preemption, the scheduler sets the TIF_NOTIFY_RESUME > thread >flag, so rseq_handle_notify_resume() can check whether it's

Re: Restartable Sequences system call merged into Linux

- On Jun 14, 2018, at 10:00 AM, Florian Weimer fwei...@redhat.com wrote: > On 06/14/2018 03:49 PM, Pavel Machek wrote: >> Hi! >> > - rseq_preempt(): on preemption, the scheduler sets the TIF_NOTIFY_RESUME > thread >flag, so rseq_handle_notify_resume() can check whether it's

[PATCH 4.14 16/36] usb: gadget: function: printer: avoid wrong list handling in printer_write()

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Yoshihiro Shimoda commit 4a014a7339f441b0851ce012f469c0fadac61c81 upstream. When printer_write() calls usb_ep_queue(), a udc driver (e.g. renesas_usbhs driver) may call

[PATCH 4.14 16/36] usb: gadget: function: printer: avoid wrong list handling in printer_write()

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Yoshihiro Shimoda commit 4a014a7339f441b0851ce012f469c0fadac61c81 upstream. When printer_write() calls usb_ep_queue(), a udc driver (e.g. renesas_usbhs driver) may call

[PATCH 4.14 15/36] phy: qcom-qusb2: Fix crash if nvmem cell not specified

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Manu Gautam commit 0b4555e776ba0712c6fafb98b226b21fd05d2427 upstream. Driver currently crashes due to NULL pointer deference while updating PHY tune register if nvmem cell is NULL. Since,

[PATCH 4.14 15/36] phy: qcom-qusb2: Fix crash if nvmem cell not specified

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Manu Gautam commit 0b4555e776ba0712c6fafb98b226b21fd05d2427 upstream. Driver currently crashes due to NULL pointer deference while updating PHY tune register if nvmem cell is NULL. Since,

[PATCH 4.14 19/36] tty/serial: atmel: use port->name as name in request_irq()

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Sebastian Andrzej Siewior commit 9594b5be7ec110ed11acec58fa94f3f293668c85 upstream. I was puzzled while looking at /proc/interrupts and random things showed up between reboots. This occurred

[PATCH 4.14 19/36] tty/serial: atmel: use port->name as name in request_irq()

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Sebastian Andrzej Siewior commit 9594b5be7ec110ed11acec58fa94f3f293668c85 upstream. I was puzzled while looking at /proc/interrupts and random things showed up between reboots. This occurred

[PATCH 4.14 20/36] serial: samsung: fix maxburst parameter for DMA transactions

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Marek Szyprowski commit aa2f80e752c75e593b3820f42c416ed9458fa73e upstream. The best granularity of residue that DMA engine can report is in the BURST units, so the serial driver must use

[PATCH 4.14 20/36] serial: samsung: fix maxburst parameter for DMA transactions

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Marek Szyprowski commit aa2f80e752c75e593b3820f42c416ed9458fa73e upstream. The best granularity of residue that DMA engine can report is in the BURST units, so the serial driver must use

[PATCH 4.14 21/36] serial: 8250: omap: Fix idling of clocks for unused uarts

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Tony Lindgren commit 13dc04d0e5fdc25c8f713ad23fdce51cf2bf96ba upstream. I noticed that unused UARTs won't necessarily idle properly always unless at least one byte tx transfer is done first.

[PATCH 4.14 21/36] serial: 8250: omap: Fix idling of clocks for unused uarts

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Tony Lindgren commit 13dc04d0e5fdc25c8f713ad23fdce51cf2bf96ba upstream. I noticed that unused UARTs won't necessarily idle properly always unless at least one byte tx transfer is done first.

[PATCH 4.14 23/36] tty: pl011: Avoid spuriously stuck-off interrupts

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Dave Martin commit 4a7e625ce50412a7711efa0f2ef0b96ce3826759 upstream. Commit 9b96fbacda34 ("serial: PL011: clear pending interrupts") clears the RX and receive timeout interrupts on pl011

[PATCH 4.14 23/36] tty: pl011: Avoid spuriously stuck-off interrupts

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Dave Martin commit 4a7e625ce50412a7711efa0f2ef0b96ce3826759 upstream. Commit 9b96fbacda34 ("serial: PL011: clear pending interrupts") clears the RX and receive timeout interrupts on pl011

[PATCH 4.14 24/36] kvm: x86: use correct privilege level for sgdt/sidt/fxsave/fxrstor access

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Paolo Bonzini commit 3c9fa24ca7c9c47605672916491f79e8ccacb9e6 upstream. The functions that were used in the emulation of fxrstor, fxsave, sgdt and sidt were originally meant for task

[PATCH 4.14 24/36] kvm: x86: use correct privilege level for sgdt/sidt/fxsave/fxrstor access

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Paolo Bonzini commit 3c9fa24ca7c9c47605672916491f79e8ccacb9e6 upstream. The functions that were used in the emulation of fxrstor, fxsave, sgdt and sidt were originally meant for task

[PATCH 4.14 26/36] Input: elan_i2c - add ELAN0612 (Lenovo v330 14IKB) ACPI ID

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Johannes Wienke commit e6e7e9cd8eed0e18217c899843bffbe8c7dae564 upstream. Add ELAN0612 to the list of supported touchpads; this ID is used in Lenovo v330 14IKB devices. Bugzilla:

[PATCH 4.14 26/36] Input: elan_i2c - add ELAN0612 (Lenovo v330 14IKB) ACPI ID

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Johannes Wienke commit e6e7e9cd8eed0e18217c899843bffbe8c7dae564 upstream. Add ELAN0612 to the list of supported touchpads; this ID is used in Lenovo v330 14IKB devices. Bugzilla:

[PATCH 4.14 07/36] kvm: nVMX: Enforce cpl=0 for VMX instructions

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Felix Wilhelm commit 727ba748e110b4de50d142edca9d6a9b7e6111d8 upstream. VMX instructions executed inside a L1 VM will always trigger a VM exit even when executed with cpl 3. This means we

[PATCH 4.14 07/36] kvm: nVMX: Enforce cpl=0 for VMX instructions

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Felix Wilhelm commit 727ba748e110b4de50d142edca9d6a9b7e6111d8 upstream. VMX instructions executed inside a L1 VM will always trigger a VM exit even when executed with cpl 3. This means we

<    1   2   3   4   5   6   7   8   9   10   >