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

3.18-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 3.18 002/185] MIPS: Fix ptrace(2) PTRACE_PEEKUSR and PTRACE_POKEUSR accesses to o32 FGRs

3.18-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 3.18 014/185] PCI: Add function 1 DMA alias quirk for Marvell 9128

3.18-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

[PATCH 3.18 015/185] tools lib traceevent: Fix get_field_str() for dynamic strings

3.18-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 3.18 014/185] PCI: Add function 1 DMA alias quirk for Marvell 9128

3.18-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

[PATCH 3.18 015/185] tools lib traceevent: Fix get_field_str() for dynamic strings

3.18-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 3.18 013/185] tracing/hrtimer: Fix tracing bugs by taking all clock bases and modes into account

3.18-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 3.18 017/185] nfs: Do not convert nfs_idmap_cache_timeout to jiffies

3.18-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 3.18 013/185] tracing/hrtimer: Fix tracing bugs by taking all clock bases and modes into account

3.18-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 3.18 017/185] nfs: Do not convert nfs_idmap_cache_timeout to jiffies

3.18-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 3.18 003/185] KVM: Fix spelling mistake: "cop_unsuable" -> "cop_unusable"

3.18-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

[PATCH 3.18 003/185] KVM: Fix spelling mistake: "cop_unsuable" -> "cop_unusable"

3.18-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

[PATCH 3.18 020/185] kconfig: Fix automatic menu creation mem leak

3.18-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 3.18 020/185] kconfig: Fix automatic menu creation mem leak

3.18-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 3.18 023/185] scsi: fas216: fix sense buffer initialization

3.18-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 3.18 023/185] scsi: fas216: fix sense buffer initialization

3.18-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:

[PATCH 3.18 021/185] kconfig: Fix expr_free() E_NOT leak

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Ulf Magnusson [ Upstream commit 5b1374b3b3c2fc4f63a398adfa446fb8eff791a4 ] Only the E_NOT operand and not the E_NOT node itself was freed, due to accidentally returning

[PATCH 3.18 021/185] kconfig: Fix expr_free() E_NOT leak

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Ulf Magnusson [ Upstream commit 5b1374b3b3c2fc4f63a398adfa446fb8eff791a4 ] Only the E_NOT operand and not the E_NOT node itself was freed, due to accidentally returning too early in

[PATCH 3.18 030/185] mm/mempolicy: add nodes_empty check in SYSC_migrate_pages

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Yisheng Xie [ Upstream commit 0486a38bcc4749808edbc848f1bcf232042770fc ] As in manpage of migrate_pages, the errno should be set to EINVAL when none of the node IDs

[PATCH 3.18 030/185] mm/mempolicy: add nodes_empty check in SYSC_migrate_pages

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Yisheng Xie [ Upstream commit 0486a38bcc4749808edbc848f1bcf232042770fc ] As in manpage of migrate_pages, the errno should be set to EINVAL when none of the node IDs specified by new_nodes are

[PATCH 3.18 026/185] RDMA/mlx5: Avoid memory leak in case of XRCD dealloc failure

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Leon Romanovsky [ Upstream commit b081808a66345ba725b77ecd8d759bee874cd937 ] Failure in XRCD FW deallocation command leaves memory leaked and returns error to the user

[PATCH 3.18 024/185] HID: roccat: prevent an out of bounds read in kovaplus_profile_activated()

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Dan Carpenter [ Upstream commit 7ad81482cad67cbe1ec808490d1ddfc420c42008 ] We get the "new_profile_index" value from the mouse device when we're handling raw events.

[PATCH 3.18 024/185] HID: roccat: prevent an out of bounds read in kovaplus_profile_activated()

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Dan Carpenter [ Upstream commit 7ad81482cad67cbe1ec808490d1ddfc420c42008 ] We get the "new_profile_index" value from the mouse device when we're handling raw events. Smatch taints it as

[PATCH 3.18 026/185] RDMA/mlx5: Avoid memory leak in case of XRCD dealloc failure

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Leon Romanovsky [ Upstream commit b081808a66345ba725b77ecd8d759bee874cd937 ] Failure in XRCD FW deallocation command leaves memory leaked and returns error to the user which he can't do

[PATCH 3.18 028/185] ocfs2/acl: use ip_xattr_sem to protect getting extended attribute

