[PATCH 3.18 172/185] PCI: Add function 1 DMA alias quirk for Marvell 88SE9220

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Thomas Vincent-Cross [ Upstream commit 832e4e1f76b8a84991e9db56fdcef1ebce839b8b ] Add Marvell 88SE9220 DMA quirk as found and tested on bug 42679. Link:

[PATCH 3.18 185/185] kdb: make "mdr" command repeat

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Randy Dunlap [ Upstream commit 1e0ce03bf142454f38a5fc050bf4fd698d2d36d8 ] The "mdr" command should repeat (continue) when only Enter/Return is pressed, so make it do so. Signed-off-by: Randy

Re: [PATCH] mtd: nand: raw: atmel: add module param to avoid using dma

On Mon, 28 May 2018 17:52:53 +0200 Peter Rosin wrote: > On 2018-05-28 16:27, Boris Brezillon wrote: > > Hi Peter, > > > > On Mon, 28 May 2018 12:10:02 +0200 > > Peter Rosin wrote: > > > >> On 2018-05-28 00:11, Peter Rosin wrote: > >>> On 2018-05-27 11:18,

Re: [PATCH] mtd: nand: raw: atmel: add module param to avoid using dma

On Mon, 28 May 2018 17:52:53 +0200 Peter Rosin wrote: > On 2018-05-28 16:27, Boris Brezillon wrote: > > Hi Peter, > > > > On Mon, 28 May 2018 12:10:02 +0200 > > Peter Rosin wrote: > > > >> On 2018-05-28 00:11, Peter Rosin wrote: > >>> On 2018-05-27 11:18, Peter Rosin wrote: > On

[PATCH 3.18 174/185] media: cx25821: prevent out-of-bounds read on array card

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Colin Ian King [ Upstream commit 67300abdbe9f1717532aaf4e037222762716d0f6 ] Currently an out of range dev->nr is detected by just reporting the issue and later on an

[PATCH 3.18 174/185] media: cx25821: prevent out-of-bounds read on array card

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Colin Ian King [ Upstream commit 67300abdbe9f1717532aaf4e037222762716d0f6 ] Currently an out of range dev->nr is detected by just reporting the issue and later on an out-of-bounds read on

[PATCH 3.18 176/185] clk: samsung: exynos5260: Fix PLL rates

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Andrzej Hajda [ Upstream commit cdb68fbd4e7962be742c4f29475220c5bf28d8a5 ] Rates declared in PLL rate tables should match exactly rates calculated from the PLL

[PATCH 3.18 176/185] clk: samsung: exynos5260: Fix PLL rates

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Andrzej Hajda [ Upstream commit cdb68fbd4e7962be742c4f29475220c5bf28d8a5 ] Rates declared in PLL rate tables should match exactly rates calculated from the PLL coefficients. If that is not

[PATCH 3.18 178/185] clk: samsung: exynos3250: Fix PLL rates

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Andrzej Hajda [ Upstream commit a8321e7887410a2b2e80ab89d1ef7b30562658ea ] Rates declared in PLL rate tables should match exactly rates calculated from PLL coefficients.

[PATCH 3.18 178/185] clk: samsung: exynos3250: Fix PLL rates

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Andrzej Hajda [ Upstream commit a8321e7887410a2b2e80ab89d1ef7b30562658ea ] Rates declared in PLL rate tables should match exactly rates calculated from PLL coefficients. If that is not the

[PATCH 3.18 175/185] clk: samsung: s3c2410: Fix PLL rates

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Andrzej Hajda [ Upstream commit 179db533c08431f509a3823077549773d519358b ] Rates declared in PLL rate tables should match exactly rates calculated from the PLL

[PATCH 3.18 175/185] clk: samsung: s3c2410: Fix PLL rates

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Andrzej Hajda [ Upstream commit 179db533c08431f509a3823077549773d519358b ] Rates declared in PLL rate tables should match exactly rates calculated from the PLL coefficients. If that is not

Re: [PATCH v2 4/6] clk: tegra20: init NDFLASH clock to sensible rate

Am Montag, den 28.05.2018, 17:53 +0200 schrieb Stefan Agner: > On 28.05.2018 09:55, Peter De Schrijver wrote: > > On Sun, May 27, 2018 at 11:54:40PM +0200, Stefan Agner wrote: > > > From: Lucas Stach > > > > > > Set up the NAND Flash controller clock to run at 150MHz > > >

Re: [PATCH 1/6] lib/rhashtable: convert param sanitations to WARN_ON

