Re: [PATCH v2] page_poison: play nicely with KASAN

On 1/15/19 2:34 AM, Qian Cai wrote: > KASAN does not play well with the page poisoning > (CONFIG_PAGE_POISONING). It triggers false positives in the allocation > path, > > BUG: KASAN: use-after-free in memchr_inv+0x2ea/0x330 > Read of size 8 at addr 1f80 by task swapper/0 > CPU: 0

Re: [PATCH v3 3/3] powerpc/32: Add KASAN support

On 1/12/19 2:16 PM, Christophe Leroy wrote: > +KASAN_SANITIZE_early_32.o := n > +KASAN_SANITIZE_cputable.o := n > +KASAN_SANITIZE_prom_init.o := n > + Usually it's also good idea to disable branch profiling - define DISABLE_BRANCH_PROFILING either in top of these files or via Makefile.

Re: [PATCH] mm: Make CONFIG_FRAME_VECTOR a visible option

On Tue, Jan 15, 2019 at 09:17:30AM -0800, Olof Johansson wrote: > I'd argue it's *more* confusing to expect users to know about and > enable some random V4L driver to get this exported kernel API included > or not. Happy to add "If in doubt, say 'n' here" help text, like we do > for many many

[PATCH] cpuidle: use BIT() for idle state flags and remove CPUIDLE_DRIVER_FLAGS_MASK

Use BIT() macro to do a small tidy-up. The CPUIDLE_DRIVER_FLAGS_MASK is not being used, so remove it. Signed-off-by: Yangtao Li --- include/linux/cpuidle.h | 8 +++- 1 file changed, 3 insertions(+), 5 deletions(-) diff --git a/include/linux/cpuidle.h b/include/linux/cpuidle.h index

kexec: relocate_kernel fails

I am not able to get kexec to work. For x86_64 relocate_kernel fails to store information for jumping back. Kexec stops in movq %r9, CP_PA_TABLE_PAGE(%r11).

Re: [PATCH v3] staging: Mediatek: Use individual config flags in Makefile

On Tue, Jan 15, 2019 at 10:02:21AM -0700, George Hilliard wrote: > These drivers can be useful on other MT76xx SoCs, which have compatible > peripherals. The drivers were selectable in Kconfig, but they were > quietly excluded from the build because the SOC_MT7621 chip was not > selected. So,

[PATCH] tty: serial: lpc32xx_hs: fix missing console boot messages

When probing the HSUART, it is put in loopback mode in order to prevent a potential issue that may happen on RX (Errata HSUART.1). serial_lpc32xx_startup() moves it out of loopback mode but this is too late to get the kernel boot messages before userspace opens the device. Also get out of

Re: [PATCH] mm: Make CONFIG_FRAME_VECTOR a visible option

On Tue, Jan 15, 2019 at 9:05 AM Christoph Hellwig wrote: > > On Tue, Jan 15, 2019 at 08:44:35AM -0800, Olof Johansson wrote: > > CONFIG_FRAME_VECTOR was made an option to avoid including the bloat on > > platforms that try to keep footprint down, which makes sense. > > > > The problem with this

[PATCH] dmaengine: imx-dma: fix wrong callback invoke

Once the "ld_queue" list is not empty, next descriptor will migrate into "ld_active" list. The "desc" variable will be overwritten during that transition. And later the dmaengine_desc_get_callback_invoke() will use it as an argument. As result we invoke wrong callback. That behaviour was in place

Re: [PATCH 1/2] mm: introduce put_user_page*(), placeholder versions

On Tue, Jan 15, 2019 at 09:07:59AM +0100, Jan Kara wrote: > On Mon 14-01-19 12:21:25, Jerome Glisse wrote: > > On Mon, Jan 14, 2019 at 03:54:47PM +0100, Jan Kara wrote: > > > On Fri 11-01-19 19:06:08, John Hubbard wrote: > > > > On 1/11/19 6:46 PM, Jerome Glisse wrote: > > > > > On Fri, Jan 11,

Re: [PATCH] MAINTAINERS: add myself as SPI NOR co-maintainer

Hi Tudor, On Tue, 15 Jan 2019 16:57:52 + wrote: > From: Tudor Ambarus > > I have been reviewing and contributing to the SPI NOR subsystem > for the last few months and I'm willing to continue doing so. > Volunteer as a maintainer for the SPI NOR part of the MTD subsystem. I'll wait a bit

Re: [PATCH v3 1/3] powerpc/mm: prepare kernel for KAsan on PPC32