3.18-stable review patch. If anyone has any objections, please let me know. -- From: piaojun [ Upstream commit 16c8d569f5704a84164f30ff01b29879f3438065 ] The race between *set_acl and *get_acl will cause getting incomplete xattr data as below: processA

[PATCH 3.18 028/185] ocfs2/acl: use ip_xattr_sem to protect getting extended attribute

3.18-stable review patch. If anyone has any objections, please let me know. -- From: piaojun [ Upstream commit 16c8d569f5704a84164f30ff01b29879f3438065 ] The race between *set_acl and *get_acl will cause getting incomplete xattr data as below: processA

[PATCH 3.18 031/185] asm-generic: provide generic_pmdp_establish()

3.18-stable review patch. If anyone has any objections, please let me know. -- From: "Kirill A. Shutemov" [ Upstream commit c58f0bb77ed8bf93dfdde762b01cb67eebbdfc29 ] Patch series "Do not lose dirty bit on THP pages", v4. Vlastimil noted that

[PATCH 3.18 027/185] ocfs2: return -EROFS to mount.ocfs2 if inode block is invalid

3.18-stable review patch. If anyone has any objections, please let me know. -- From: piaojun [ Upstream commit 025bcbde3634b2c9b316f227fed13ad6ad6817fb ] If metadata is corrupted such as 'invalid inode block', we will get failed by calling 'mount()' and

Re: [PATCH V2 rdma-next 3/4] RDMA/hns: Add reset process for RoCE in hip08

On Sat, May 26, 2018 at 09:47:43AM +0800, Wei Hu (Xavier) wrote: > > > On 2018/5/25 22:55, Jason Gunthorpe wrote: > > On Fri, May 25, 2018 at 01:54:31PM +0800, Wei Hu (Xavier) wrote: > >> > >> On 2018/5/25 5:31, Jason Gunthorpe wrote: > static const struct hnae3_client_ops

[PATCH 3.18 031/185] asm-generic: provide generic_pmdp_establish()

3.18-stable review patch. If anyone has any objections, please let me know. -- From: "Kirill A. Shutemov" [ Upstream commit c58f0bb77ed8bf93dfdde762b01cb67eebbdfc29 ] Patch series "Do not lose dirty bit on THP pages", v4. Vlastimil noted that pmdp_invalidate() is not atomic

[PATCH 3.18 027/185] ocfs2: return -EROFS to mount.ocfs2 if inode block is invalid

3.18-stable review patch. If anyone has any objections, please let me know. -- From: piaojun [ Upstream commit 025bcbde3634b2c9b316f227fed13ad6ad6817fb ] If metadata is corrupted such as 'invalid inode block', we will get failed by calling 'mount()' and then set filesystem

Re: [PATCH V2 rdma-next 3/4] RDMA/hns: Add reset process for RoCE in hip08

On Sat, May 26, 2018 at 09:47:43AM +0800, Wei Hu (Xavier) wrote: > > > On 2018/5/25 22:55, Jason Gunthorpe wrote: > > On Fri, May 25, 2018 at 01:54:31PM +0800, Wei Hu (Xavier) wrote: > >> > >> On 2018/5/25 5:31, Jason Gunthorpe wrote: > static const struct hnae3_client_ops

[PATCH 3.18 033/185] IB/ipoib: Fix for potential no-carrier state

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Alex Estrin [ Upstream commit 1029361084d18cc270f64dfd39529fafa10cfe01 ] On reboot SM can program port pkey table before ipoib registered its event handler, which could

[PATCH 3.18 033/185] IB/ipoib: Fix for potential no-carrier state

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Alex Estrin [ Upstream commit 1029361084d18cc270f64dfd39529fafa10cfe01 ] On reboot SM can program port pkey table before ipoib registered its event handler, which could result in missing pkey

[PATCH 3.18 032/185] mm: pin address_space before dereferencing it while isolating an LRU page

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Mel Gorman [ Upstream commit 69d763fc6d3aee787a3e8c8c35092b4f4960fa5d ] Minchan Kim asked the following question -- what locks protects address_space destroying

[PATCH 3.18 032/185] mm: pin address_space before dereferencing it while isolating an LRU page

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Mel Gorman [ Upstream commit 69d763fc6d3aee787a3e8c8c35092b4f4960fa5d ] Minchan Kim asked the following question -- what locks protects address_space destroying when race happens between