On Mon, 28 May 2018, Herbert Xu wrote: On Mon, May 28, 2018 at 06:12:09AM -0700, Davidlohr Bueso wrote: Well, I don't really _want_ them; nor does the ipc code which already does a WARN_ON() (but that goes away in future patches). What I want is to get rid of the return path. So I don't

Re: [PATCH 1/6] lib/rhashtable: convert param sanitations to WARN_ON

On Mon, 28 May 2018, Herbert Xu wrote: On Mon, May 28, 2018 at 06:12:09AM -0700, Davidlohr Bueso wrote: Well, I don't really _want_ them; nor does the ipc code which already does a WARN_ON() (but that goes away in future patches). What I want is to get rid of the return path. So I don't

Re: [PATCH v2 4/6] clk: tegra20: init NDFLASH clock to sensible rate

Am Montag, den 28.05.2018, 17:53 +0200 schrieb Stefan Agner: > On 28.05.2018 09:55, Peter De Schrijver wrote: > > On Sun, May 27, 2018 at 11:54:40PM +0200, Stefan Agner wrote: > > > From: Lucas Stach > > > > > > Set up the NAND Flash controller clock to run at 150MHz > > > instead of the rate

[PATCH 4.4 002/268] MIPS: Fix ptrace(2) PTRACE_PEEKUSR and PTRACE_POKEUSR accesses to o32 FGRs

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Maciej W. Rozycki commit 9a3a92ccfe3620743d4ae57c987dc8e9c5f88996 upstream. Check the TIF_32BIT_FPREGS task setting of the tracee rather than the tracer in determining the

[PATCH 4.4 002/268] MIPS: Fix ptrace(2) PTRACE_PEEKUSR and PTRACE_POKEUSR accesses to o32 FGRs

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Maciej W. Rozycki commit 9a3a92ccfe3620743d4ae57c987dc8e9c5f88996 upstream. Check the TIF_32BIT_FPREGS task setting of the tracee rather than the tracer in determining the layout of

[PATCH 4.4 001/268] MIPS: ptrace: Expose FIR register through FP regset

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Maciej W. Rozycki commit 71e909c0cdad28a1df1fa14442929e68615dee45 upstream. Correct commit 7aeb753b5353 ("MIPS: Implement task_user_regset_view.") and expose the FIR register

[PATCH 4.4 001/268] MIPS: ptrace: Expose FIR register through FP regset

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Maciej W. Rozycki commit 71e909c0cdad28a1df1fa14442929e68615dee45 upstream. Correct commit 7aeb753b5353 ("MIPS: Implement task_user_regset_view.") and expose the FIR register using the unused