On Tue, Jan 15, 2019 at 6:06 PM Andrey Ryabinin wrote: > > > > On 1/15/19 2:14 PM, Dmitry Vyukov wrote: > > On Tue, Jan 15, 2019 at 8:27 AM Christophe Leroy > > wrote: > >> On 01/14/2019 09:34 AM, Dmitry Vyukov wrote: > >>> On Sat, Jan 12, 2019 at 12:16 PM Christophe Leroy > >>> wrote: > >>> >

Re: [PATCHv3 03/13] acpi/hmat: Parse and report heterogeneous memory

On Thu, Jan 10, 2019 at 07:42:46AM -0800, Rafael J. Wysocki wrote: > On Wed, Jan 9, 2019 at 6:47 PM Keith Busch wrote: > > > > Systems may provide different memory types and export this information > > in the ACPI Heterogeneous Memory Attribute Table (HMAT). Parse these > > tables provided by the

Re: [PATCH v3 1/3] powerpc/mm: prepare kernel for KAsan on PPC32

On 1/15/19 2:14 PM, Dmitry Vyukov wrote: > On Tue, Jan 15, 2019 at 8:27 AM Christophe Leroy > wrote: >> On 01/14/2019 09:34 AM, Dmitry Vyukov wrote: >>> On Sat, Jan 12, 2019 at 12:16 PM Christophe Leroy >>> wrote: >>> >>> In kernel/cputable.c, explicitly use memcpy() in order >>> to allow

Re: [PATCH v2] pvcalls-front: fix potential null dereference