[PATCH 3.18 008/185] xen-swiotlb: fix the check condition for xen_swiotlb_free_coherent

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Joe Jin commit 4855c92dbb7b3b85c23e88ab7ca04f99b9677b41 upstream. When run raidconfig from Dom0 we found that the Xen DMA heap is reduced, but Dom Heap is increased by the

[PATCH 3.18 029/185] mm/mempolicy: fix the check of nodemask from user

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Yisheng Xie [ Upstream commit 56521e7a02b7b84a5e72691a1fb15570e6055545 ] As Xiaojun reported the ltp of migrate_pages01 will fail on arm64 system which has 4

[PATCH 3.18 008/185] xen-swiotlb: fix the check condition for xen_swiotlb_free_coherent

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Joe Jin commit 4855c92dbb7b3b85c23e88ab7ca04f99b9677b41 upstream. When run raidconfig from Dom0 we found that the Xen DMA heap is reduced, but Dom Heap is increased by the same size. Tracing

[PATCH 3.18 029/185] mm/mempolicy: fix the check of nodemask from user

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Yisheng Xie [ Upstream commit 56521e7a02b7b84a5e72691a1fb15570e6055545 ] As Xiaojun reported the ltp of migrate_pages01 will fail on arm64 system which has 4 nodes[0...3], all have memory and

Re: [PATCH] perf tools: Fix indexing for decoder packet queue

On 27 May 2018 at 21:13, Leo Yan wrote: > On Fri, May 25, 2018 at 05:10:54PM -0600, Mathieu Poirier wrote: >> The tail of a queue is supposed to be pointing to the next available slot >> in a queue. In this implementation the tail is incremented before it is >> used and as

Re: [PATCH] perf tools: Fix indexing for decoder packet queue

On 27 May 2018 at 21:13, Leo Yan wrote: > On Fri, May 25, 2018 at 05:10:54PM -0600, Mathieu Poirier wrote: >> The tail of a queue is supposed to be pointing to the next available slot >> in a queue. In this implementation the tail is incremented before it is >> used and as such points to the

[PATCH 3.18 007/185] libata: Blacklist some Sandisk SSDs for NCQ

3.18-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

[PATCH 3.18 034/185] x86/power: Fix swsusp_arch_resume prototype

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Arnd Bergmann [ Upstream commit 328008a72d38b5bde6491e463405c34a81a65d3e ] The declaration for swsusp_arch_resume marks it as 'asmlinkage', but the definition in x86-32 does

[PATCH 3.18 007/185] libata: Blacklist some Sandisk SSDs for NCQ

3.18-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 3.18 034/185] x86/power: Fix swsusp_arch_resume prototype

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Arnd Bergmann [ Upstream commit 328008a72d38b5bde6491e463405c34a81a65d3e ] The declaration for swsusp_arch_resume marks it as 'asmlinkage', but the definition in x86-32 does not, and it fails

Re: [PATCH] IB: Revert "remove redundant INFINIBAND kconfig dependencies"

On Fri, May 25, 2018 at 11:29:59PM +0200, Arnd Bergmann wrote: > Several subsystems depend on INFINIBAND_ADDR_TRANS, which in turn depends > on INFINIBAND. However, when with CONFIG_INIFIBAND=m, this leads to a > link error when another driver using it is built-in. The > INFINIBAND_ADDR_TRANS

[PATCH 3.18 010/185] firewire-ohci: work around oversized DMA reads on JMicron controllers

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Hector Martin [ Upstream commit 188775181bc05f29372b305ef96485840e351fde ] At least some JMicron controllers issue buggy oversized DMA reads when fetching context

[PATCH 3.18 010/185] firewire-ohci: work around oversized DMA reads on JMicron controllers

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Hector Martin [ Upstream commit 188775181bc05f29372b305ef96485840e351fde ] At least some JMicron controllers issue buggy oversized DMA reads when fetching context descriptors, always fetching

Re: [PATCH] IB: Revert "remove redundant INFINIBAND kconfig dependencies"

On Fri, May 25, 2018 at 11:29:59PM +0200, Arnd Bergmann wrote: > Several subsystems depend on INFINIBAND_ADDR_TRANS, which in turn depends > on INFINIBAND. However, when with CONFIG_INIFIBAND=m, this leads to a > link error when another driver using it is built-in. The > INFINIBAND_ADDR_TRANS

[PATCH 3.18 001/185] MIPS: ptrace: Expose FIR register through FP regset