[PATCH 4.4 003/268] KVM: Fix spelling mistake: "cop_unsuable" -> "cop_unusable"

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Colin Ian King commit ba3696e94d9d590d9a7e55f68e81c25dba515191 upstream. Trivial fix to spelling mistake in debugfs_entries text. Fixes: 669e846e6c4e ("KVM/MIPS32:

[PATCH 4.4 003/268] KVM: Fix spelling mistake: "cop_unsuable" -> "cop_unusable"

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Colin Ian King commit ba3696e94d9d590d9a7e55f68e81c25dba515191 upstream. Trivial fix to spelling mistake in debugfs_entries text. Fixes: 669e846e6c4e ("KVM/MIPS32: MIPS arch specific APIs for

[PATCH 3.18 179/185] audit: return on memory error to avoid null pointer dereference

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Richard Guy Briggs [ Upstream commit 23138ead270045f1b3e912e667967b6094244999 ] If there is a memory allocation error when trying to change an audit kernel feature value, the

[PATCH 3.18 179/185] audit: return on memory error to avoid null pointer dereference

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Richard Guy Briggs [ Upstream commit 23138ead270045f1b3e912e667967b6094244999 ] If there is a memory allocation error when trying to change an audit kernel feature value, the ignored

[PATCH 4.4 016/268] xfs: remove racy hasattr check from attr ops

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Brian Foster commit 5a93790d4e2df73e30c965ec6e49be82fc3ccfce upstream. xfs_attr_[get|remove]() have unlocked attribute fork checks to optimize away a lock cycle in cases

[PATCH 4.4 016/268] xfs: remove racy hasattr check from attr ops

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Brian Foster commit 5a93790d4e2df73e30c965ec6e49be82fc3ccfce upstream. xfs_attr_[get|remove]() have unlocked attribute fork checks to optimize away a lock cycle in cases where the fork does

[PATCH 4.4 007/268] mmc: sdhci-iproc: fix 32bit writes for TRANSFER_MODE register

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Corneliu Doban commit 5f651b870485ee60f5abbbd85195a6852978894a upstream. When the host controller accepts only 32bit writes, the value of the 16bit TRANSFER_MODE

[PATCH 4.4 007/268] mmc: sdhci-iproc: fix 32bit writes for TRANSFER_MODE register

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Corneliu Doban commit 5f651b870485ee60f5abbbd85195a6852978894a upstream. When the host controller accepts only 32bit writes, the value of the 16bit TRANSFER_MODE register, that has the same

[PATCH 4.4 019/268] NFSv4: always set NFS_LOCK_LOST when a lock is lost.

4.4-stable review patch. If anyone has any objections, please let me know. -- From: NeilBrown [ Upstream commit dce2630c7da73b0634686bca557cc8945cc450c8 ] There are 2 comments in the NFSv4 code which suggest that SIGLOST should possibly be sent to a process.

[PATCH 4.4 019/268] NFSv4: always set NFS_LOCK_LOST when a lock is lost.

4.4-stable review patch. If anyone has any objections, please let me know. -- From: NeilBrown [ Upstream commit dce2630c7da73b0634686bca557cc8945cc450c8 ] There are 2 comments in the NFSv4 code which suggest that SIGLOST should possibly be sent to a process. In these cases a

Re: [PATCH 4.14 000/496] 4.14.45-stable review

On Mon, May 28, 2018 at 11:56:25AM +0200, Greg Kroah-Hartman wrote: > This is the start of the stable review cycle for the 4.14.45 release. > There are 496 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

Re: [PATCH 4.14 000/496] 4.14.45-stable review

On Mon, May 28, 2018 at 11:56:25AM +0200, Greg Kroah-Hartman wrote: > This is the start of the stable review cycle for the 4.14.45 release. > There are 496 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

[PATCH 4.4 024/268] PCI: Add function 1 DMA alias quirk for Marvell 9128

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Alex Williamson [ Upstream commit aa008206634363ef800fbd5f0262016c9ff81dea ] The Marvell 9128 is the original device generating bug 42679, from which many other

[PATCH 4.4 024/268] PCI: Add function 1 DMA alias quirk for Marvell 9128

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Alex Williamson [ Upstream commit aa008206634363ef800fbd5f0262016c9ff81dea ] The Marvell 9128 is the original device generating bug 42679, from which many other Marvell DMA alias quirks have

Re: [rfc patch] mm, oom: fix unnecessary killing of additional processes

On Fri 25-05-18 12:36:08, David Rientjes wrote: > On Fri, 25 May 2018, Michal Hocko wrote: > > > > The oom reaper ensures forward progress by setting MMF_OOM_SKIP itself if > > > it cannot reap an mm. This can happen for a variety of reasons, > > > including: > > > > > > - the inability to

Re: [rfc patch] mm, oom: fix unnecessary killing of additional processes

On Fri 25-05-18 12:36:08, David Rientjes wrote: > On Fri, 25 May 2018, Michal Hocko wrote: > > > > The oom reaper ensures forward progress by setting MMF_OOM_SKIP itself if > > > it cannot reap an mm. This can happen for a variety of reasons, > > > including: > > > > > > - the inability to

Re: [PATCH][next] ALSA: xen-front: remove redundant error check on ret

On Mon, 28 May 2018 00:42:12 +0200, Takashi Sakamoto wrote: > > Hi, > > On May 28 2018 06:23, Colin King wrote: > > From: Colin Ian King > > > > The error for a -ve value in ret is redundant as all previous > > assignments to ret have an associated -ve check and hence

Re: [PATCH][next] ALSA: xen-front: remove redundant error check on ret

On Mon, 28 May 2018 00:42:12 +0200, Takashi Sakamoto wrote: > > Hi, > > On May 28 2018 06:23, Colin King wrote: > > From: Colin Ian King > > > > The error for a -ve value in ret is redundant as all previous > > assignments to ret have an associated -ve check and hence it > > is impossible for

Re: [PATCH] doc: document scope NOFS, NOIO APIs

On 05/25/2018 09:52 AM, Michal Hocko wrote: > On Thu 24-05-18 09:37:18, Randy Dunlap wrote: >> On 05/24/2018 04:43 AM, Michal Hocko wrote: > [...] >>> +The traditional way to avoid this deadlock problem is to clear __GFP_FS >>> +resp. __GFP_IO (note the later implies clearing the first as well) in

Re: [PATCH] doc: document scope NOFS, NOIO APIs

On 05/25/2018 09:52 AM, Michal Hocko wrote: > On Thu 24-05-18 09:37:18, Randy Dunlap wrote: >> On 05/24/2018 04:43 AM, Michal Hocko wrote: > [...] >>> +The traditional way to avoid this deadlock problem is to clear __GFP_FS >>> +resp. __GFP_IO (note the later implies clearing the first as well) in

Re: [RFC PATCH 1/5] mm, slab/slub: introduce kmalloc-reclaimable caches

On 05/25/2018 05:51 PM, Christopher Lameter wrote: > On Thu, 24 May 2018, Vlastimil Babka wrote: > >> diff --git a/include/linux/slab.h b/include/linux/slab.h >> index 9ebe659bd4a5..5bff0571b360 100644 >> --- a/include/linux/slab.h >> +++ b/include/linux/slab.h >> @@ -296,11 +296,16 @@ static

Re: [RFC PATCH 1/5] mm, slab/slub: introduce kmalloc-reclaimable caches

On 05/25/2018 05:51 PM, Christopher Lameter wrote: > On Thu, 24 May 2018, Vlastimil Babka wrote: > >> diff --git a/include/linux/slab.h b/include/linux/slab.h >> index 9ebe659bd4a5..5bff0571b360 100644 >> --- a/include/linux/slab.h >> +++ b/include/linux/slab.h >> @@ -296,11 +296,16 @@ static

[PATCH 4.4 008/268] libata: Blacklist some Sandisk SSDs for NCQ

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Tejun Heo commit 322579dcc865b94b47345ad1b6002ad167f85405 upstream. Sandisk SSDs SD7SN6S256G and SD8SN8U256G are regularly locking up regularly under sustained moderate load

Re: [PATCH] doc: document scope NOFS, NOIO APIs

On Mon 28-05-18 09:48:54, Dave Chinner wrote: > On Fri, May 25, 2018 at 10:16:24AM +0200, Michal Hocko wrote: > > On Fri 25-05-18 08:17:15, Dave Chinner wrote: > > > On Thu, May 24, 2018 at 01:43:41PM +0200, Michal Hocko wrote: > > [...] > > > > +FS/IO code then simply calls the appropriate save

[PATCH 4.4 021/268] ASoC: au1x: Fix timeout tests in au1xac97c_ac97_read()

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Dan Carpenter [ Upstream commit 123af9043e93cb6f235207d260d50f832cdb5439 ] The loop timeout doesn't work because it's a post op and ends with "tmo" set to -1. I

Re: [PATCH] doc: document scope NOFS, NOIO APIs

On Mon 28-05-18 09:48:54, Dave Chinner wrote: > On Fri, May 25, 2018 at 10:16:24AM +0200, Michal Hocko wrote: > > On Fri 25-05-18 08:17:15, Dave Chinner wrote: > > > On Thu, May 24, 2018 at 01:43:41PM +0200, Michal Hocko wrote: > > [...] > > > > +FS/IO code then simply calls the appropriate save

[PATCH 4.4 021/268] ASoC: au1x: Fix timeout tests in au1xac97c_ac97_read()

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Dan Carpenter [ Upstream commit 123af9043e93cb6f235207d260d50f832cdb5439 ] The loop timeout doesn't work because it's a post op and ends with "tmo" set to -1. I changed it from a post-op to a

[PATCH 4.4 008/268] libata: Blacklist some Sandisk SSDs for NCQ

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Tejun Heo commit 322579dcc865b94b47345ad1b6002ad167f85405 upstream. Sandisk SSDs SD7SN6S256G and SD8SN8U256G are regularly locking up regularly under sustained moderate load with NCQ enabled.

[PATCH 4.4 023/268] tracing/hrtimer: Fix tracing bugs by taking all clock bases and modes into account

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Anna-Maria Gleixner [ Upstream commit 91633eed73a3ac37aaece5c8c1f93a18bae616a9 ] So far only CLOCK_MONOTONIC and CLOCK_REALTIME were taken into account as well as

[PATCH 4.4 026/268] perf callchain: Fix attr.sample_max_stack setting

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Arnaldo Carvalho de Melo [ Upstream commit 249d98e567e25dd03e015e2d31e1b7b9648f34df ] When setting the "dwarf" unwinder for a specific event and not specifying the max-stack,

[PATCH 4.4 023/268] tracing/hrtimer: Fix tracing bugs by taking all clock bases and modes into account

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Anna-Maria Gleixner [ Upstream commit 91633eed73a3ac37aaece5c8c1f93a18bae616a9 ] So far only CLOCK_MONOTONIC and CLOCK_REALTIME were taken into account as well as HRTIMER_MODE_ABS/REL in the

[PATCH 4.4 026/268] perf callchain: Fix attr.sample_max_stack setting

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Arnaldo Carvalho de Melo [ Upstream commit 249d98e567e25dd03e015e2d31e1b7b9648f34df ] When setting the "dwarf" unwinder for a specific event and not specifying the max-stack, the

[PATCH 4.4 027/268] tools lib traceevent: Fix get_field_str() for dynamic strings

4.4-stable review patch. If anyone has any objections, please let me know. -- From: "Steven Rostedt (VMware)" [ Upstream commit d777f8de99b05d399c0e4e51cdce016f26bd971b ] If a field is a dynamic string, get_field_str() returned just the offset/size value

[PATCH 4.4 027/268] tools lib traceevent: Fix get_field_str() for dynamic strings

4.4-stable review patch. If anyone has any objections, please let me know. -- From: "Steven Rostedt (VMware)" [ Upstream commit d777f8de99b05d399c0e4e51cdce016f26bd971b ] If a field is a dynamic string, get_field_str() returned just the offset/size value and not the string.

[PATCH 4.4 020/268] ALSA: hda - Use IS_REACHABLE() for dependency on input

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Takashi Iwai [ Upstream commit c469652bb5e8fb715db7d152f46d33b3740c9b87 ] The commit ffcd28d88e4f ("ALSA: hda - Select INPUT for Realtek HD-audio codec") introduced the

[PATCH 4.4 028/268] dm thin: fix documentation relative to low water mark threshold

4.4-stable review patch. If anyone has any objections, please let me know. -- From: mulhern [ Upstream commit 9b28a1102efc75d81298198166ead87d643a29ce ] Fixes: 1. The use of "exceeds" when the opposite of exceeds, falls below, was meant. 2. Properly

[PATCH 4.4 028/268] dm thin: fix documentation relative to low water mark threshold

4.4-stable review patch. If anyone has any objections, please let me know. -- From: mulhern [ Upstream commit 9b28a1102efc75d81298198166ead87d643a29ce ] Fixes: 1. The use of "exceeds" when the opposite of exceeds, falls below, was meant. 2. Properly speaking, a table can not

[PATCH 4.4 020/268] ALSA: hda - Use IS_REACHABLE() for dependency on input

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Takashi Iwai [ Upstream commit c469652bb5e8fb715db7d152f46d33b3740c9b87 ] The commit ffcd28d88e4f ("ALSA: hda - Select INPUT for Realtek HD-audio codec") introduced the reverse-selection of

[PATCH 4.4 032/268] kconfig: Fix automatic menu creation mem leak

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Ulf Magnusson [ Upstream commit ae7440ef0c8013d68c00dad6900e7cce5311bb1c ] expr_trans_compare() always allocates and returns a new expression, giving the following leak

[PATCH 4.4 032/268] kconfig: Fix automatic menu creation mem leak

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Ulf Magnusson [ Upstream commit ae7440ef0c8013d68c00dad6900e7cce5311bb1c ] expr_trans_compare() always allocates and returns a new expression, giving the following leak outline: ...

[PATCH 4.4 034/268] mac80211_hwsim: fix possible memory leak in hwsim_new_radio_nl()

4.4-stable review patch. If anyone has any objections, please let me know. -- From: "weiyongjun (A)" [ Upstream commit 0ddcff49b672239dda94d70d0fcf50317a9f4b51 ] 'hwname' is malloced in hwsim_new_radio_nl() and should be freed before leaving from the

[PATCH 4.4 034/268] mac80211_hwsim: fix possible memory leak in hwsim_new_radio_nl()

4.4-stable review patch. If anyone has any objections, please let me know. -- From: "weiyongjun (A)" [ Upstream commit 0ddcff49b672239dda94d70d0fcf50317a9f4b51 ] 'hwname' is malloced in hwsim_new_radio_nl() and should be freed before leaving from the error handling cases,

[PATCH 4.4 029/268] nfs: Do not convert nfs_idmap_cache_timeout to jiffies

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Jan Chochol [ Upstream commit cbebc6ef4fc830f4040d4140bf53484812d5d5d9 ] Since commit 57e62324e469 ("NFS: Store the legacy idmapper result in the keyring")

[PATCH 4.4 029/268] nfs: Do not convert nfs_idmap_cache_timeout to jiffies

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Jan Chochol [ Upstream commit cbebc6ef4fc830f4040d4140bf53484812d5d5d9 ] Since commit 57e62324e469 ("NFS: Store the legacy idmapper result in the keyring") nfs_idmap_cache_timeout changed

[PATCH 4.4 037/268] btrfs: Fix out of bounds access in btrfs_search_slot

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Nikolay Borisov [ Upstream commit 9ea2c7c9da13c9073e371c046cbbc45481ecb459 ] When modifying a tree where the root is at BTRFS_MAX_LEVEL - 1 then the level variable is going

[PATCH 4.4 037/268] btrfs: Fix out of bounds access in btrfs_search_slot

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Nikolay Borisov [ Upstream commit 9ea2c7c9da13c9073e371c046cbbc45481ecb459 ] When modifying a tree where the root is at BTRFS_MAX_LEVEL - 1 then the level variable is going to be 7 (this is

[PATCH 4.4 036/268] Btrfs: set plug for fsync

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Liu Bo [ Upstream commit 343e4fc1c60971b0734de26dbbd475d433950982 ] Setting plug can merge adjacent IOs before dispatching IOs to the disk driver. Without plug, it'd not

[PATCH] ALSA: xen: ensure nul-terminated device name

gcc-8 warns that pcm_instance->name is not necessarily terminated correctly if the input is more than 80 characters long or lacks a termination byte itself: In function 'strncpy', inlined from 'cfg_device' at sound/xen/xen_snd_front_cfg.c:399:3, inlined from 'xen_snd_front_cfg_card' at

[PATCH 4.4 036/268] Btrfs: set plug for fsync

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Liu Bo [ Upstream commit 343e4fc1c60971b0734de26dbbd475d433950982 ] Setting plug can merge adjacent IOs before dispatching IOs to the disk driver. Without plug, it'd not be a problem for

[PATCH] ALSA: xen: ensure nul-terminated device name

gcc-8 warns that pcm_instance->name is not necessarily terminated correctly if the input is more than 80 characters long or lacks a termination byte itself: In function 'strncpy', inlined from 'cfg_device' at sound/xen/xen_snd_front_cfg.c:399:3, inlined from 'xen_snd_front_cfg_card' at

[PATCH 4.4 039/268] scsi: fas216: fix sense buffer initialization

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Arnd Bergmann [ Upstream commit 96d5eaa9bb74d299508d811d865c2c41b38b0301 ] While testing with the ARM specific memset() macro removed, I ran into a compiler warning that shows

[PATCH 4.4 039/268] scsi: fas216: fix sense buffer initialization

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Arnd Bergmann [ Upstream commit 96d5eaa9bb74d299508d811d865c2c41b38b0301 ] While testing with the ARM specific memset() macro removed, I ran into a compiler warning that shows an old bug:

RE: [patch v22 1/4] drivers: jtag: Add JTAG core driver

Hi Greg. Thanks for your review. Please see my comments inline. Best Regards, Oleksandr Shamray > -Original Message- > From: Greg KH [mailto:gre...@linuxfoundation.org] > Sent: 28 мая 2018 г. 15:35 > To: Oleksandr Shamray > Cc: a...@arndb.de;

RE: [patch v22 1/4] drivers: jtag: Add JTAG core driver

Hi Greg. Thanks for your review. Please see my comments inline. Best Regards, Oleksandr Shamray > -Original Message- > From: Greg KH [mailto:gre...@linuxfoundation.org] > Sent: 28 мая 2018 г. 15:35 > To: Oleksandr Shamray > Cc: a...@arndb.de; linux-kernel@vger.kernel.org; linux-arm- >

[PATCH 4.4 009/268] libata: blacklist Micron 500IT SSD with MU01 firmware

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Sudip Mukherjee commit 136d769e0b3475d71350aa3648a116a6ee7a8f6c upstream. While whitelisting Micron M500DC drives, the tweaked blacklist entry enabled queued TRIM

[PATCH 4.4 009/268] libata: blacklist Micron 500IT SSD with MU01 firmware

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Sudip Mukherjee commit 136d769e0b3475d71350aa3648a116a6ee7a8f6c upstream. While whitelisting Micron M500DC drives, the tweaked blacklist entry enabled queued TRIM from M500IT variants also.

Re: [PATCH 2/2] sched: Warn if we fail to migrate a task

Hi Peter, On Mon, May 28, 2018 at 05:06:56PM +0200, Peter Zijlstra wrote: > On Sat, May 26, 2018 at 08:46:48AM -0700, Paul Burton wrote: > > diff --git a/kernel/sched/core.c b/kernel/sched/core.c > > index 2380bc228dd0..cda3affd45b7 100644 > > --- a/kernel/sched/core.c > > +++

Re: [PATCH 2/2] sched: Warn if we fail to migrate a task

Hi Peter, On Mon, May 28, 2018 at 05:06:56PM +0200, Peter Zijlstra wrote: > On Sat, May 26, 2018 at 08:46:48AM -0700, Paul Burton wrote: > > diff --git a/kernel/sched/core.c b/kernel/sched/core.c > > index 2380bc228dd0..cda3affd45b7 100644 > > --- a/kernel/sched/core.c > > +++

[PATCH] platform: chrome: Add input dependency for tablet switch driver

Without CONFIG_INPUT, or with a modular input layer and built-in tablet driver, we get a link error: ERROR: "input_event" [drivers/platform/chrome/chromeos_tbmc.ko] undefined! ERROR: "input_register_device" [drivers/platform/chrome/chromeos_tbmc.ko] undefined! ERROR: "input_set_capability"

[PATCH] platform: chrome: Add input dependency for tablet switch driver

Without CONFIG_INPUT, or with a modular input layer and built-in tablet driver, we get a link error: ERROR: "input_event" [drivers/platform/chrome/chromeos_tbmc.ko] undefined! ERROR: "input_register_device" [drivers/platform/chrome/chromeos_tbmc.ko] undefined! ERROR: "input_set_capability"

Re: [patch] mm, hugetlb_cgroup: suppress SIGBUS when hugetlb_cgroup charge fails

On Fri 25-05-18 15:18:11, David Rientjes wrote: [...] > Let's see what Mike and Aneesh say, because they may object to using > VM_FAULT_OOM because there's no way to guarantee that we'll come under the > limit of hugetlb_cgroup as a result of the oom. My assumption is that we > use

Re: [patch] mm, hugetlb_cgroup: suppress SIGBUS when hugetlb_cgroup charge fails

On Fri 25-05-18 15:18:11, David Rientjes wrote: [...] > Let's see what Mike and Aneesh say, because they may object to using > VM_FAULT_OOM because there's no way to guarantee that we'll come under the > limit of hugetlb_cgroup as a result of the oom. My assumption is that we > use

[PATCH] media: marvel-ccic: mmp: select VIDEOBUF2_VMALLOC/DMA_CONTIG

Testing randconfig builds after the return of the mmp ccic driver shows a link error in some configurations: drivers/media/platform/marvell-ccic/mcam-core.o: In function `mccic_register': mcam-core.c:(.text+0x2e48): undefined reference to `vb2_dma_contig_memops' A closer look at the mcam-core.c

[PATCH] media: marvel-ccic: mmp: select VIDEOBUF2_VMALLOC/DMA_CONTIG

Testing randconfig builds after the return of the mmp ccic driver shows a link error in some configurations: drivers/media/platform/marvell-ccic/mcam-core.o: In function `mccic_register': mcam-core.c:(.text+0x2e48): undefined reference to `vb2_dma_contig_memops' A closer look at the mcam-core.c

Re: linux-next: Signed-off-by missing for commits in the rdma tree

On Sat, May 26, 2018 at 01:31:12PM +1000, Stephen Rothwell wrote: > Hi all, > > Commits > > 116aeb887371 ("iw_cxgb4: provide detailed provider-specific CM_ID > information") > to > 0252f73334f9 ("IB/qib: Fix DMA api warning with debug kernel") > > are missing a Signed-off-by from their

Re: linux-next: Signed-off-by missing for commits in the rdma tree

On Sat, May 26, 2018 at 01:31:12PM +1000, Stephen Rothwell wrote: > Hi all, > > Commits > > 116aeb887371 ("iw_cxgb4: provide detailed provider-specific CM_ID > information") > to > 0252f73334f9 ("IB/qib: Fix DMA api warning with debug kernel") > > are missing a Signed-off-by from their

[PATCH] dm: writecache: fix format string warning

The return type of ACCESS_ONCE is configuration dependent and may be either 'int' or 'long int' for the writecache_has_error() macro, so we get a warning like this for either format string: In file included from drivers/md/dm-writecache.c:8: drivers/md/dm-writecache.c: In function

[PATCH] dm: writecache: fix format string warning

The return type of ACCESS_ONCE is configuration dependent and may be either 'int' or 'long int' for the writecache_has_error() macro, so we get a warning like this for either format string: In file included from drivers/md/dm-writecache.c:8: drivers/md/dm-writecache.c: In function

Re: [PATCH 1/6] lib/rhashtable: convert param sanitations to WARN_ON

On Mon, May 28, 2018 at 06:12:09AM -0700, Davidlohr Bueso wrote: > > Well, I don't really _want_ them; nor does the ipc code which already > does a WARN_ON() (but that goes away in future patches). What I want > is to get rid of the return path. So I don't really care if we convert > them to WARN

Re: [PATCH 1/6] lib/rhashtable: convert param sanitations to WARN_ON

On Mon, May 28, 2018 at 06:12:09AM -0700, Davidlohr Bueso wrote: > > Well, I don't really _want_ them; nor does the ipc code which already > does a WARN_ON() (but that goes away in future patches). What I want > is to get rid of the return path. So I don't really care if we convert > them to WARN

Re: [RFC PATCH 0/5] kmalloc-reclaimable caches

On 05/24/2018 05:32 PM, Johannes Weiner wrote: > On Thu, May 24, 2018 at 01:00:06PM +0200, Vlastimil Babka wrote: >> - the vmstat/meminfo counter name is rather general and might suggest it also >> includes reclaimable page caches, which it doesn't >> >> Suggestions welcome for all three points.

Re: [RFC PATCH 0/5] kmalloc-reclaimable caches

On 05/24/2018 05:32 PM, Johannes Weiner wrote: > On Thu, May 24, 2018 at 01:00:06PM +0200, Vlastimil Babka wrote: >> - the vmstat/meminfo counter name is rather general and might suggest it also >> includes reclaimable page caches, which it doesn't >> >> Suggestions welcome for all three points.

[PATCH] ARM: tegra: fix compile-testing PCI host driver

The tegra_cpuidle_pcie_irqs_in_use() function is stubbed out for non-ARM builds, but now we can compile-test the Tegra pci driver on non-Tegra ARM platforms as well, which results in a new link error: drivers/pci/host/pci-tegra.o: In function `tegra_pcie_map_irq': pci-tegra.c:(.text+0x288):

[PATCH] ARM: tegra: fix compile-testing PCI host driver

The tegra_cpuidle_pcie_irqs_in_use() function is stubbed out for non-ARM builds, but now we can compile-test the Tegra pci driver on non-Tegra ARM platforms as well, which results in a new link error: drivers/pci/host/pci-tegra.o: In function `tegra_pcie_map_irq': pci-tegra.c:(.text+0x288):

[PATCH] Make elf2ecoff work on 64bit host machines

Use fixed width integer types for ecoff structs to make elf2ecoff work on 64bit host machines Signed-off-by: Thomas Bogendoerfer --- arch/mips/boot/ecoff.h | 58 +++--- arch/mips/boot/elf2ecoff.c | 29 +++ 2

Re: [PATCH] memcg: force charge kmem counter too

On Sat 26-05-18 15:37:05, Shakeel Butt wrote: > On Sat, May 26, 2018 at 11:51 AM, Vladimir Davydov > wrote: > > On Fri, May 25, 2018 at 11:55:01AM -0700, Shakeel Butt wrote: > >> Based on several conditions the kernel can decide to force charge an > >> allocation for a

[PATCH] Make elf2ecoff work on 64bit host machines

Use fixed width integer types for ecoff structs to make elf2ecoff work on 64bit host machines Signed-off-by: Thomas Bogendoerfer --- arch/mips/boot/ecoff.h | 58 +++--- arch/mips/boot/elf2ecoff.c | 29 +++ 2 files changed, 43

Re: [PATCH] memcg: force charge kmem counter too

On Sat 26-05-18 15:37:05, Shakeel Butt wrote: > On Sat, May 26, 2018 at 11:51 AM, Vladimir Davydov > wrote: > > On Fri, May 25, 2018 at 11:55:01AM -0700, Shakeel Butt wrote: > >> Based on several conditions the kernel can decide to force charge an > >> allocation for a memcg i.e. overcharge

Re: [PATCH] printk/nmi: Prevent deadlock when serializing NMI backtraces

On Wed 2018-05-23 11:01:07, Sergey Senozhatsky wrote: > On (05/22/18 17:43), Steven Rostedt wrote: > > > CPU0 CPU1CPU2 > > > > > > printk() > > > vprintk_emit() > > > spin_lock(_lock) > > > > > >

Re: [RFC PATCH v2 00/12] get rid of GFP_ZONE_TABLE/BAD

On Fri 25-05-18 05:00:44, Matthew Wilcox wrote: > On Thu, May 24, 2018 at 05:29:43PM +0200, Michal Hocko wrote: > > > ie if we had more, > > > could we solve our pain by making them more generic? > > > > Well, if you have more you will consume more bits in the struct pages, > > right? > > Not

<    4   5   6   7   8   9   10   11   12   13   >