On 1/14/19 9:31 PM, Wen Yang wrote: > static checker warning: > drivers/xen/pvcalls-front.c:373 alloc_active_ring() > error: we previously assumed 'map->active.ring' could be null >(see line 357) > > drivers/xen/pvcalls-front.c > 351 static int alloc_active_ring(struct

Re: [PATCH] mm: Make CONFIG_FRAME_VECTOR a visible option

On Tue, Jan 15, 2019 at 08:44:35AM -0800, Olof Johansson wrote: > CONFIG_FRAME_VECTOR was made an option to avoid including the bloat on > platforms that try to keep footprint down, which makes sense. > > The problem with this is external modules that aren't built in-tree. > Since they don't have

[PATCH] arm64: dts: imx: Fix MU4_INT number

MU4_INT correct number is 180, while 179 is for MU3_INT. Signed-off-by: Daniel Baluta --- arch/arm64/boot/dts/freescale/imx8qxp.dtsi | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/arch/arm64/boot/dts/freescale/imx8qxp.dtsi b/arch/arm64/boot/dts/freescale/imx8qxp.dtsi index

Want editing?

Want editing your photos? We can help. No matter you need photos background cutting out , or adding clipping path, or even retouching. We are the right studio that who can help you for your photo editing with the quality you need. Let me know if interested. Thanks, Nancy

[PATCH v3] staging: Mediatek: Use individual config flags in Makefile

These drivers can be useful on other MT76xx SoCs, which have compatible peripherals. The drivers were selectable in Kconfig, but they were quietly excluded from the build because the SOC_MT7621 chip was not selected. So, make the Makefiles use the same flags as Kconfig for these drivers.

Re: [PATCH] mm, memory_hotplug: __offline_pages fix wrong locking

On Tue 15-01-19 13:03:07, Michal Hocko wrote: > From: Michal Hocko > > Jan has noticed that we do double unlock on some failure paths when > offlining a page range. This is indeed the case when test_pages_in_a_zone > respp. start_isolate_page_range fail. This was an omission when forward >

[PATCH 4.4 11/51] Btrfs: improve check_node to avoid reading corrupted nodes

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Liu Bo commit 6b722c1747d533ac6d4df110dc8233db46918b65 upstream. We need to check items in a node to make sure that we're reading a valid one, otherwise we could get various crashes while

[PATCH] irqchip/irq-csky-mpintc: Add triger type and priority setting

From: Guo Ren Support 4 triger types: - IRQ_TYPE_LEVEL_HIGH - IRQ_TYPE_LEVEL_LOW - IRQ_TYPE_EDGE_RISING - IRQ_TYPE_EDGE_FALLING Support 0-255 priority setting for each irq. Signed-off-by: Guo Ren --- .../bindings/interrupt-controller/csky,mpintc.txt | 24 ++-

[PATCH 4.4 02/51] btrfs: cleanup, stop casting for extent_map->lookup everywhere

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Jeff Mahoney commit 95617d69326ce386c95e33db7aeb832b45ee9f8f upstream. Overloading extent_map->bdev to struct map_lookup * might have started out as a means to an end, but it's a pattern

[PATCH 4.4 25/51] btrfs: tree-check: reduce stack consumption in check_dir_item

4.4-stable review patch. If anyone has any objections, please let me know. -- From: David Sterba commit e2683fc9d219430f5b78889b50cde7f40efeba7b upstream. I've noticed that the updated item checker stack consumption increased dramatically in 542f5385e20cf97447 ("btrfs:

Re: [PATCH V2 0/5] i2c:ocores: improvements

Hi there, I just want to ask if there has been any update about this patchset that I'm not aware off. Thanks On Tuesday, November 27, 2018 12:38:22 PM CET Wolfram Sang wrote: > > This patch set provides improvements to the i2c-ocore driver. > > > > [V1 -> V2] > > - replaced usleep_range() with

[PATCH 4.4 08/51] Btrfs: check btree nodes nritems

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Liu Bo commit 053ab70f0604224c7893b43f9d9d5efa283580d6 upstream. When btree node (level = 1) has nritems which equals to zero, we can end up with panic due to insert_ptr()'s BUG_ON(slot >

[PATCH 4.4 00/51] 4.4.171-stable review

This is the start of the stable review cycle for the 4.4.171 release. There are 51 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 Thu Jan 17 15:48:21 UTC 2019. Anything

[PATCH 4.4 07/51] Btrfs: detect corruption when non-root leaf has zero item

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Liu Bo commit 1ba98d086fe3a14d6a31f2f66dbab70c45d00f63 upstream. Right now we treat leaf which has zero item as a valid one because we could have an empty tree, that is, a root that is also a

[PATCH 4.4 17/51] btrfs: Check if item pointer overlaps with the item itself

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Qu Wenruo commit 7f43d4affb2a254d421ab20b0cf65ac2569909fb upstream. Function check_leaf() checks if any item pointer points outside of the leaf, but it doesn't check if the pointer overlaps

[PATCH 4.4 26/51] btrfs: tree-checker: Verify block_group_item

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Qu Wenruo commit fce466eab7ac6baa9d2dcd88abcf945be3d4a089 upstream. A crafted image with invalid block group items could make free space cache code to cause panic. We could detect such

[PATCH 4.4 36/51] USB: storage: dont insert sane sense for SPC3+ when bad sense specified

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Icenowy Zheng commit c5603d2fdb424849360fe7e3f8c1befc97571b8c upstream. Currently the code will set US_FL_SANE_SENSE flag unconditionally if device claims SPC3+, however we should allow

[PATCH 4.4 32/51] btrfs: tree-checker: Fix misleading group system information

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Shaokun Zhang commit 761333f2f50ccc887aa9957ae829300262c0d15b upstream. block_group_err shows the group system as a decimal value with a '0x' prefix, which is somewhat misleading. Fix it to

[PATCH 4.4 28/51] btrfs: validate type when reading a chunk

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Gu Jinxiang commit 315409b0098fb2651d86553f0436b70502b29bb2 upstream. Reported in https://bugzilla.kernel.org/show_bug.cgi?id=199839, with an image that has an invalid chunk type but does not

[PATCH 4.4 37/51] USB: storage: add quirk for SMI SM3350

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Icenowy Zheng commit 0a99cc4b8ee83885ab9f097a3737d1ab28455ac0 upstream. The SMI SM3350 USB-UFS bridge controller cannot handle long sense request correctly and will make the chip refuse to do

[PATCH 4.4 31/51] btrfs: tree-checker: Check level for leaves and nodes

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Qu Wenruo commit f556faa46eb4e96d0d0772e74ecf66781e132f72 upstream. Although we have tree level check at tree read runtime, it's completely based on its parent level. We still need to do

[PATCH 4.4 46/51] PCI: altera: Move retrain from fixup to altera_pcie_host_init()

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Ley Foon Tan commit ce4f1c7ad490aa7129bde5632d6e53943f8a866c upstream. Previously we used a PCI early fixup to initiate a link retrain on Altera devices. But Altera PCIe IP can be configured

Re: [PATCH 2/2] fuse: Replace page without copying in fuse_writepage_in_flight()

On 15.01.2019 19:36, Miklos Szeredi wrote: > On Tue, Jan 15, 2019 at 5:14 PM Kirill Tkhai wrote: >> >> On 15.01.2019 18:39, Miklos Szeredi wrote: >>> On Mon, Nov 26, 2018 at 10:46 AM Kirill Tkhai wrote: It looks like we can optimize old_req page replacement and avoid copying by

Licensing of include/linux/hash.h

Hi Nadia, As part of the licensing assessment on pahole [0] that I am making for Debian, I realized that file hash.h in both pahole [1] and the kernel [2] comes without any licensing specification. Could you please make an explicit choice and maybe provide patches? Kind regards, Domenico [0]

[PATCH 4.4 39/51] slab: alien caches must not be initialized if the allocation of the alien cache failed

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Christoph Lameter commit 09c2e76ed734a1d36470d257a778aaba28e86531 upstream. Callers of __alloc_alien() check for NULL. We must do the same check in __alloc_alien_cache to avoid NULL pointer

[PATCH 4.4 43/51] PCI: altera: Poll for link up status after retraining the link

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Ley Foon Tan commit 3a928e98a833e1a470a60d2fedf3c55502185fb7 upstream. Some PCIe devices take a long time to reach link up state after retrain. Poll for link up status after retraining the

[PATCH 4.4 42/51] PCI: altera: Check link status before retrain link

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Ley Foon Tan commit c622032ebc538cb3869c312ae3ad235a99da84b6 upstream. Check the link status before retraining. If the link is not up, don't bother trying to retrain it. [bhelgaas: split

[PATCH v2 2/2] staging: rtl8188eu: add spaces around operators in os_intfs.c

Add spaces around '+', '<<' and '*' to follow kernel coding style. Reported by checkpatch. Signed-off-by: Michael Straube --- drivers/staging/rtl8188eu/os_dep/os_intfs.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/drivers/staging/rtl8188eu/os_dep/os_intfs.c

[PATCH 4.4 48/51] i2c: dev: prevent adapter retries and timeout being set as minus value

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Yi Zeng commit 6ebec961d59bccf65d08b13fc1ad4e6272a89338 upstream. If adapter->retries is set to a minus value from user space via ioctl, it will make __i2c_transfer and __i2c_smbus_xfer skip

[PATCH 4.4 47/51] ACPI: power: Skip duplicate power resource references in _PRx

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Hans de Goede commit 7d7b467cb95bf29597b417d4990160d4ea6d69b9 upstream. Some ACPI tables contain duplicate power resource references like this: Name (_PR0, Package (0x04) // _PR0:

[PATCH 4.4 19/51] btrfs: Add checker for EXTENT_CSUM

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Qu Wenruo commit 4b865cab96fe2a30ed512cf667b354bd291b3b0a upstream. EXTENT_CSUM checker is a relatively easy one, only needs to check: 1) Objectid Fixed to BTRFS_EXTENT_CSUM_OBJECTID 2)