3.18-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 3.18 001/185] MIPS: ptrace: Expose FIR register through FP regset

3.18-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 3.18 036/185] ACPI: processor_perflib: Do not send _PPC change notification if not ready

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Chen Yu [ Upstream commit ba1edb9a5125a617d612f98eead14b9b84e75c3a ] The following warning was triggered after resumed from S3 - if all the nonboot CPUs were put offline

[PATCH 3.18 047/185] scsi: bnx2fc: Fix check in SCSI completion handler for timed out request

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Chad Dupuis [ Upstream commit ecf7ff49945f5741fa1da112f994939f942031d3 ] When a request times out we set the io_req flag BNX2FC_FLAG_IO_COMPL so that if a subsequent

[PATCH 3.18 036/185] ACPI: processor_perflib: Do not send _PPC change notification if not ready

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Chen Yu [ Upstream commit ba1edb9a5125a617d612f98eead14b9b84e75c3a ] The following warning was triggered after resumed from S3 - if all the nonboot CPUs were put offline before suspend: [

[PATCH 3.18 047/185] scsi: bnx2fc: Fix check in SCSI completion handler for timed out request

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Chad Dupuis [ Upstream commit ecf7ff49945f5741fa1da112f994939f942031d3 ] When a request times out we set the io_req flag BNX2FC_FLAG_IO_COMPL so that if a subsequent completion comes in on

[PATCH 3.18 049/185] scsi: mptfusion: Add bounds check in mptctl_hp_targetinfo()

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Dan Carpenter [ Upstream commit a7043e9529f3c367cc4d82997e00be034cbe57ca ] My static checker complains about an out of bounds read:

[PATCH 3.18 049/185] scsi: mptfusion: Add bounds check in mptctl_hp_targetinfo()

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Dan Carpenter [ Upstream commit a7043e9529f3c367cc4d82997e00be034cbe57ca ] My static checker complains about an out of bounds read: drivers/message/fusion/mptctl.c:2786

[PATCH 3.18 046/185] scsi: ufs: Enable quirk to ignore sending WRITE_SAME command

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Sujit Reddy Thumma [ Upstream commit 84af7e8b895088d89f246d6b0f82717fafdebf61 ] WRITE_SAME command is not supported by UFS. Enable a quirk for the upper level drivers

[PATCH 3.18 046/185] scsi: ufs: Enable quirk to ignore sending WRITE_SAME command

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Sujit Reddy Thumma [ Upstream commit 84af7e8b895088d89f246d6b0f82717fafdebf61 ] WRITE_SAME command is not supported by UFS. Enable a quirk for the upper level drivers to not send WRITE SAME

Re: [PATCH 12/12] ARM: dts: exynos5250-arndale: add dsi and panel nodes

On Mon, May 28, 2018 at 11:55 AM, Maciej Purski wrote: > The patch adds bridge and panel nodes. > It adds also DSI properties specific for arndale board. > > Signed-off-by: Andrzej Hajda > Signed-off-by: Maciej Purski > --- >

Re: [PATCH v2 3/6] mtd: rawnand: add NVIDIA Tegra NAND Flash controller driver

Note that it's certainly possible to encode U-Boot and kernel with RS[4] and still use RS[8] for the rootfs even if the boot rom doesn't support it. This whole 'use-bootable-ecc-only' business seems a bit overengineered. 2018-05-28 14:43 GMT+02:00 Stefan Agner : > On 28.05.2018

[PATCH 3.18 050/185] scsi: qla2xxx: Avoid triggering undefined behavior in qla2x00_mbx_completion()

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Bart Van Assche [ Upstream commit c02189e12ce3bf3808cb880569d3b10249f50bd9 ] A left shift must shift less than the bit width of the left argument. Avoid triggering

Re: [PATCH 12/12] ARM: dts: exynos5250-arndale: add dsi and panel nodes

On Mon, May 28, 2018 at 11:55 AM, Maciej Purski wrote: > The patch adds bridge and panel nodes. > It adds also DSI properties specific for arndale board. > > Signed-off-by: Andrzej Hajda > Signed-off-by: Maciej Purski > --- > arch/arm/boot/dts/exynos5250-arndale.dts | 39 >

Re: [PATCH v2 3/6] mtd: rawnand: add NVIDIA Tegra NAND Flash controller driver

Note that it's certainly possible to encode U-Boot and kernel with RS[4] and still use RS[8] for the rootfs even if the boot rom doesn't support it. This whole 'use-bootable-ecc-only' business seems a bit overengineered. 2018-05-28 14:43 GMT+02:00 Stefan Agner : > On 28.05.2018 13:57, Dmitry

[PATCH 3.18 050/185] scsi: qla2xxx: Avoid triggering undefined behavior in qla2x00_mbx_completion()

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Bart Van Assche [ Upstream commit c02189e12ce3bf3808cb880569d3b10249f50bd9 ] A left shift must shift less than the bit width of the left argument. Avoid triggering undefined behavior if

[PATCH 3.18 054/185] scsi: aacraid: fix shutdown crash when init fails

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Meelis Roos [ Upstream commit 00c20cdc79259c6c5bf978b21af96c2d3edb646d ] When aacraid init fails with "AAC0: adapter self-test failed.", shutdown leads to UBSAN warning and

[PATCH 3.18 054/185] scsi: aacraid: fix shutdown crash when init fails

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Meelis Roos [ Upstream commit 00c20cdc79259c6c5bf978b21af96c2d3edb646d ] When aacraid init fails with "AAC0: adapter self-test failed.", shutdown leads to UBSAN warning and then oops:

[PATCH 3.18 055/185] scsi: qla4xxx: skip error recovery in case of register disconnect.

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Manish Rangankar [ Upstream commit 1bc5ad3a6acdcf56f83272f2de1cd2389ea9e9e2 ] A system crashes when continuously removing/re-adding the storage controller.

[PATCH 3.18 055/185] scsi: qla4xxx: skip error recovery in case of register disconnect.

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Manish Rangankar [ Upstream commit 1bc5ad3a6acdcf56f83272f2de1cd2389ea9e9e2 ] A system crashes when continuously removing/re-adding the storage controller. Signed-off-by: Manish Rangankar

[PATCH] sh: pass machine size to sparse

By default, sparse assumes a 64bit machine when compiled on x86-64 and 32bit when compiled on anything else. This can of course create all sort of problems, like issuing false warnings like: 'shift too big (32) for type unsigned long', or worse, to not emit legitimate warnings. Fix this by

[PATCH 3.18 057/185] ARM: OMAP1: clock: Fix debugfs_create_*() usage

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Geert Uytterhoeven [ Upstream commit 8cbbf1745dcde7ba7e423dc70619d223de90fd43 ] When exposing data access through debugfs, the correct debugfs_create_*() functions

[PATCH] sh: pass machine size to sparse

By default, sparse assumes a 64bit machine when compiled on x86-64 and 32bit when compiled on anything else. This can of course create all sort of problems, like issuing false warnings like: 'shift too big (32) for type unsigned long', or worse, to not emit legitimate warnings. Fix this by

[PATCH 3.18 057/185] ARM: OMAP1: clock: Fix debugfs_create_*() usage

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Geert Uytterhoeven [ Upstream commit 8cbbf1745dcde7ba7e423dc70619d223de90fd43 ] When exposing data access through debugfs, the correct debugfs_create_*() functions must be used, depending on

Re: [PATCH] IB: Revert "remove redundant INFINIBAND kconfig dependencies"

On Fri, May 25, 2018 at 05:32:52PM -0700, Greg Thelen wrote: > On Fri, May 25, 2018 at 2:32 PM Arnd Bergmann wrote: > > > Several subsystems depend on INFINIBAND_ADDR_TRANS, which in turn depends > > on INFINIBAND. However, when with CONFIG_INIFIBAND=m, this leads to a > > link

Re: [PATCH] IB: Revert "remove redundant INFINIBAND kconfig dependencies"

On Fri, May 25, 2018 at 05:32:52PM -0700, Greg Thelen wrote: > On Fri, May 25, 2018 at 2:32 PM Arnd Bergmann wrote: > > > Several subsystems depend on INFINIBAND_ADDR_TRANS, which in turn depends > > on INFINIBAND. However, when with CONFIG_INIFIBAND=m, this leads to a > > link error when

[PATCH] powerpc/64: Fix build failure with GCC 8.1

CC arch/powerpc/kernel/nvram_64.o arch/powerpc/kernel/nvram_64.c: In function 'nvram_create_partition': arch/powerpc/kernel/nvram_64.c:1042:2: error: 'strncpy' specified bound 12 equals destination size [-Werror=stringop-truncation] strncpy(new_part->header.name, name, 12);

[PATCH] powerpc/64: Fix build failure with GCC 8.1

CC arch/powerpc/kernel/nvram_64.o arch/powerpc/kernel/nvram_64.c: In function 'nvram_create_partition': arch/powerpc/kernel/nvram_64.c:1042:2: error: 'strncpy' specified bound 12 equals destination size [-Werror=stringop-truncation] strncpy(new_part->header.name, name, 12);

Re: [PATCH v4 6/6] tty/serial: atmel: changed the driver to work under at91-usart mfd

On 25/05/2018 19:19, Radu Pirea wrote: > This patch modifies the place where resources and device tree properties > are searched. > > Signed-off-by: Radu Pirea > --- > drivers/tty/serial/Kconfig| 1 + > drivers/tty/serial/atmel_serial.c | 40

Re: [PATCH v4 6/6] tty/serial: atmel: changed the driver to work under at91-usart mfd

On 25/05/2018 19:19, Radu Pirea wrote: > This patch modifies the place where resources and device tree properties > are searched. > > Signed-off-by: Radu Pirea > --- > drivers/tty/serial/Kconfig| 1 + > drivers/tty/serial/atmel_serial.c | 40 +-- > 2 files

[PATCH 0/5] Remove sh_mobile_ceu_camera from arch/sh

Hello, this series removes dependencies on the soc_camera based sh_mobile_ceu_camera driver from 3 board files in arch/sh and from one sensor driver used by one of those boards. Hans, this means there are no more user of the soc_camera framework that I know of in Linux, and I guess we can now

[PATCH 0/5] Remove sh_mobile_ceu_camera from arch/sh

Hello, this series removes dependencies on the soc_camera based sh_mobile_ceu_camera driver from 3 board files in arch/sh and from one sensor driver used by one of those boards. Hans, this means there are no more user of the soc_camera framework that I know of in Linux, and I guess we can now

[PATCH 3/5] arch: sh: kfr2r09: Use new renesas-ceu camera driver

Use the new renesas-ceu camera driver in kfr2r09 board file instead of the soc_camera based sh_mobile_ceu_camera driver. Get rid of soc_camera specific components, and move clk and gpio handling away from board file, registering the clock source and the enable gpios for driver consumption.

[PATCH 3/5] arch: sh: kfr2r09: Use new renesas-ceu camera driver

Use the new renesas-ceu camera driver in kfr2r09 board file instead of the soc_camera based sh_mobile_ceu_camera driver. Get rid of soc_camera specific components, and move clk and gpio handling away from board file, registering the clock source and the enable gpios for driver consumption.

Re: [PATCH 10/12] ARM: dts: exynos5250: add DSI node

On Mon, May 28, 2018 at 11:54 AM, Maciej Purski wrote: > The patch adds common part of DSI node for Exynos5250 platforms. > > Signed-off-by: Andrzej Hajda > Signed-off-by: Maciej Purski > --- > arch/arm/boot/dts/exynos5250.dtsi |

Re: [PATCH 10/12] ARM: dts: exynos5250: add DSI node

On Mon, May 28, 2018 at 11:54 AM, Maciej Purski wrote: > The patch adds common part of DSI node for Exynos5250 platforms. > > Signed-off-by: Andrzej Hajda > Signed-off-by: Maciej Purski > --- > arch/arm/boot/dts/exynos5250.dtsi | 14 ++ > 1 file changed, 14 insertions(+) This

[PATCH 4/5] arch: sh: ms7724se: Use new renesas-ceu camera driver

Use the new renesas-ceu camera driver is ms7724se board file instead of the soc_camera based sh_mobile_ceu_camera driver. Get rid of soc_camera specific components, and register CEU0 and CEU1 with no active video subdevices. Memory for the CEU video buffers is now reserved with membocks APIs and

[PATCH 4/5] arch: sh: ms7724se: Use new renesas-ceu camera driver

Use the new renesas-ceu camera driver is ms7724se board file instead of the soc_camera based sh_mobile_ceu_camera driver. Get rid of soc_camera specific components, and register CEU0 and CEU1 with no active video subdevices. Memory for the CEU video buffers is now reserved with membocks APIs and

[PATCH 5/5] arch: sh: ap325rxa: Use new renesas-ceu camera driver

Use the new renesas-ceu camera driver in ap325rxa board file instead of the soc_camera based sh_mobile_ceu_camera driver. Get rid of soc_camera specific components, and register CEU0 with a single video sensor (ov7725). Memory for the CEU video buffers is now reserved with membocks APIs and need

Re: [PATCH] HID: rmi: use HID_QUIRK_NO_INPUT_SYNC

On Fri, May 25, 2018 at 2:51 PM, Benjamin Tissoires wrote: > When we receive a RMI4 report, we should not unconditionally send an > input_sync event. Instead, we should let the rmi4 transport layer do it > for us. > > This fixes a situation where we might receive X

[PATCH 1/5] media: i2c: Copy rj54n1cb0c soc_camera sensor driver

Copy the soc_camera based driver in v4l2 sensor driver directory. This commit just copies the original file without modifying it. No modification to KConfig and Makefile as soc_camera framework dependencies need to be removed first in next commit. Signed-off-by: Jacopo Mondi

[PATCH 5/5] arch: sh: ap325rxa: Use new renesas-ceu camera driver

Use the new renesas-ceu camera driver in ap325rxa board file instead of the soc_camera based sh_mobile_ceu_camera driver. Get rid of soc_camera specific components, and register CEU0 with a single video sensor (ov7725). Memory for the CEU video buffers is now reserved with membocks APIs and need

Re: [PATCH] HID: rmi: use HID_QUIRK_NO_INPUT_SYNC

On Fri, May 25, 2018 at 2:51 PM, Benjamin Tissoires wrote: > When we receive a RMI4 report, we should not unconditionally send an > input_sync event. Instead, we should let the rmi4 transport layer do it > for us. > > This fixes a situation where we might receive X in a report and the rest > in a

[PATCH 1/5] media: i2c: Copy rj54n1cb0c soc_camera sensor driver

Copy the soc_camera based driver in v4l2 sensor driver directory. This commit just copies the original file without modifying it. No modification to KConfig and Makefile as soc_camera framework dependencies need to be removed first in next commit. Signed-off-by: Jacopo Mondi ---

[PATCH 2/5] media: i2c: rj54n1: Remove soc_camera dependencies

Remove soc_camera framework dependencies from rj54n1 sensor driver. - Handle clock - Handle GPIOs (named 'powerup' and 'enable') - Register the async subdevice - Remove g/s_mbus_config as they're deprecated. - Adjust build system - List the driver as maintained for 'Odd Fixes' as I don't have HW

[PATCH 2/5] media: i2c: rj54n1: Remove soc_camera dependencies

Remove soc_camera framework dependencies from rj54n1 sensor driver. - Handle clock - Handle GPIOs (named 'powerup' and 'enable') - Register the async subdevice - Remove g/s_mbus_config as they're deprecated. - Adjust build system - List the driver as maintained for 'Odd Fixes' as I don't have HW

[PATCH 3.18 059/185] mac80211: round IEEE80211_TX_STATUS_HEADROOM up to multiple of 4

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Felix Fietkau [ Upstream commit 651b9920d7a694ffb1f885aef2bbb068a25d9d66 ] This ensures that mac80211 allocated management frames are properly aligned, which makes copying them

[PATCH 3.18 059/185] mac80211: round IEEE80211_TX_STATUS_HEADROOM up to multiple of 4

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Felix Fietkau [ Upstream commit 651b9920d7a694ffb1f885aef2bbb068a25d9d66 ] This ensures that mac80211 allocated management frames are properly aligned, which makes copying them more

Re: [PATCH v3 net-next 2/2] tcp: minor optimization around tcp_hdr() usage in tcp receive path

On Mon, May 28, 2018 at 8:36 AM Yafang Shao wrote: > This is additional to the commit ea1627c20c34 ("tcp: minor optimizations around tcp_hdr() usage"). > At this point, skb->data is same with tcp_hdr() as tcp header has not > been pulled yet. > Cc: Eric Dumazet

Re: [PATCH v3 net-next 2/2] tcp: minor optimization around tcp_hdr() usage in tcp receive path

On Mon, May 28, 2018 at 8:36 AM Yafang Shao wrote: > This is additional to the commit ea1627c20c34 ("tcp: minor optimizations around tcp_hdr() usage"). > At this point, skb->data is same with tcp_hdr() as tcp header has not > been pulled yet. > Cc: Eric Dumazet > Signed-off-by: Yafang Shao >

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