[PATCH 4.4 54/73] pinctrl: at91-pio4: fix pull-up/down logic

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Ludovic Desroches commit 5305a7b7e860bb40ab226bc7d58019416073948a upstream. The default configuration of a pin is often with a value in the pull-up/down field at

[PATCH 4.4 55/73] regmap: spmi: Fix regmap_spmi_ext_read in multi-byte case

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Jack Pham commit dec8e8f6e6504aa3496c0f7cc10c756bb0e10f44 upstream. Specifically for the case of reads that use the Extended Register Read Long command, a multi-byte read

[PATCH 4.4 54/73] pinctrl: at91-pio4: fix pull-up/down logic

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Ludovic Desroches commit 5305a7b7e860bb40ab226bc7d58019416073948a upstream. The default configuration of a pin is often with a value in the pull-up/down field at chip reset. So, even if the

[PATCH 4.4 55/73] regmap: spmi: Fix regmap_spmi_ext_read in multi-byte case

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Jack Pham commit dec8e8f6e6504aa3496c0f7cc10c756bb0e10f44 upstream. Specifically for the case of reads that use the Extended Register Read Long command, a multi-byte read operation is broken

[PATCH 4.4 52/73] spi: spi-ti-qspi: Fix FLEN and WLEN settings if bits_per_word is overridden

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Ben Hutchings commit ea1b60fb085839a9544cb3a0069992991beabb7f upstream. Each transfer can specify 8, 16 or 32 bits per word independently of the default for the

[PATCH 4.4 52/73] spi: spi-ti-qspi: Fix FLEN and WLEN settings if bits_per_word is overridden

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Ben Hutchings commit ea1b60fb085839a9544cb3a0069992991beabb7f upstream. Each transfer can specify 8, 16 or 32 bits per word independently of the default for the device being addressed.

[PATCH 4.4 53/73] spi: spi-ti-qspi: Handle truncated frames properly

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Ben Hutchings commit 1ff7760ff66b98ef244bf0e5e2bd5310651205ad upstream. We clamp frame_len_words to a maximum of 4096, but do not actually limit the number of

[PATCH 4.4 53/73] spi: spi-ti-qspi: Handle truncated frames properly

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Ben Hutchings commit 1ff7760ff66b98ef244bf0e5e2bd5310651205ad upstream. We clamp frame_len_words to a maximum of 4096, but do not actually limit the number of words written or read through the

[PATCH 4.4 51/73] spi: pxa2xx: Do not detect number of enabled chip selects on Intel SPT

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Jarkko Nikula commit 66ec246eb9982e7eb8e15e1fc55f543230310dd0 upstream. Certain Intel Sunrisepoint PCH variants report zero chip selects in SPI capabilities

[PATCH 4.4 51/73] spi: pxa2xx: Do not detect number of enabled chip selects on Intel SPT

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Jarkko Nikula commit 66ec246eb9982e7eb8e15e1fc55f543230310dd0 upstream. Certain Intel Sunrisepoint PCH variants report zero chip selects in SPI capabilities register even they have one per

[PATCH 4.4 57/73] vfs: add vfs_select_inode() helper

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Miklos Szeredi commit 54d5ca871e72f2bb172ec9323497f01cd5091ec7 upstream. Signed-off-by: Miklos Szeredi Signed-off-by: Greg Kroah-Hartman

[PATCH 4.4 57/73] vfs: add vfs_select_inode() helper

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Miklos Szeredi commit 54d5ca871e72f2bb172ec9323497f01cd5091ec7 upstream. Signed-off-by: Miklos Szeredi Signed-off-by: Greg Kroah-Hartman --- fs/open.c | 12

[PATCH 4.4 59/73] ARM: dts: at91: sam9x5: Fix the memory range assigned to the PMC

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Boris Brezillon commit aab0a4c83ceb344d2327194bf354820e50607af6 upstream. The memory range assigned to the PMC (Power Management Controller) was not

[PATCH 4.4 58/73] vfs: rename: check backing inode being equal

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Miklos Szeredi commit 9409e22acdfc9153f88d9b1ed2bd2a5b34d2d3ca upstream. If a file is renamed to a hardlink of itself POSIX specifies that rename(2) should do nothing and

[PATCH 4.4 59/73] ARM: dts: at91: sam9x5: Fix the memory range assigned to the PMC

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Boris Brezillon commit aab0a4c83ceb344d2327194bf354820e50607af6 upstream. The memory range assigned to the PMC (Power Management Controller) was not including the PMC_PCR register which are