[PATCH v2 1/2] staging: rtl8188eu: cleanup declarations in os_intfs.c

Replace tabs with spaces and/or remove extra spaces in declarations. Signed-off-by: Michael Straube --- v1 -> v2 added missing Signed-off-by drivers/staging/rtl8188eu/os_dep/os_intfs.c | 12 ++-- 1 file changed, 6 insertions(+), 6 deletions(-) diff --git

[PATCH 4.4 22/51] btrfs: tree-checker: Fix false panic for sanity test

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Qu Wenruo commit 69fc6cbbac542c349b3d350d10f6e394c253c81d upstream. [BUG] If we run btrfs with CONFIG_BTRFS_FS_RUN_SANITY_TESTS=y, it will instantly cause kernel panic like: -- ...

[PATCH 4.9 15/16] ext4: avoid kernel warning when writing the superblock to a dead device

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Theodore Ts'o commit e86807862e6880809f191c4cea7f88a489f0ed34 upstream. The xfstests generic/475 test switches the underlying device with dm-error while running a stress test. This results in

[PATCH 4.4 15/51] btrfs: struct-funcs, constify readers

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Jeff Mahoney commit 1cbb1f454e5321e47fc1e6b233066c7ccc979d15 upstream. We have reader helpers for most of the on-disk structures that use an extent_buffer and pointer as offset into the buffer

[PATCH 4.9 11/16] i2c: dev: prevent adapter retries and timeout being set as minus value

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Yi Zeng commit 6ebec961d59bccf65d08b13fc1ad4e6272a89338 upstream. If adapter->retries is set to a minus value from user space via ioctl, it will make __i2c_transfer and __i2c_smbus_xfer skip

[PATCH 4.9 06/16] USB: storage: add quirk for SMI SM3350

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Icenowy Zheng commit 0a99cc4b8ee83885ab9f097a3737d1ab28455ac0 upstream. The SMI SM3350 USB-UFS bridge controller cannot handle long sense request correctly and will make the chip refuse to do

[PATCH 4.9 02/16] CIFS: Do not hide EINTR after sending network packets

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Pavel Shilovsky commit ee13919c2e8d1f904e035ad4b4239029a8994131 upstream. Currently we hide EINTR code returned from sock_sendmsg() and return 0 instead. This makes a caller think that we

[PATCH 4.14 19/27] drm/fb-helper: Partially bring back workaround for bugs of SDL 1.2

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Ivan Mironov commit 62d85b3bf9d978ed4b6b2aeef5cf0ccf1423906e upstream. SDL 1.2 sets all fields related to the pixel format to zero in some cases[1]. Prior to commit db05c48197759 ("drm:

[PATCH 4.14 02/27] x86, modpost: Replace last remnants of RETPOLINE with CONFIG_RETPOLINE

4.14-stable review patch. If anyone has any objections, please let me know. -- From: WANG Chao commit e4f358916d528d479c3c12bd2fd03f2d5a576380 upstream. Commit 4cd24de3a098 ("x86/retpoline: Make CONFIG_RETPOLINE depend on compiler support") replaced the RETPOLINE define

[PATCH 4.14 05/27] ALSA: hda/realtek - Disable headset Mic VREF for headset mode of ALC225

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Kailang Yang commit d1dd42110d2727e81b9265841a62bc84c454c3a2 upstream. Disable Headset Mic VREF for headset mode of ALC225. This will be controlled by coef bits of headset mode functions. [

[PATCH 4.9 00/16] 4.9.151-stable review

This is the start of the stable review cycle for the 4.9.151 release. There are 16 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 Thu Jan 17 15:48:25 UTC 2019. Anything

[PATCH 4.9 07/16] USB: Add USB_QUIRK_DELAY_CTRL_MSG quirk for Corsair K70 RGB

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Jack Stocker commit 3483254b89438e60f719937376c5e0ce2bc46761 upstream. To match the Corsair Strafe RGB, the Corsair K70 RGB also requires USB_QUIRK_DELAY_CTRL_MSG to completely resolve boot

Re: [PATCH 1/2] ARCv2: LIB: memeset: fix doing prefetchw outside of buffer

On 1/15/19 4:00 AM, Eugeniy Paltsev wrote: >>> -#ifdef PREALLOC_NOT_AVAIL >>> - prefetchw [r3, 64] ;Prefetch the next write location >>> -#else >>> - prealloc [r3, 64] >>> -#endif >>> + PREALLOC_INSTR([r3, 64]) ;Prefetch the next write location >> These are not solving the issue - I'd

[PATCH v3] x86-64/Xen: fix stack switching

While in the native case entry into the kernel happens on the trampoline stack, PV Xen kernels get entered with the current thread stack right away. Hence source and destination stacks are identical in that case, and special care is needed. Other than in sync_regs() the copying done on the INT80

[PATCH] MAINTAINERS: add myself as SPI NOR co-maintainer

From: Tudor Ambarus I have been reviewing and contributing to the SPI NOR subsystem for the last few months and I'm willing to continue doing so. Volunteer as a maintainer for the SPI NOR part of the MTD subsystem. Signed-off-by: Tudor Ambarus --- MAINTAINERS | 1 + 1 file changed, 1

[PATCH 4.14 17/27] ACPI / PMIC: xpower: Fix TS-pin current-source handling

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Hans de Goede commit 2b531d71595d2b5b12782a49b23c335869e2621e upstream. The current-source used for the battery temp-sensor (TS) is shared with the GPADC. For proper fuel-gauge and charger

[PATCH 4.14 23/27] ext4: avoid kernel warning when writing the superblock to a dead device

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Theodore Ts'o commit e86807862e6880809f191c4cea7f88a489f0ed34 upstream. The xfstests generic/475 test switches the underlying device with dm-error while running a stress test. This results

[PATCH 4.14 20/27] rbd: dont return 0 on unmap if RBD_DEV_FLAG_REMOVING is set

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Ilya Dryomov commit 85f5a4d666fd9be73856ed16bb36c5af5b406b29 upstream. There is a window between when RBD_DEV_FLAG_REMOVING is set and when the device is removed from rbd_dev_list. During

[PATCH 4.14 06/27] CIFS: Fix adjustment of credits for MTU requests

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Pavel Shilovsky commit b983f7e92348d7e7d091db1b78b7915e9dd3d63a upstream. Currently for MTU requests we allocate maximum possible credits in advance and then adjust them according to the

[PATCH 4.19 13/50] cifs: Fix potential OOB access of lock element array

4.19-stable review patch. If anyone has any objections, please let me know. -- From: Ross Lagerwall commit b9a74cde94957d82003fb9f7ab4777938ca851cd upstream. If maxBuf is small but non-zero, it could result in a zero sized lock element array which we would then try and access

[PATCH 4.14 11/27] USB: storage: add quirk for SMI SM3350

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Icenowy Zheng commit 0a99cc4b8ee83885ab9f097a3737d1ab28455ac0 upstream. The SMI SM3350 USB-UFS bridge controller cannot handle long sense request correctly and will make the chip refuse to do

[PATCH] clocksource: use BIT() for clock source flags

Signed-off-by: Yangtao Li --- include/linux/clocksource.h | 16 1 file changed, 8 insertions(+), 8 deletions(-) diff --git a/include/linux/clocksource.h b/include/linux/clocksource.h index b21db536fd52..130f4c3c0781 100644 --- a/include/linux/clocksource.h +++

[PATCH 4.14 13/27] slab: alien caches must not be initialized if the allocation of the alien cache failed

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Christoph Lameter commit 09c2e76ed734a1d36470d257a778aaba28e86531 upstream. Callers of __alloc_alien() check for NULL. We must do the same check in __alloc_alien_cache to avoid NULL pointer

[PATCH 4.14 09/27] usb: cdc-acm: send ZLP for Telit 3G Intel based modems

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Daniele Palmas commit 34aabf918717dd14e05051896aaecd3b16b53d95 upstream. Telit 3G Intel based modems require zero packet to be sent if out data size is equal to the endpoint max packet size.

[PATCH 4.19 11/50] CIFS: Do not hide EINTR after sending network packets

4.19-stable review patch. If anyone has any objections, please let me know. -- From: Pavel Shilovsky commit ee13919c2e8d1f904e035ad4b4239029a8994131 upstream. Currently we hide EINTR code returned from sock_sendmsg() and return 0 instead. This makes a caller think that we

[PATCH 4.19 12/50] CIFS: Fix credit computation for compounded requests

4.19-stable review patch. If anyone has any objections, please let me know. -- From: Pavel Shilovsky commit 8544f4aa9dd19a04d1244dae10feecc813ccf175 upstream. In SMB3 protocol every part of the compound chain consumes credits individually, so we need to call

[PATCH 4.14 25/27] ext4: track writeback errors using the generic tracking infrastructure

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Theodore Ts'o commit 95cb67138746451cc84cf8e516e14989746e93b0 upstream. We already using mapping_set_error() in fs/ext4/page_io.c, so all we need to do is to use

[PATCH 4.19 01/50] Btrfs: fix deadlock when using free space tree due to block group creation

4.19-stable review patch. If anyone has any objections, please let me know. -- From: Filipe Manana commit a6d8654d885d7d79a3fb82da64eaa489ca332a82 upstream. When modifying the free space tree we can end up COWing one of its extent buffers which in turn might result in

[PATCH 4.19 10/50] CIFS: Do not set credits to 1 if the server didnt grant anything

4.19-stable review patch. If anyone has any objections, please let me know. -- From: Pavel Shilovsky commit 33fa5c8b8a7dbe6353a56eaa654b790348890d42 upstream. Currently we reset the number of total credits granted by the server to 1 if the server didn't grant us anything int

[PATCH 4.14 12/27] USB: Add USB_QUIRK_DELAY_CTRL_MSG quirk for Corsair K70 RGB

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Jack Stocker commit 3483254b89438e60f719937376c5e0ce2bc46761 upstream. To match the Corsair Strafe RGB, the Corsair K70 RGB also requires USB_QUIRK_DELAY_CTRL_MSG to completely resolve boot

[PATCH 4.19 18/50] slab: alien caches must not be initialized if the allocation of the alien cache failed

4.19-stable review patch. If anyone has any objections, please let me know. -- From: Christoph Lameter commit 09c2e76ed734a1d36470d257a778aaba28e86531 upstream. Callers of __alloc_alien() check for NULL. We must do the same check in __alloc_alien_cache to avoid NULL pointer

[GIT PULL] tracing/kprobes: Fix NULL pointer dereference in trace_kprobe_create()

Linus, Andrea Righi fixed a NULL pointer dereference in trace_kprobe_create() It is possible to trigger a NULL pointer dereference by writing an incorrectly formatted string to the krpobe_events file. Please pull the latest trace-v5.0-rc1 tree, which can be found at:

Re: [RFC PATCH v2 2/2] kexec, KEYS: Make use of platform keyring for signature verify

On Tue, Jan 15, 2019 at 11:47 PM Mimi Zohar wrote: > > On Tue, 2019-01-15 at 17:45 +0800, Kairui Song wrote: > > > diff --git a/arch/x86/kernel/kexec-bzimage64.c > > b/arch/x86/kernel/kexec-bzimage64.c > > index 7d97e432cbbc..a06b04065bb1 100644 > > --- a/arch/x86/kernel/kexec-bzimage64.c > >

[PATCH 4.19 23/50] ACPI/IORT: Fix rc_dma_get_range()

4.19-stable review patch. If anyone has any objections, please let me know. -- From: Jean-Philippe Brucker commit c236dd8f587f6a8d6800c03df318fd4d2627 upstream. When executed for a PCI_ROOT_COMPLEX type, iort_match_node_callback() expects the opaque pointer argument to be

[PATCH 4.19 21/50] ACPI: power: Skip duplicate power resource references in _PRx

4.19-stable review patch. If anyone has any objections, please let me know. -- From: Hans de Goede commit 7d7b467cb95bf29597b417d4990160d4ea6d69b9 upstream. Some ACPI tables contain duplicate power resource references like this: Name (_PR0, Package (0x04) // _PR0:

[PATCH 4.19 27/50] drm/amdgpu: Add new VegaM pci id

4.19-stable review patch. If anyone has any objections, please let me know. -- From: Alex Deucher commit f6653a0e0877572c87f6dab5351e7bd6b6b7100c upstream. Add a new pci id. Reviewed-by: Leo Liu Signed-off-by: Alex Deucher Cc: sta...@vger.kernel.org Signed-off-by: Greg

[PATCH 4.19 30/50] PCI: dwc: Move interrupt acking into the proper callback

4.19-stable review patch. If anyone has any objections, please let me know. -- From: Marc Zyngier commit 3f7bb2ec20ce07c02b2002349d256c91a463fcc5 upstream. The write to the status register is really an ACK for the HW, and should be treated as such by the driver. Let's move it

[PATCH 4.19 33/50] drm/fb-helper: Partially bring back workaround for bugs of SDL 1.2

4.19-stable review patch. If anyone has any objections, please let me know. -- From: Ivan Mironov commit 62d85b3bf9d978ed4b6b2aeef5cf0ccf1423906e upstream. SDL 1.2 sets all fields related to the pixel format to zero in some cases[1]. Prior to commit db05c48197759 ("drm:

[PATCH 4.19 28/50] PCI: dwc: Use interrupt masking instead of disabling

4.19-stable review patch. If anyone has any objections, please let me know. -- From: Marc Zyngier commit 830920e065e90db318a0da98bf13a02b641eae7f upstream. The dwc driver is showing an interesting level of brokeness, as it insists on using the enable/disable set of registers

[PATCH 4.19 32/50] drm/fb_helper: Allow leaking fbdev smem_start

4.19-stable review patch. If anyone has any objections, please let me know. -- From: Neil Armstrong commit 4be9bd10e22dfc7fc101c5cf5969ef2d3a042d8a upstream. Since "drm/fb: Stop leaking physical address", the default behaviour of the DRM fbdev emulation is to set the

Re: [PATCH v4 0/3] mtd: rawnand: add STM32 FMC2 NAND flash controller driver

Hi Christophe, Christophe Kerello wrote on Fri, 14 Dec 2018 10:58:05 +0100: > This patchset adds the support for the STMicroelectronics FMC2 NAND flash > controller found on STM32MP SOCs. > > This patchset supports: > - the command sequencer feature, a hardware accelerator for read/write >

[PATCH 4.19 07/50] ALSA: hda/realtek - Add unplug function into unplug state of Headset Mode for ALC225

4.19-stable review patch. If anyone has any objections, please let me know. -- From: Kailang Yang commit 4d4b0c52bde470c379f5d168d5c139ad866cb808 upstream. Forgot to add unplug function to unplug state of headset mode for ALC225. Signed-off-by: Kailang Yang Cc:

[PATCH 4.19 00/50] 4.19.16-stable review

This is the start of the stable review cycle for the 4.19.16 release. There are 50 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 Thu Jan 17 15:48:36 UTC 2019. Anything

Re: [PATCH] USB: Fix configuration selection issues introduced in v4.20.0

On Tue, Jan 15, 2019 at 07:13:54PM +0300, Nikolay Yakimov wrote: > Commit f13912d3f014a introduced changes to the usb_choose_configuration > function > to better support USB Audio UAC3-compatible devices. However, there are a few > problems with this patch. First of all, it adds new "if" clauses

[PATCH 4.19 06/50] ALSA: hda/realtek - Support Dell headset mode for New AIO platform

4.19-stable review patch. If anyone has any objections, please let me know. -- From: Kailang Yang commit c2a7c55a04065c3b0c32d23b099db7ea1dbf6250 upstream. Dell has new platform for ALC274. This will support to enable headset mode. Signed-off-by: Kailang Yang Cc:

[PATCH 4.19 37/50] rbd: dont return 0 on unmap if RBD_DEV_FLAG_REMOVING is set

4.19-stable review patch. If anyone has any objections, please let me know. -- From: Ilya Dryomov commit 85f5a4d666fd9be73856ed16bb36c5af5b406b29 upstream. There is a window between when RBD_DEV_FLAG_REMOVING is set and when the device is removed from rbd_dev_list. During

[PATCH 4.19 49/50] Btrfs: fix deadlock when enabling quotas due to concurrent snapshot creation

4.19-stable review patch. If anyone has any objections, please let me know. -- From: Filipe Manana commit 9a6f209e36500efac51528132a3e3083586eda5f upstream. If the quota enable and snapshot creation ioctls are called concurrently we can get into a deadlock where the task

Re: [PATCH] kvm: add proper frame pointer logic for vmx

On 1/15/19 11:34 AM, Sean Christopherson wrote: > On Tue, Jan 15, 2019 at 08:13:22AM +0100, Paolo Bonzini wrote: >> On 15/01/19 08:04, Qian Cai wrote: >>> >>> >>> On 1/15/19 1:44 AM, Qian Cai wrote: compilation warning since v5.0-rc1, arch/x86/kvm/vmx/vmx.o: warning: objtool:

[PATCH 4.19 45/50] sunrpc: use-after-free in svc_process_common()

4.19-stable review patch. If anyone has any objections, please let me know. -- From: Vasily Averin commit d4b09acf924b84bae77cad090a9d108e70b43643 upstream. if node have NFSv41+ mounts inside several net namespaces it can lead to use-after-free in svc_process_common()

[PATCH 4.19 48/50] Btrfs: fix access to available allocation bits when starting balance

4.19-stable review patch. If anyone has any objections, please let me know. -- From: Filipe Manana commit 5a8067c0d17feb7579db0476191417b441a8996e upstream. The available allocation bits members from struct btrfs_fs_info are protected by a sequence lock, and when starting

[PATCH 4.19 41/50] ext4: use ext4_write_inode() when fsyncing w/o a journal

4.19-stable review patch. If anyone has any objections, please let me know. -- From: Theodore Ts'o commit ad211f3e94b314a910d4af03178a0b52a7d1ee0a upstream. In no-journal mode, we previously used __generic_file_fsync() in no-journal mode. This triggers a lockdep warning, and

Re: [PATCH v9 0/2] mtd: rawnand: meson: add Amlogic NAND driver support

Miquel Raynal wrote on Tue, 15 Jan 2019 17:52:32 +0100: > Hi Jianxin, > > Jianxin Pan wrote on Tue, 15 Jan 2019 > 23:38:02 +0800: > > > These two patches try to add initial NAND driver support for Amlogic Meson > > SoCs, current it has been tested on GXL(p212) and AXG(s400) platform. > > >

Re: [PATCH] kvm: add proper frame pointer logic for vmx

On 1/15/19 2:13 AM, Paolo Bonzini wrote: > Hmm, maybe like this: > > diff --git a/arch/x86/kvm/vmx/vmenter.S b/arch/x86/kvm/vmx/vmenter.S > index bcef2c7e9bc4..33122fa9d4bd 100644 > --- a/arch/x86/kvm/vmx/vmenter.S > +++ b/arch/x86/kvm/vmx/vmenter.S > @@ -26,19 +26,17 @@ ENTRY(vmx_vmenter) >

[PATCH 4.20 01/57] powerpc/tm: Unset MSR[TS] if not recheckpointing

4.20-stable review patch. If anyone has any objections, please let me know. -- From: Breno Leitao commit 6f5b9f018f4c7686fd944d920209d1382d320e4e upstream. There is a TM Bad Thing bug that can be caused when you return from a signal context in a suspended transaction but with

[PATCH 4.19 35/50] drm/amdgpu: Dont ignore rc from drm_dp_mst_topology_mgr_resume()

4.19-stable review patch. If anyone has any objections, please let me know. -- From: Lyude Paul commit fe7553bef8d676d1d8b40666868b33ec39b9df5d upstream. drm_dp_mst_topology_mgr_resume() returns whether or not it managed to find the topology in question after a suspend resume

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