[PATCH 4.4 58/73] vfs: rename: check backing inode being equal

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Miklos Szeredi commit 9409e22acdfc9153f88d9b1ed2bd2a5b34d2d3ca upstream. If a file is renamed to a hardlink of itself POSIX specifies that rename(2) should do nothing and return success. This

[PATCH 4.4 61/73] regulator: s2mps11: Fix invalid selector mask and voltages for buck9

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Krzysztof Kozlowski commit 3b672623079bb3e5685b8549e514f2dfaa564406 upstream. The buck9 regulator of S2MPS11 PMIC had incorrect vsel_mask (0xff instead of 0x1f) thus

[PATCH 4.4 63/73] atomic_open(): fix the handling of create_error

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Al Viro commit 10c64cea04d3c75c306b3f990586ffb343b63287 upstream. * if we have a hashed negative dentry and either CREAT|EXCL on r/o filesystem, or CREAT|TRUNC on r/o

Re: [PATCH v5 02/12] mm: migrate: support non-lru movable page migration

On Mon, May 16, 2016 at 04:17:51PM +0900, Sergey Senozhatsky wrote: > On (05/09/16 11:20), Minchan Kim wrote: > [..] > > +++ b/include/linux/migrate.h > > @@ -32,11 +32,16 @@ extern char *migrate_reason_names[MR_TYPES]; > > > > #ifdef CONFIG_MIGRATION > > > > +extern int PageMovable(struct

[PATCH 4.4 61/73] regulator: s2mps11: Fix invalid selector mask and voltages for buck9

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Krzysztof Kozlowski commit 3b672623079bb3e5685b8549e514f2dfaa564406 upstream. The buck9 regulator of S2MPS11 PMIC had incorrect vsel_mask (0xff instead of 0x1f) thus reading entire register as

[PATCH 4.4 63/73] atomic_open(): fix the handling of create_error

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Al Viro commit 10c64cea04d3c75c306b3f990586ffb343b63287 upstream. * if we have a hashed negative dentry and either CREAT|EXCL on r/o filesystem, or CREAT|TRUNC on r/o filesystem, or CREAT|EXCL

Re: [PATCH v5 02/12] mm: migrate: support non-lru movable page migration

On Mon, May 16, 2016 at 04:17:51PM +0900, Sergey Senozhatsky wrote: > On (05/09/16 11:20), Minchan Kim wrote: > [..] > > +++ b/include/linux/migrate.h > > @@ -32,11 +32,16 @@ extern char *migrate_reason_names[MR_TYPES]; > > > > #ifdef CONFIG_MIGRATION > > > > +extern int PageMovable(struct

[PATCH 4.4 66/73] get_rock_ridge_filename(): handle malformed NM entries

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Al Viro commit 99d825822eade8d827a1817357cbf3f889a552d6 upstream. Payloads of NM entries are not supposed to contain NUL. When we run into such, only the part prior

[PATCH 4.4 66/73] get_rock_ridge_filename(): handle malformed NM entries

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Al Viro commit 99d825822eade8d827a1817357cbf3f889a552d6 upstream. Payloads of NM entries are not supposed to contain NUL. When we run into such, only the part prior to the first NUL goes into

[PATCH 4.4 62/73] regulator: axp20x: Fix axp22x ldo_io voltage ranges

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Hans de Goede commit a2262e5a12e05389ab4c7fc5cf60016b041dd8dc upstream. The minium voltage of 1800mV is a copy and paste error from the axp20x regulator info. The correct

[PATCH 4.4 67/73] Input: max8997-haptic - fix NULL pointer dereference

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Marek Szyprowski commit 6ae645d5fa385f3787bf1723639cd907fe5865e7 upstream. NULL pointer derefence happens when booting with DTB because the platform data for haptic

[PATCH 4.4 62/73] regulator: axp20x: Fix axp22x ldo_io voltage ranges

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Hans de Goede commit a2262e5a12e05389ab4c7fc5cf60016b041dd8dc upstream. The minium voltage of 1800mV is a copy and paste error from the axp20x regulator info. The correct minimum voltage for

[PATCH 4.4 67/73] Input: max8997-haptic - fix NULL pointer dereference

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Marek Szyprowski commit 6ae645d5fa385f3787bf1723639cd907fe5865e7 upstream. NULL pointer derefence happens when booting with DTB because the platform data for haptic device is not set in

[PATCH 4.4 69/73] drm/radeon: fix PLL sharing on DCE6.1 (v2)

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Lucas Stach commit e3c00d87845ab375f90fa6e10a5e72a3a5778cd3 upstream. On DCE6.1 PPLL2 is exclusively available to UNIPHYA, so it should not be taken into consideration when

[PATCH 4.4 70/73] drm/i915: Bail out of pipe config compute loop on LPT

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Daniel Vetter commit 2700818ac9f935d8590715eecd7e8cadbca552b6 upstream. LPT is pch, so might run into the fdi bandwidth constraint (especially since it has only 2

[PATCH 4.4 69/73] drm/radeon: fix PLL sharing on DCE6.1 (v2)

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Lucas Stach commit e3c00d87845ab375f90fa6e10a5e72a3a5778cd3 upstream. On DCE6.1 PPLL2 is exclusively available to UNIPHYA, so it should not be taken into consideration when looking for an

[PATCH 4.4 70/73] drm/i915: Bail out of pipe config compute loop on LPT

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Daniel Vetter commit 2700818ac9f935d8590715eecd7e8cadbca552b6 upstream. LPT is pch, so might run into the fdi bandwidth constraint (especially since it has only 2 lanes). But right now we just

[PATCH 4.4 73/73] nf_conntrack: avoid kernel pointer value leak in slab name

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Linus Torvalds commit 31b0b385f69d8d5491a4bca288e25e63f1d945d0 upstream. The slab name ends up being visible in the directory structure under /sys, and even if

[PATCH 4.4 68/73] Revert "[media] videobuf2-v4l2: Verify planes array in buffer dequeueing"

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Mauro Carvalho Chehab commit 93f0750dcdaed083d6209b01e952e98ca730db66 upstream. This patch causes a Kernel panic when called on a DVB driver. This was also reported

[PATCH 4.4 73/73] nf_conntrack: avoid kernel pointer value leak in slab name

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Linus Torvalds commit 31b0b385f69d8d5491a4bca288e25e63f1d945d0 upstream. The slab name ends up being visible in the directory structure under /sys, and even if you don't have access rights to

[PATCH 4.4 68/73] Revert "[media] videobuf2-v4l2: Verify planes array in buffer dequeueing"

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Mauro Carvalho Chehab commit 93f0750dcdaed083d6209b01e952e98ca730db66 upstream. This patch causes a Kernel panic when called on a DVB driver. This was also reported by David R : May 7

[PATCH 3.14 14/17] VSOCK: do not disconnect socket when peer has shutdown SEND only

3.14-stable review patch. If anyone has any objections, please let me know. -- From: Ian Campbell [ Upstream commit dedc58e067d8c379a15a8a183c5db318201295bb ] The peer may be expecting a reply having sent a request and then done a shutdown(SHUT_WR),

[PATCH 3.14 07/17] ARM: OMAP3: Fix booting with thumb2 kernel

3.14-stable review patch. If anyone has any objections, please let me know. -- From: Tony Lindgren commit d8a50941c91a68da202aaa96a3dacd471ea9c693 upstream. We get a NULL pointer dereference on omap3 for thumb2 compiled kernels: Internal error: Oops:

[PATCH 4.4 72/73] drm/radeon: fix DP link training issue with second 4K monitor

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Arindam Nath commit 1a738347df2ee4977459a8776fe2c62196bdcb1b upstream. There is an issue observed when we hotplug a second DP 4K monitor to the system. Sometimes, the

[PATCH 4.4 20/73] net: Implement net_dbg_ratelimited() for CONFIG_DYNAMIC_DEBUG case

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Tim Bingham [ Upstream commit 2c94b53738549d81dc7464a32117d1f5112c64d3 ] Prior to commit d92cff89a0c8 ("net_dbg_ratelimited: turn into no-op when !DEBUG") the

[PATCH 3.14 14/17] VSOCK: do not disconnect socket when peer has shutdown SEND only

3.14-stable review patch. If anyone has any objections, please let me know. -- From: Ian Campbell [ Upstream commit dedc58e067d8c379a15a8a183c5db318201295bb ] The peer may be expecting a reply having sent a request and then done a shutdown(SHUT_WR), so tearing down the whole

[PATCH 3.14 07/17] ARM: OMAP3: Fix booting with thumb2 kernel

3.14-stable review patch. If anyone has any objections, please let me know. -- From: Tony Lindgren commit d8a50941c91a68da202aaa96a3dacd471ea9c693 upstream. We get a NULL pointer dereference on omap3 for thumb2 compiled kernels: Internal error: Oops: 8005 [#1] SMP THUMB2

[PATCH 4.4 72/73] drm/radeon: fix DP link training issue with second 4K monitor

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Arindam Nath commit 1a738347df2ee4977459a8776fe2c62196bdcb1b upstream. There is an issue observed when we hotplug a second DP 4K monitor to the system. Sometimes, the link training fails for

[PATCH 4.4 20/73] net: Implement net_dbg_ratelimited() for CONFIG_DYNAMIC_DEBUG case

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Tim Bingham [ Upstream commit 2c94b53738549d81dc7464a32117d1f5112c64d3 ] Prior to commit d92cff89a0c8 ("net_dbg_ratelimited: turn into no-op when !DEBUG") the implementation of

[PATCH 4.4 64/73] qla1280: Dont allocate 512kb of host tags

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Johannes Thumshirn commit 2bcbc81421c511ef117cadcf0bee9c4340e68db0 upstream. The qla1280 driver sets the scsi_host_template's can_queue field to 0xf which results in an

[PATCH 4.4 50/73] ALSA: hda - Fix broken reconfig

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Takashi Iwai commit addacd801e1638f41d659cb53b9b73fc14322cb1 upstream. The HD-audio reconfig function got broken in the recent kernels, typically resulting in a failure like:

[PATCH 4.4 64/73] qla1280: Dont allocate 512kb of host tags

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Johannes Thumshirn commit 2bcbc81421c511ef117cadcf0bee9c4340e68db0 upstream. The qla1280 driver sets the scsi_host_template's can_queue field to 0xf which results in an allocation failure

[PATCH 4.4 50/73] ALSA: hda - Fix broken reconfig

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Takashi Iwai commit addacd801e1638f41d659cb53b9b73fc14322cb1 upstream. The HD-audio reconfig function got broken in the recent kernels, typically resulting in a failure like: snd_hda_intel

[PATCH 3.14 10/17] packet: fix heap info leak in PACKET_DIAG_MCLIST sock_diag interface

3.14-stable review patch. If anyone has any objections, please let me know. -- From: Mathias Krause [ Upstream commit 309cf37fe2a781279b7675d4bb7173198e532867 ] Because we miss to wipe the remainder of i->addr[] in packet_mc_add(), pdiag_put_mclist()

[PATCH 3.14 05/17] drm/radeon: fix PLL sharing on DCE6.1 (v2)

3.14-stable review patch. If anyone has any objections, please let me know. -- From: Lucas Stach commit e3c00d87845ab375f90fa6e10a5e72a3a5778cd3 upstream. On DCE6.1 PPLL2 is exclusively available to UNIPHYA, so it should not be taken into consideration when

[PATCH 3.14 00/17] 3.14.70-stable review

This is the start of the stable review cycle for the 3.14.70 release. There are 17 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 May 19 01:13:32 UTC 2016. Anything

[PATCH 3.14 10/17] packet: fix heap info leak in PACKET_DIAG_MCLIST sock_diag interface

3.14-stable review patch. If anyone has any objections, please let me know. -- From: Mathias Krause [ Upstream commit 309cf37fe2a781279b7675d4bb7173198e532867 ] Because we miss to wipe the remainder of i->addr[] in packet_mc_add(), pdiag_put_mclist() leaks uninitialized heap

[PATCH 3.14 05/17] drm/radeon: fix PLL sharing on DCE6.1 (v2)

3.14-stable review patch. If anyone has any objections, please let me know. -- From: Lucas Stach commit e3c00d87845ab375f90fa6e10a5e72a3a5778cd3 upstream. On DCE6.1 PPLL2 is exclusively available to UNIPHYA, so it should not be taken into consideration when looking for an

[PATCH 3.14 00/17] 3.14.70-stable review

This is the start of the stable review cycle for the 3.14.70 release. There are 17 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 May 19 01:13:32 UTC 2016. Anything

[PATCH 3.14 06/17] drm/i915: Bail out of pipe config compute loop on LPT

3.14-stable review patch. If anyone has any objections, please let me know. -- From: Daniel Vetter commit 2700818ac9f935d8590715eecd7e8cadbca552b6 upstream. LPT is pch, so might run into the fdi bandwidth constraint (especially since it has only 2

[PATCH 3.14 01/17] crypto: hash - Fix page length clamping in hash walk

3.14-stable review patch. If anyone has any objections, please let me know. -- From: Herbert Xu commit 13f4bb78cf6a312bbdec367ba3da044b09bf0e29 upstream. The crypto hash walk code is broken when supplied with an offset greater than or equal to

[PATCH 3.14 08/17] decnet: Do not build routes to devices without decnet private data.

3.14-stable review patch. If anyone has any objections, please let me know. -- From: "David S. Miller" [ Upstream commit a36a0d4008488fa545c74445d69eaf56377d5d4e ] In particular, make sure we check for decnet private presence for loopback devices.

[PATCH 3.14 06/17] drm/i915: Bail out of pipe config compute loop on LPT

3.14-stable review patch. If anyone has any objections, please let me know. -- From: Daniel Vetter commit 2700818ac9f935d8590715eecd7e8cadbca552b6 upstream. LPT is pch, so might run into the fdi bandwidth constraint (especially since it has only 2 lanes). But right now we

[PATCH 3.14 01/17] crypto: hash - Fix page length clamping in hash walk

3.14-stable review patch. If anyone has any objections, please let me know. -- From: Herbert Xu commit 13f4bb78cf6a312bbdec367ba3da044b09bf0e29 upstream. The crypto hash walk code is broken when supplied with an offset greater than or equal to PAGE_SIZE. This patch fixes it

[PATCH 3.14 08/17] decnet: Do not build routes to devices without decnet private data.

3.14-stable review patch. If anyone has any objections, please let me know. -- From: "David S. Miller" [ Upstream commit a36a0d4008488fa545c74445d69eaf56377d5d4e ] In particular, make sure we check for decnet private presence for loopback devices. Signed-off-by: David S.

Re: [PATCH v5 08/12] zsmalloc: introduce zspage structure

On Mon, May 16, 2016 at 12:09:41PM +0900, Sergey Senozhatsky wrote: > On (05/09/16 11:20), Minchan Kim wrote: > > We have squeezed meta data of zspage into first page's descriptor. > > So, to get meta data from subpage, we should get first page first > > of all. But it makes trouble to implment

Re: [PATCH v5 08/12] zsmalloc: introduce zspage structure

On Mon, May 16, 2016 at 12:09:41PM +0900, Sergey Senozhatsky wrote: > On (05/09/16 11:20), Minchan Kim wrote: > > We have squeezed meta data of zspage into first page's descriptor. > > So, to get meta data from subpage, we should get first page first > > of all. But it makes trouble to implment

Re: [RFC][PATCH 0/7] locking/rwsem: Convert rwsem count to atomic_long_t

On Mon, May 16, 2016 at 5:37 PM, Jason Low wrote: > > This rest of the series converts the rwsem count variable to an atomic_long_t > since it is used it as an atomic variable. This allows us to also remove > the rwsem_atomic_{add,update} abstraction and reduce 100+ lines of

Re: [RFC][PATCH 0/7] locking/rwsem: Convert rwsem count to atomic_long_t

On Mon, May 16, 2016 at 5:37 PM, Jason Low wrote: > > This rest of the series converts the rwsem count variable to an atomic_long_t > since it is used it as an atomic variable. This allows us to also remove > the rwsem_atomic_{add,update} abstraction and reduce 100+ lines of code. I would

Re: [PATCH 02/11] mtd: nand_bbt: introduce BBT related data structure

Hi Boris, Firstly, sorry for late reply. On Thu, May 5, 2016 at 4:33 AM, Boris Brezillon wrote: > Hi Peter, > > On Wed, 4 May 2016 09:36:05 +0800 > Peter Pan wrote: > >> Hi Boris, >> >> On Tue, Apr 19, 2016 at 3:34 PM, Boris Brezillon

Re: [PATCH 02/11] mtd: nand_bbt: introduce BBT related data structure

Hi Boris, Firstly, sorry for late reply. On Thu, May 5, 2016 at 4:33 AM, Boris Brezillon wrote: > Hi Peter, > > On Wed, 4 May 2016 09:36:05 +0800 > Peter Pan wrote: > >> Hi Boris, >> >> On Tue, Apr 19, 2016 at 3:34 PM, Boris Brezillon >> wrote: >> > Hi Peter, >> > >> > On Tue, 19 Apr 2016

Re: [PATCH v5 07/12] zsmalloc: factor page chain functionality out

On Mon, May 16, 2016 at 11:14:20AM +0900, Sergey Senozhatsky wrote: > On (05/09/16 11:20), Minchan Kim wrote: > > For page migration, we need to create page chain of zspage dynamically > > so this patch factors it out from alloc_zspage. > > > > Cc: Sergey Senozhatsky

Re: [PATCH v5 07/12] zsmalloc: factor page chain functionality out

On Mon, May 16, 2016 at 11:14:20AM +0900, Sergey Senozhatsky wrote: > On (05/09/16 11:20), Minchan Kim wrote: > > For page migration, we need to create page chain of zspage dynamically > > so this patch factors it out from alloc_zspage. > > > > Cc: Sergey Senozhatsky > > Signed-off-by: Minchan

Re: [rcu_sched stall] regression/miss-config ?

On Mon, May 16, 2016 at 12:49:41PM -0700, Santosh Shilimkar wrote: > On 5/16/2016 10:34 AM, Paul E. McKenney wrote: > >On Mon, May 16, 2016 at 09:33:57AM -0700, Santosh Shilimkar wrote: > >>On 5/16/2016 5:03 AM, Paul E. McKenney wrote: > >>>On Sun, May 15, 2016 at 09:35:40PM -0700,

Re: [rcu_sched stall] regression/miss-config ?

On Mon, May 16, 2016 at 12:49:41PM -0700, Santosh Shilimkar wrote: > On 5/16/2016 10:34 AM, Paul E. McKenney wrote: > >On Mon, May 16, 2016 at 09:33:57AM -0700, Santosh Shilimkar wrote: > >>On 5/16/2016 5:03 AM, Paul E. McKenney wrote: > >>>On Sun, May 15, 2016 at 09:35:40PM -0700,

[RFC][PATCH 7/7] locking,asm-generic: Remove generic rwsem add and rwsem update definitions

The rwsem count has been converted to an atomic variable and we now directly use atomic_long_add() and atomic_long_add_return() on the count, so we can remove the asm-generic implementation of rwsem_atomic_add() and rwsem_atomic_update(). Signed-off-by: Jason Low ---

[RFC][PATCH 7/7] locking,asm-generic: Remove generic rwsem add and rwsem update definitions

The rwsem count has been converted to an atomic variable and we now directly use atomic_long_add() and atomic_long_add_return() on the count, so we can remove the asm-generic implementation of rwsem_atomic_add() and rwsem_atomic_update(). Signed-off-by: Jason Low --- include/asm-generic/rwsem.h

[RFC][PATCH 6/7] locking,s390: Remove s390 rwsem add and rwsem update

The rwsem count has been converted to an atomic variable and the rwsem code now directly uses atomic_long_add() and atomic_long_add_return(), so we can remove the s390 implementation of rwsem_atomic_add() and rwsem_atomic_update(). Signed-off-by: Jason Low ---

[RFC][PATCH 6/7] locking,s390: Remove s390 rwsem add and rwsem update

The rwsem count has been converted to an atomic variable and the rwsem code now directly uses atomic_long_add() and atomic_long_add_return(), so we can remove the s390 implementation of rwsem_atomic_add() and rwsem_atomic_update(). Signed-off-by: Jason Low --- arch/s390/include/asm/rwsem.h | 37

[RFC][PATCH 3/7] locking,x86: Remove x86 rwsem add and rwsem update

The rwsem count has been converted to an atomic variable and the rwsem code now directly uses atomic_long_add() and atomic_long_add_return(), so we can remove the x86 implementation of rwsem_atomic_add() and rwsem_atomic_update(). Signed-off-by: Jason Low ---

[RFC][PATCH 4/7] locking,alpha: Remove Alpha rwsem add and rwsem update

The rwsem count has been converted to an atomic variable and the rwsem code now directly uses atomic_long_add() and atomic_long_add_return(), so we can remove the alpha implementation of rwsem_atomic_add() and rwsem_atomic_update(). Signed-off-by: Jason Low ---

[RFC][PATCH 5/7] locking,ia64: Remove ia64 rwsem add and rwsem update

The rwsem count has been converted to an atomic variable and the rwsem code now directly uses atomic_long_add() and atomic_long_add_return(), so we can remove the ia64 implementation of rwsem_atomic_add() and rwsem_atomic_update(). Signed-off-by: Jason Low ---

[RFC][PATCH 3/7] locking,x86: Remove x86 rwsem add and rwsem update

The rwsem count has been converted to an atomic variable and the rwsem code now directly uses atomic_long_add() and atomic_long_add_return(), so we can remove the x86 implementation of rwsem_atomic_add() and rwsem_atomic_update(). Signed-off-by: Jason Low --- arch/x86/include/asm/rwsem.h | 18

[RFC][PATCH 4/7] locking,alpha: Remove Alpha rwsem add and rwsem update

The rwsem count has been converted to an atomic variable and the rwsem code now directly uses atomic_long_add() and atomic_long_add_return(), so we can remove the alpha implementation of rwsem_atomic_add() and rwsem_atomic_update(). Signed-off-by: Jason Low --- arch/alpha/include/asm/rwsem.h |

[RFC][PATCH 5/7] locking,ia64: Remove ia64 rwsem add and rwsem update

The rwsem count has been converted to an atomic variable and the rwsem code now directly uses atomic_long_add() and atomic_long_add_return(), so we can remove the ia64 implementation of rwsem_atomic_add() and rwsem_atomic_update(). Signed-off-by: Jason Low --- arch/ia64/include/asm/rwsem.h | 7

[RFC][PATCH 2/7] locking/rwsem: Convert sem->count to atomic_long_t

Convert the rwsem count variable to an atomic_long_t since we use it as an atomic variable. This also allows us to remove the rwsem_atomic_{add,update} "abstraction" which would now be an unnecesary level of indirection. In follow up patches, we also remove the rwsem_atomic_{add,update}

[RFC][PATCH 1/7] locking/rwsem: Optimize write lock by reducing operations in slowpath

When acquiring the rwsem write lock in the slowpath, we first try to set count to RWSEM_WAITING_BIAS. When that is successful, we then atomically add the RWSEM_WAITING_BIAS in cases where there are other tasks on the wait list. This causes write lock operations to often issue multiple atomic

[RFC][PATCH 2/7] locking/rwsem: Convert sem->count to atomic_long_t

Convert the rwsem count variable to an atomic_long_t since we use it as an atomic variable. This also allows us to remove the rwsem_atomic_{add,update} "abstraction" which would now be an unnecesary level of indirection. In follow up patches, we also remove the rwsem_atomic_{add,update}

[RFC][PATCH 1/7] locking/rwsem: Optimize write lock by reducing operations in slowpath

When acquiring the rwsem write lock in the slowpath, we first try to set count to RWSEM_WAITING_BIAS. When that is successful, we then atomically add the RWSEM_WAITING_BIAS in cases where there are other tasks on the wait list. This causes write lock operations to often issue multiple atomic

[RFC][PATCH 0/7] locking/rwsem: Convert rwsem count to atomic_long_t

The first patch contains an optimization for acquiring the rwsem write lock in the slowpath. This rest of the series converts the rwsem count variable to an atomic_long_t since it is used it as an atomic variable. This allows us to also remove the rwsem_atomic_{add,update} abstraction and reduce

[RFC][PATCH 0/7] locking/rwsem: Convert rwsem count to atomic_long_t

The first patch contains an optimization for acquiring the rwsem write lock in the slowpath. This rest of the series converts the rwsem count variable to an atomic_long_t since it is used it as an atomic variable. This allows us to also remove the rwsem_atomic_{add,update} abstraction and reduce

RE: [PATCH v2 0/4] ACPI 2.0: Enable TermList interpretion for table loading

Hi, Rafael Can we queue this up in linux-next? ASLTS recursive tests are done in ACPICA upstream and no regressions can be seen. We need more tests around this experimental change from the real users to have the chances to learn the unknown cases. If they reported regressions, we could stop the

RE: [PATCH v2 0/4] ACPI 2.0: Enable TermList interpretion for table loading

Hi, Rafael Can we queue this up in linux-next? ASLTS recursive tests are done in ACPICA upstream and no regressions can be seen. We need more tests around this experimental change from the real users to have the chances to learn the unknown cases. If they reported regressions, we could stop the

linux-next: manual merge of the net-next tree with the arm64 tree

Hi all, Today's linux-next merge of the net-next tree got a conflict in: arch/arm64/Kconfig between commit: 8ee708792e1c ("arm64: Kconfig: remove redundant HAVE_ARCH_TRANSPARENT_HUGEPAGE definition") from the arm64 tree and commit: 606b5908 ("bpf: split HAVE_BPF_JIT into cBPF and

linux-next: manual merge of the net-next tree with the arm64 tree

Hi all, Today's linux-next merge of the net-next tree got a conflict in: arch/arm64/Kconfig between commit: 8ee708792e1c ("arm64: Kconfig: remove redundant HAVE_ARCH_TRANSPARENT_HUGEPAGE definition") from the arm64 tree and commit: 606b5908 ("bpf: split HAVE_BPF_JIT into cBPF and

linux-next: manual merge of the vfs tree with the ext4 tree

Hi all, Today's linux-next merge of the vfs tree got conflicts in: fs/ext4/ext4.h fs/ext4/indirect.c fs/ext4/inode.c between commit: 914f82a32d02 ("ext4: refactor direct IO code") from the ext4 tree and commit: c8b8e32d700f ("direct-io: eliminate the offset argument to

linux-next: manual merge of the vfs tree with the ext4 tree

Hi all, Today's linux-next merge of the vfs tree got conflicts in: fs/ext4/ext4.h fs/ext4/indirect.c fs/ext4/inode.c between commit: 914f82a32d02 ("ext4: refactor direct IO code") from the ext4 tree and commit: c8b8e32d700f ("direct-io: eliminate the offset argument to

Re: [REGRESSION] asix: Lots of asix_rx_fixup() errors and slow transmissions

On Wed, May 11, 2016 at 3:00 PM, Dean Jenkins wrote: > > Your observations are consistent with missing URBs from the USB host > controller. > > Here is a summary of what I think is happening in your case: > > Good case: > URB #1: 1514 octets of 1514 Ethernet frame (A) >

Re: [REGRESSION] asix: Lots of asix_rx_fixup() errors and slow transmissions

On Wed, May 11, 2016 at 3:00 PM, Dean Jenkins wrote: > > Your observations are consistent with missing URBs from the USB host > controller. > > Here is a summary of what I think is happening in your case: > > Good case: > URB #1: 1514 octets of 1514 Ethernet frame (A) > URB #2: 1514 octets of

Re: [PATCH v2 0/8] crypto: caam - add support for LS1043A SoC

On Mon, May 16, 2016 at 03:49:27PM +, Horia Ioan Geanta Neag wrote: > > I assume it's too late for 4.7, however applying the patches would solve > dependencies b/w on-going caam development. I will be merging this after the merge window is closed. Cheers, -- Email: Herbert Xu

Re: [PATCH v2 0/8] crypto: caam - add support for LS1043A SoC

On Mon, May 16, 2016 at 03:49:27PM +, Horia Ioan Geanta Neag wrote: > > I assume it's too late for 4.7, however applying the patches would solve > dependencies b/w on-going caam development. I will be merging this after the merge window is closed. Cheers, -- Email: Herbert Xu Home Page:

[PATCH v2 net-next] bpf: arm64: remove callee-save registers use for tmp registers

In the current implementation of ARM64 eBPF JIT, R23 and R24 are used for tmp registers, which are callee-saved registers. This leads to variable size of JIT prologue and epilogue. The latest blinding constant change prefers to constant size of prologue and epilogue. AAPCS reserves R9 ~ R15 for

[PATCH v2 net-next] bpf: arm64: remove callee-save registers use for tmp registers

In the current implementation of ARM64 eBPF JIT, R23 and R24 are used for tmp registers, which are callee-saved registers. This leads to variable size of JIT prologue and epilogue. The latest blinding constant change prefers to constant size of prologue and epilogue. AAPCS reserves R9 ~ R15 for

CAN I TRUST YOU?

Dear Beneficiary I am Peter Douglas Director Inspection Unit United Nations Inspection Agent in Hartsfield–Jackson Atlanta International Airport Atlanta GA. We are rounding up for the last Quater of the auditing, all abandom Consignment in US Airports are being transfer to our facilities here

CAN I TRUST YOU?

Dear Beneficiary I am Peter Douglas Director Inspection Unit United Nations Inspection Agent in Hartsfield–Jackson Atlanta International Airport Atlanta GA. We are rounding up for the last Quater of the auditing, all abandom Consignment in US Airports are being transfer to our facilities here

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