[PATCH 05/14] VFS: Provide empty name qstr [ver #2]

Provide an empty name (ie. "") qstr for general use. Signed-off-by: David Howells --- fs/dcache.c|8 ++-- fs/gfs2/dir.c |3 +-- fs/namei.c |3 +-- fs/nsfs.c |3 +-- fs/pipe.c |3 +--

[RFC 10/11] ima: handling all policy flags per namespace using ima_ns_policy structure

Global ima_appraise still saves the initial appraise mode and it is used to initialize namespace.ima_appraise flag when a user defined policy is set. Globals moved into ima_ns_policy structure (namespace IMA policy private data): - ima_policy_flag - ima_appraise - ima_rules -

[PATCH 05/14] VFS: Provide empty name qstr [ver #2]

Provide an empty name (ie. "") qstr for general use. Signed-off-by: David Howells --- fs/dcache.c|8 ++-- fs/gfs2/dir.c |3 +-- fs/namei.c |3 +-- fs/nsfs.c |3 +-- fs/pipe.c |3 +-- include/linux/dcache.h |

[RFC 10/11] ima: handling all policy flags per namespace using ima_ns_policy structure

Global ima_appraise still saves the initial appraise mode and it is used to initialize namespace.ima_appraise flag when a user defined policy is set. Globals moved into ima_ns_policy structure (namespace IMA policy private data): - ima_policy_flag - ima_appraise - ima_rules -

[PATCH 10/14] procfs: Move proc_fill_super() to fs/proc/root.c [ver #2]

Move proc_fill_super() to fs/proc/root.c as that's where the other superblock stuff is. Signed-off-by: David Howells --- fs/proc/inode.c| 48 +--- fs/proc/internal.h |4 +--- fs/proc/root.c | 48

[RFC 00/11] ima: namespace support for IMA policy

The IMA policy rules and policy/appraise flags are now encapsulated on a new structure which completely describes the policy for a given namespace. The correct namespace structure is retrieved from a radix tree based on the namespace id in use by the process in the context whenever the IMA

[PATCH 10/14] procfs: Move proc_fill_super() to fs/proc/root.c [ver #2]

Move proc_fill_super() to fs/proc/root.c as that's where the other superblock stuff is. Signed-off-by: David Howells --- fs/proc/inode.c| 48 +--- fs/proc/internal.h |4 +--- fs/proc/root.c | 48

[RFC 00/11] ima: namespace support for IMA policy

The IMA policy rules and policy/appraise flags are now encapsulated on a new structure which completely describes the policy for a given namespace. The correct namespace structure is retrieved from a radix tree based on the namespace id in use by the process in the context whenever the IMA

[PATCH 04/14] VFS: Make get_filesystem() return the affected filesystem [ver #2]

Make get_filesystem() return a pointer to the filesystem on which it just got a ref. Suggested-by: Rasmus Villemoes Signed-off-by: David Howells --- fs/filesystems.c |3 ++- include/linux/fs.h |2 +- 2 files changed, 3 insertions(+), 2

[PATCH 04/14] VFS: Make get_filesystem() return the affected filesystem [ver #2]

Make get_filesystem() return a pointer to the filesystem on which it just got a ref. Suggested-by: Rasmus Villemoes Signed-off-by: David Howells --- fs/filesystems.c |3 ++- include/linux/fs.h |2 +- 2 files changed, 3 insertions(+), 2 deletions(-) diff --git a/fs/filesystems.c

[PATCH 03/14] VFS: Make get_mnt_ns() return the namespace [ver #2]

Make get_mnt_ns() return the namespace it got a ref on for consistency with other namespace ref getting functions. Signed-off-by: David Howells --- fs/mount.h |3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/fs/mount.h b/fs/mount.h index

[PATCH 03/14] VFS: Make get_mnt_ns() return the namespace [ver #2]

Make get_mnt_ns() return the namespace it got a ref on for consistency with other namespace ref getting functions. Signed-off-by: David Howells --- fs/mount.h |3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/fs/mount.h b/fs/mount.h index 2826543a131d..b1e99b38f2ee

[PATCH 02/14] Clean up whitespace in fs/namespace.c [ver #2]

Clean up line terminal whitespace in fs/namespace.c. Signed-off-by: David Howells --- fs/namespace.c |4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/fs/namespace.c b/fs/namespace.c index cc1375eff88c..db034b6afd43 100644 --- a/fs/namespace.c +++

[PATCH 02/14] Clean up whitespace in fs/namespace.c [ver #2]

Clean up line terminal whitespace in fs/namespace.c. Signed-off-by: David Howells --- fs/namespace.c |4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/fs/namespace.c b/fs/namespace.c index cc1375eff88c..db034b6afd43 100644 --- a/fs/namespace.c +++ b/fs/namespace.c @@

[PATCH 01/14] Provide a function to create a NUL-terminated string from unterminated data [ver #2]

Provide a function, kmemdup_nul(), that will create a NUL-terminated string from an unterminated character array where the length is known in advance. This is better than kstrndup() in situations where we already know the string length as the strnlen() in kstrndup() is superfluous.

[PATCH 01/14] Provide a function to create a NUL-terminated string from unterminated data [ver #2]

Provide a function, kmemdup_nul(), that will create a NUL-terminated string from an unterminated character array where the length is known in advance. This is better than kstrndup() in situations where we already know the string length as the strnlen() in kstrndup() is superfluous.

[RFC][PATCH 00/14] VFS: Introduce superblock configuration context [ver #2]

Here are a set of patches to create a superblock configuration context prior to setting up a new mount, populating it with the parsed options/binary data, creating the superblock and then effecting the mount. This allows namespaces and other information to be conveyed through the mount

[RFC][PATCH 00/14] VFS: Introduce superblock configuration context [ver #2]

Here are a set of patches to create a superblock configuration context prior to setting up a new mount, populating it with the parsed options/binary data, creating the superblock and then effecting the mount. This allows namespaces and other information to be conveyed through the mount

Re: [PATCH] xfs: avoid harmless gcc-7 warnings

On Thu, May 11, 2017 at 02:49:21PM +0200, Arnd Bergmann wrote: > gcc-7 flags the use of integer math inside of a condition > as a potential bug: > > fs/xfs/xfs_bmap_util.c: In function 'xfs_swap_extents_check_format': > fs/xfs/xfs_bmap_util.c:1619:8: error: '<<' in boolean context, did you mean

Re: [PATCH] xfs: avoid harmless gcc-7 warnings

On Thu, May 11, 2017 at 02:49:21PM +0200, Arnd Bergmann wrote: > gcc-7 flags the use of integer math inside of a condition > as a potential bug: > > fs/xfs/xfs_bmap_util.c: In function 'xfs_swap_extents_check_format': > fs/xfs/xfs_bmap_util.c:1619:8: error: '<<' in boolean context, did you mean

[PATCH 14/14] Add commands to create or update a superblock [ver #2]

Institute a separate step in the mounting procedure: (1) Create new sb_config context. (2) Configure the context. (3) Create superblock. (4) Mount the superblock any number of times. (5) Destroy the context. Step (3) is added and must be given by userspace before fsmount() may be used:

Re: pinctrl-sx150x.c broken in 4.11

> Hmm maybe yeah. I don't quite follow the above the "pinctrl-0 property > of sx150x device tree node, is misinterpreted as hog" part though. sx150x is i2c-gpio device. It has 16 GPIO lines that are communicated with via i2c bus, and an interrupt line. Interrupt line is typically connected to

[PATCH 14/14] Add commands to create or update a superblock [ver #2]

Institute a separate step in the mounting procedure: (1) Create new sb_config context. (2) Configure the context. (3) Create superblock. (4) Mount the superblock any number of times. (5) Destroy the context. Step (3) is added and must be given by userspace before fsmount() may be used:

Re: pinctrl-sx150x.c broken in 4.11

> Hmm maybe yeah. I don't quite follow the above the "pinctrl-0 property > of sx150x device tree node, is misinterpreted as hog" part though. sx150x is i2c-gpio device. It has 16 GPIO lines that are communicated with via i2c bus, and an interrupt line. Interrupt line is typically connected to

Re: Implementing Dynamic Rerouting in Kernel

On 05/11/2017 02:59 AM, Ravish Kumar wrote: > Hi Experts, > > Need expert advice for the one of the requirement Where in VPN > solution we want to dynaically route the packets to different adapter. > We will manage our own DNS cache and , based on DNS to IP lookup, we > can redirect the packet

Re: Implementing Dynamic Rerouting in Kernel

On 05/11/2017 02:59 AM, Ravish Kumar wrote: > Hi Experts, > > Need expert advice for the one of the requirement Where in VPN > solution we want to dynaically route the packets to different adapter. > We will manage our own DNS cache and , based on DNS to IP lookup, we > can redirect the packet

[PATCH 4/4] vmbus: Adjust five checks for null pointers

From: Markus Elfring Date: Thu, 11 May 2017 17:52:38 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The script “checkpatch.pl” pointed information out like the following. Comparison to NULL could be written … Thus

[PATCH 4/4] vmbus: Adjust five checks for null pointers

From: Markus Elfring Date: Thu, 11 May 2017 17:52:38 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The script “checkpatch.pl” pointed information out like the following. Comparison to NULL could be written … Thus fix the affected source code

[PATCH 1/4] vmbus: Improve a size determination in vmbus_device_create()

From: Markus Elfring Date: Thu, 11 May 2017 17:30:10 +0200 Replace the specification of a data structure by a pointer dereference as the parameter for the operator "sizeof" to make the corresponding size determination a bit safer according to the Linux coding style

[PATCH 1/4] vmbus: Improve a size determination in vmbus_device_create()

From: Markus Elfring Date: Thu, 11 May 2017 17:30:10 +0200 Replace the specification of a data structure by a pointer dereference as the parameter for the operator "sizeof" to make the corresponding size determination a bit safer according to the Linux coding style convention. Signed-off-by:

Re: [PATCH] net: qca_spi: Fix alignment issues in rx path

From: Stefan Wahren Date: Tue, 9 May 2017 15:40:38 +0200 > The qca_spi driver causes alignment issues on ARM devices. > So fix this by using netdev_alloc_skb_ip_align(). > > Signed-off-by: Stefan Wahren > Fixes: 291ab06ecf67 ("net: qualcomm: new

Re: [PATCH] net: qca_spi: Fix alignment issues in rx path

From: Stefan Wahren Date: Tue, 9 May 2017 15:40:38 +0200 > The qca_spi driver causes alignment issues on ARM devices. > So fix this by using netdev_alloc_skb_ip_align(). > > Signed-off-by: Stefan Wahren > Fixes: 291ab06ecf67 ("net: qualcomm: new Ethernet over SPI driver for > QCA7000")

[PATCH 3/4] vmbus: Fix a typo in a comment line

From: Markus Elfring Date: Thu, 11 May 2017 17:43:55 +0200 Add a missing character in this description. Signed-off-by: Markus Elfring --- drivers/hv/vmbus_drv.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

[PATCH 3/4] vmbus: Fix a typo in a comment line

From: Markus Elfring Date: Thu, 11 May 2017 17:43:55 +0200 Add a missing character in this description. Signed-off-by: Markus Elfring --- drivers/hv/vmbus_drv.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/hv/vmbus_drv.c b/drivers/hv/vmbus_drv.c index

[PATCH 2/4] vmbus: Delete an error message for a failed memory allocation in vmbus_device_create()

From: Markus Elfring Date: Thu, 11 May 2017 17:33:14 +0200 Omit an extra message for a memory allocation failure in this function. This issue was detected by using the Coccinelle software. Link:

[PATCH 2/4] vmbus: Delete an error message for a failed memory allocation in vmbus_device_create()

From: Markus Elfring Date: Thu, 11 May 2017 17:33:14 +0200 Omit an extra message for a memory allocation failure in this function. This issue was detected by using the Coccinelle software. Link: http://events.linuxfoundation.org/sites/events/files/slides/LCJ16-Refactor_Strings-WSang_0.pdf

[PATCH] soc: imx: gpc: build gpc only if hardware has gpc

Add CONFIG_HAVE_IMX_GPC to goal definition of gpc.o, to avoid building it for hardware that does not need it. Signed-off-by: Marc Ohlf --- drivers/soc/imx/Makefile | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/soc/imx/Makefile

[PATCH] soc: imx: gpc: build gpc only if hardware has gpc

Add CONFIG_HAVE_IMX_GPC to goal definition of gpc.o, to avoid building it for hardware that does not need it. Signed-off-by: Marc Ohlf --- drivers/soc/imx/Makefile | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/soc/imx/Makefile b/drivers/soc/imx/Makefile index

[PATCH 0/4] VMBus: Adjustments for some function implementations

From: Markus Elfring Date: Thu, 11 May 2017 18:00:18 +0200 A few update suggestions were taken into account from static source code analysis. Markus Elfring (4): Improve a size determination in vmbus_device_create() Delete an error message for a failed memory

Re: [PATCH] netxen_nic: set rcode to the return status from the call to netxen_issue_cmd

From: Colin King Date: Tue, 9 May 2017 17:19:42 +0100 > From: Colin Ian King > > Currently rcode is being initialized to NX_RCODE_SUCCESS and later it > is checked to see if it is not NX_RCODE_SUCCESS which is never true. It > appears that

[PATCH 0/4] VMBus: Adjustments for some function implementations

From: Markus Elfring Date: Thu, 11 May 2017 18:00:18 +0200 A few update suggestions were taken into account from static source code analysis. Markus Elfring (4): Improve a size determination in vmbus_device_create() Delete an error message for a failed memory allocation in

Re: [PATCH] netxen_nic: set rcode to the return status from the call to netxen_issue_cmd

From: Colin King Date: Tue, 9 May 2017 17:19:42 +0100 > From: Colin Ian King > > Currently rcode is being initialized to NX_RCODE_SUCCESS and later it > is checked to see if it is not NX_RCODE_SUCCESS which is never true. It > appears that there is an unintentional missing assignment of rcode

Re: [PATCH v6 19/23] drivers/fsi: Add GPIO based FSI master

On 5/10/17 8:58 PM, Jeremy Kerr wrote: Hi Chris, I don't think we'd want this per master. The lock is for the 'top' master issuing commands. Only the top master can initiate any transactions on the bus to any devices connected downstream. Downstream masters such as hub masters, etc...

Re: [PATCH v6 19/23] drivers/fsi: Add GPIO based FSI master

On 5/10/17 8:58 PM, Jeremy Kerr wrote: Hi Chris, I don't think we'd want this per master. The lock is for the 'top' master issuing commands. Only the top master can initiate any transactions on the bus to any devices connected downstream. Downstream masters such as hub masters, etc...

Re: [PATCH 1/1] remoteproc: fix elf_loader da_to_va translation and writing beyond segment

On 05/11/2017 02:05 AM, Bjorn Andersson wrote: On Wed 03 May 05:12 PDT 2017, Henri Roosen wrote: Consider a system with 2 memory regions: 0x1fff8000 - 0x1fff: iram So I presume there's a hole here. 0x2100 - 0x21007fff: dram The .elf file for this system contains the following

Re: [PATCH 1/1] remoteproc: fix elf_loader da_to_va translation and writing beyond segment

On 05/11/2017 02:05 AM, Bjorn Andersson wrote: On Wed 03 May 05:12 PDT 2017, Henri Roosen wrote: Consider a system with 2 memory regions: 0x1fff8000 - 0x1fff: iram So I presume there's a hole here. 0x2100 - 0x21007fff: dram The .elf file for this system contains the following

Re: Is there an recommended way to refer to bitkeepr commits?

On 05/11/2017 01:59 AM, Michael Ellerman wrote: > Linus Torvalds writes: > >> On Wed, May 10, 2017 at 3:04 PM, Eric W. Biederman >> wrote: >>> >>> Thomas Gleixner appears to have a tree with all of those same commits >>> except with the

Re: Is there an recommended way to refer to bitkeepr commits?

On 05/11/2017 01:59 AM, Michael Ellerman wrote: > Linus Torvalds writes: > >> On Wed, May 10, 2017 at 3:04 PM, Eric W. Biederman >> wrote: >>> >>> Thomas Gleixner appears to have a tree with all of those same commits >>> except with the BKrev tags stripped out. >> >> That's the best import - so

Re: [PATCHv2] arm64/cpufeature: don't use mutex in bringup path

On 11/05/17 16:54, Suzuki K Poulose wrote: > On 11/05/17 16:37, Mark Rutland wrote: >> On Thu, May 11, 2017 at 04:15:38PM +0100, Suzuki K Poulose wrote: >>> On 11/05/17 16:01, Mark Rutland wrote: +static inline bool cpus_have_const_cap(int num) +{ + if

Re: [PATCHv2] arm64/cpufeature: don't use mutex in bringup path

On 11/05/17 16:54, Suzuki K Poulose wrote: > On 11/05/17 16:37, Mark Rutland wrote: >> On Thu, May 11, 2017 at 04:15:38PM +0100, Suzuki K Poulose wrote: >>> On 11/05/17 16:01, Mark Rutland wrote: +static inline bool cpus_have_const_cap(int num) +{ + if

Re: [linux-sunxi] Re: [PATCH] pinctrl: use non-devm kmalloc versions for free functions

于 2017年5月11日 GMT+08:00 下午10:01:54, Linus Walleij 写到: >On Thu, May 4, 2017 at 1:57 AM, Andre Przywara >wrote: > >> When a pinctrl driver gets interrupted during its probe process >> (returning -EPROBE_DEFER), the devres system cleans up all

Re: [linux-sunxi] Re: [PATCH] pinctrl: use non-devm kmalloc versions for free functions

于 2017年5月11日 GMT+08:00 下午10:01:54, Linus Walleij 写到: >On Thu, May 4, 2017 at 1:57 AM, Andre Przywara >wrote: > >> When a pinctrl driver gets interrupted during its probe process >> (returning -EPROBE_DEFER), the devres system cleans up all allocated >> resources. During this process it calls

Re: [PATCH v2 05/10] usb: musb: tusb6010_omap: Do not reset the other direction's packet size

On Thu, May 11, 2017 at 09:19:17AM +0300, Peter Ujfalusi wrote: > > > On 2017-05-11 02:16, Joe Perches wrote: > >On Wed, 2017-05-10 at 12:07 -0500, Bin Liu wrote: > >>On Wed, May 10, 2017 at 11:42:27AM +0300, Peter Ujfalusi wrote: > >>>We have one register for each EP to set the maximum packet

Re: [PATCH v2 05/10] usb: musb: tusb6010_omap: Do not reset the other direction's packet size

On Thu, May 11, 2017 at 09:19:17AM +0300, Peter Ujfalusi wrote: > > > On 2017-05-11 02:16, Joe Perches wrote: > >On Wed, 2017-05-10 at 12:07 -0500, Bin Liu wrote: > >>On Wed, May 10, 2017 at 11:42:27AM +0300, Peter Ujfalusi wrote: > >>>We have one register for each EP to set the maximum packet

[PATCH 4.11 23/28] bpf: dont let ldimm64 leak map addresses on unprivileged

4.11-stable review patch. If anyone has any objections, please let me know. -- From: Daniel Borkmann [ Upstream commit 0d0e57697f162da4aa218b5feafe614fb666db07 ] The patch fixes two things at once: 1) It checks the env->allow_ptr_leaks and only prints

[PATCH 4.11 23/28] bpf: dont let ldimm64 leak map addresses on unprivileged

4.11-stable review patch. If anyone has any objections, please let me know. -- From: Daniel Borkmann [ Upstream commit 0d0e57697f162da4aa218b5feafe614fb666db07 ] The patch fixes two things at once: 1) It checks the env->allow_ptr_leaks and only prints the map address to

Re: [PATCH RT v2] futex/rtmutex: Cure RT double blocking issue

On 2017-05-11 11:54:47 [-0400], Steven Rostedt wrote: > This is the same patch that Thomas wrote, right? Shouldn't this start > with: > > From: Thomas Gleixner > > ? correct. It made its way properly into the patch queue, I just managed to get it wrong while sending it to

Re: [PATCH RT v2] futex/rtmutex: Cure RT double blocking issue

On 2017-05-11 11:54:47 [-0400], Steven Rostedt wrote: > This is the same patch that Thomas wrote, right? Shouldn't this start > with: > > From: Thomas Gleixner > > ? correct. It made its way properly into the patch queue, I just managed to get it wrong while sending it to the list… > -- Steve

Re: [PATCH RT v2] futex/rtmutex: Cure RT double blocking issue

On Thu, 11 May 2017 17:20:54 +0200 Sebastian Sewior wrote: This is the same patch that Thomas wrote, right? Shouldn't this start with: From: Thomas Gleixner ? -- Steve > RT has a problem when the wait on a futex/rtmutex got interrupted by a >

Re: [PATCH RT v2] futex/rtmutex: Cure RT double blocking issue

On Thu, 11 May 2017 17:20:54 +0200 Sebastian Sewior wrote: This is the same patch that Thomas wrote, right? Shouldn't this start with: From: Thomas Gleixner ? -- Steve > RT has a problem when the wait on a futex/rtmutex got interrupted by a > timeout or a signal. task->pi_blocked_on is

[PATCH 4.11 02/28] drm/sti: fix GDP size to support up to UHD resolution

4.11-stable review patch. If anyone has any objections, please let me know. -- From: Vincent Abriou commit 2f410f88c0a1c7e19762918d2614f506a7b63a82 upstream. On stih407-410 chip family the GDP layers are able to support up to UHD resolution (3840 x

[PATCH 4.11 02/28] drm/sti: fix GDP size to support up to UHD resolution

4.11-stable review patch. If anyone has any objections, please let me know. -- From: Vincent Abriou commit 2f410f88c0a1c7e19762918d2614f506a7b63a82 upstream. On stih407-410 chip family the GDP layers are able to support up to UHD resolution (3840 x 2160). Signed-off-by:

[PATCH 4.11 24/28] net: mdio-mux: bcm-iproc: call mdiobus_free() in error path

4.11-stable review patch. If anyone has any objections, please let me know. -- From: Jon Mason [ Upstream commit 922c60e89d52730050c6ccca218bff40cc8bcd8e ] If an error is encountered in mdio_mux_init(), the error path will call mdiobus_free(). Since

[PATCH 4.11 24/28] net: mdio-mux: bcm-iproc: call mdiobus_free() in error path

4.11-stable review patch. If anyone has any objections, please let me know. -- From: Jon Mason [ Upstream commit 922c60e89d52730050c6ccca218bff40cc8bcd8e ] If an error is encountered in mdio_mux_init(), the error path will call mdiobus_free(). Since mdiobus_register() has

[PATCH 4.11 26/28] xen/arm,arm64: fix xen_dma_ops after 815dd18 "Consolidate get_dma_ops..."

4.11-stable review patch. If anyone has any objections, please let me know. -- From: Stefano Stabellini commit e058632670b709145730a134acc3f83f392f7aa7 upstream. The following commit: commit 815dd18788fe0d41899f51b91d0560279cf16b0d Author: Bart

[PATCH 4.11 26/28] xen/arm,arm64: fix xen_dma_ops after 815dd18 "Consolidate get_dma_ops..."

4.11-stable review patch. If anyone has any objections, please let me know. -- From: Stefano Stabellini commit e058632670b709145730a134acc3f83f392f7aa7 upstream. The following commit: commit 815dd18788fe0d41899f51b91d0560279cf16b0d Author: Bart Van Assche Date: Fri

[PATCH 4.11 25/28] f2fs: sanity check segment count

4.11-stable review patch. If anyone has any objections, please let me know. -- From: Jin Qian commit b9dd46188edc2f0d1f37328637860bb65a771124 upstream. F2FS uses 4 bytes to represent block address. As a result, supported size of disk is 16 TB and it equals

[PATCH 4.11 25/28] f2fs: sanity check segment count

4.11-stable review patch. If anyone has any objections, please let me know. -- From: Jin Qian commit b9dd46188edc2f0d1f37328637860bb65a771124 upstream. F2FS uses 4 bytes to represent block address. As a result, supported size of disk is 16 TB and it equals to 16 * 1024 * 1024

[PATCH 4.11 20/28] ipv6: reorder ip6_route_dev_notifier after ipv6_dev_notf

4.11-stable review patch. If anyone has any objections, please let me know. -- From: WANG Cong [ Upstream commit 242d3a49a2a1a71d8eb9f953db1bcaa9d698ce00 ] For each netns (except init_net), we initialize its null entry in 3 places: 1) The template

[PATCH 4.11 20/28] ipv6: reorder ip6_route_dev_notifier after ipv6_dev_notf

4.11-stable review patch. If anyone has any objections, please let me know. -- From: WANG Cong [ Upstream commit 242d3a49a2a1a71d8eb9f953db1bcaa9d698ce00 ] For each netns (except init_net), we initialize its null entry in 3 places: 1) The template itself, as we use

Re: [PATCH] drbd: fix request leak introduced by locking/atomic, kref: Kill kref_sub()

On 05/11/2017 02:21 AM, Lars Ellenberg wrote: > Regression fix for 4.11, which totally broke DRBD > > When killing kref_sub(), the unconditional additional kref_get() > was not properly paired with the necessary kref_put(), causing > a leak of struct drbd_requests (~ 224 Bytes) per submitted bio,

Re: [PATCH] drbd: fix request leak introduced by locking/atomic, kref: Kill kref_sub()

On 05/11/2017 02:21 AM, Lars Ellenberg wrote: > Regression fix for 4.11, which totally broke DRBD > > When killing kref_sub(), the unconditional additional kref_get() > was not properly paired with the necessary kref_put(), causing > a leak of struct drbd_requests (~ 224 Bytes) per submitted bio,

[PATCH 4.11 27/28] xen: Revert commits da72ff5bfcb0 and 72a9b186292d

4.11-stable review patch. If anyone has any objections, please let me know. -- From: Boris Ostrovsky commit 84d582d236dc1f9085e741affc72e9ba061a67c2 upstream. Recent discussion (http://marc.info/?l=xen-devel=149192184523741) established that commit

[PATCH 4.11 22/28] bnxt_en: allocate enough space for ->ntp_fltr_bmap

4.11-stable review patch. If anyone has any objections, please let me know. -- From: Dan Carpenter [ Upstream commit ac45bd93a5035c2f39c9862b8b6ed692db0fdc87 ] We have the number of longs, but we need to calculate the number of bytes required.

[PATCH 4.11 27/28] xen: Revert commits da72ff5bfcb0 and 72a9b186292d

4.11-stable review patch. If anyone has any objections, please let me know. -- From: Boris Ostrovsky commit 84d582d236dc1f9085e741affc72e9ba061a67c2 upstream. Recent discussion (http://marc.info/?l=xen-devel=149192184523741) established that commit 72a9b186292d ("xen: Remove

[PATCH 4.11 22/28] bnxt_en: allocate enough space for ->ntp_fltr_bmap

4.11-stable review patch. If anyone has any objections, please let me know. -- From: Dan Carpenter [ Upstream commit ac45bd93a5035c2f39c9862b8b6ed692db0fdc87 ] We have the number of longs, but we need to calculate the number of bytes required. Fixes: c0c050c58d84 ("bnxt_en:

[PATCH 4.11 19/28] ipv6: initialize route null entry in addrconf_init()

4.11-stable review patch. If anyone has any objections, please let me know. -- From: WANG Cong [ Upstream commit 2f460933f58eee3393aba64f0f6d14acb08d1724 ] Andrey reported a crash on init_net.ipv6.ip6_null_entry->rt6i_idev since it is always NULL.

[PATCH 4.11 14/28] net: ipv6: Do not duplicate DAD on link up

4.11-stable review patch. If anyone has any objections, please let me know. -- From: David Ahern [ Upstream commit 6d717134a1a6e1b34a7d0d70e953037bc2642046 ] Andrey reported a warning triggered by the rcu code: [ cut here ]

[PATCH 4.11 14/28] net: ipv6: Do not duplicate DAD on link up

4.11-stable review patch. If anyone has any objections, please let me know. -- From: David Ahern [ Upstream commit 6d717134a1a6e1b34a7d0d70e953037bc2642046 ] Andrey reported a warning triggered by the rcu code: [ cut here ] WARNING: CPU: 1 PID: 5911

[PATCH 4.11 19/28] ipv6: initialize route null entry in addrconf_init()

4.11-stable review patch. If anyone has any objections, please let me know. -- From: WANG Cong [ Upstream commit 2f460933f58eee3393aba64f0f6d14acb08d1724 ] Andrey reported a crash on init_net.ipv6.ip6_null_entry->rt6i_idev since it is always NULL. This is clearly wrong, we

[PATCH 4.11 04/28] brcmfmac: Ensure pointer correctly set if skb data location changes

4.11-stable review patch. If anyone has any objections, please let me know. -- From: James Hughes commit 455a1eb4654c24560eb9dfc634f29cba3d87601e upstream. The incoming skb header may be resized if header space is insufficient, which might change

[PATCH 4.11 04/28] brcmfmac: Ensure pointer correctly set if skb data location changes

4.11-stable review patch. If anyone has any objections, please let me know. -- From: James Hughes commit 455a1eb4654c24560eb9dfc634f29cba3d87601e upstream. The incoming skb header may be resized if header space is insufficient, which might change the data adddress in the skb.

[PATCH 4.11 16/28] tcp: do not inherit fastopen_req from parent

4.11-stable review patch. If anyone has any objections, please let me know. -- From: Eric Dumazet [ Upstream commit 8b485ce69876c65db12ed390e7f9c0d2a64eff2c ] Under fuzzer stress, it is possible that a child gets a non NULL fastopen_req pointer from its

[PATCH 4.11 16/28] tcp: do not inherit fastopen_req from parent

4.11-stable review patch. If anyone has any objections, please let me know. -- From: Eric Dumazet [ Upstream commit 8b485ce69876c65db12ed390e7f9c0d2a64eff2c ] Under fuzzer stress, it is possible that a child gets a non NULL fastopen_req pointer from its parent at accept()

[PATCH 4.11 17/28] ipv4, ipv6: ensure raw socket message is big enough to hold an IP header

4.11-stable review patch. If anyone has any objections, please let me know. -- From: Alexander Potapenko [ Upstream commit 86f4c90a1c5c1493f07f2d12c1079f5bf01936f2 ] raw_send_hdrinc() and rawv6_send_hdrinc() expect that the buffer copied from the userspace

Re: [PATCH v2 1/2] net: Added mtu parameter to dev_forward_skb calls

On Thu, 11 May 2017 15:46:27 +0200 Fredrik Markstrom wrote: > From: Fredrik Markström > > is_skb_forwardable() currently checks if the packet size is <= mtu of > the receiving interface. This is not consistent with most of the hardware

[PATCH 4.11 17/28] ipv4, ipv6: ensure raw socket message is big enough to hold an IP header

4.11-stable review patch. If anyone has any objections, please let me know. -- From: Alexander Potapenko [ Upstream commit 86f4c90a1c5c1493f07f2d12c1079f5bf01936f2 ] raw_send_hdrinc() and rawv6_send_hdrinc() expect that the buffer copied from the userspace contains the

Re: [PATCH v2 1/2] net: Added mtu parameter to dev_forward_skb calls

On Thu, 11 May 2017 15:46:27 +0200 Fredrik Markstrom wrote: > From: Fredrik Markström > > is_skb_forwardable() currently checks if the packet size is <= mtu of > the receiving interface. This is not consistent with most of the hardware > ethernet drivers that happily receives packets larger

[PATCH 4.11 18/28] rtnetlink: NUL-terminate IFLA_PHYS_PORT_NAME string

4.11-stable review patch. If anyone has any objections, please let me know. -- From: Michal Schmidt [ Upstream commit 77ef033b687c3e030017c94a29bf6ea3aaaef678 ] IFLA_PHYS_PORT_NAME is a string attribute, so terminate it with \0. Otherwise libnl3 fails to

[PATCH 4.11 08/28] net: macb: fix phy interrupt parsing

4.11-stable review patch. If anyone has any objections, please let me know. -- From: Alexandre Belloni [ Upstream commit ae3696c167cc04d32634c4af82f43b446c5176b0 ] Since 83a77e9ec415, the phydev irq is explicitly set to PHY_POLL when

[PATCH 4.11 08/28] net: macb: fix phy interrupt parsing

4.11-stable review patch. If anyone has any objections, please let me know. -- From: Alexandre Belloni [ Upstream commit ae3696c167cc04d32634c4af82f43b446c5176b0 ] Since 83a77e9ec415, the phydev irq is explicitly set to PHY_POLL when there is no pdata. It doesn't work on DT

[PATCH 4.11 18/28] rtnetlink: NUL-terminate IFLA_PHYS_PORT_NAME string

4.11-stable review patch. If anyone has any objections, please let me know. -- From: Michal Schmidt [ Upstream commit 77ef033b687c3e030017c94a29bf6ea3aaaef678 ] IFLA_PHYS_PORT_NAME is a string attribute, so terminate it with \0. Otherwise libnl3 fails to validate netlink

[PATCH 4.11 12/28] bpf, arm64: fix jit branch offset related to ldimm64

4.11-stable review patch. If anyone has any objections, please let me know. -- From: Daniel Borkmann [ Upstream commit ddc665a4bb4b728b4e6ecec8db1b64efa9184b9c ] When the instruction right before the branch destination is a 64 bit load immediate, we

[PATCH 4.11 12/28] bpf, arm64: fix jit branch offset related to ldimm64

4.11-stable review patch. If anyone has any objections, please let me know. -- From: Daniel Borkmann [ Upstream commit ddc665a4bb4b728b4e6ecec8db1b64efa9184b9c ] When the instruction right before the branch destination is a 64 bit load immediate, we currently calculate the

[PATCH 4.11 06/28] sparc64: fix fault handling in NGbzero.S and GENbzero.S

4.11-stable review patch. If anyone has any objections, please let me know. -- From: Dave Aldridge commit 3c7f62212018b904ae17f5636ead18a4dca3a88f upstream. When any of the functions contained in NGbzero.S and GENbzero.S vector through

[PATCH 4.11 06/28] sparc64: fix fault handling in NGbzero.S and GENbzero.S

4.11-stable review patch. If anyone has any objections, please let me know. -- From: Dave Aldridge commit 3c7f62212018b904ae17f5636ead18a4dca3a88f upstream. When any of the functions contained in NGbzero.S and GENbzero.S vector through *bzero_from_clear_user, we may end up

[PATCH 4.11 00/28] 4.11.1-stable review

This is the start of the stable review cycle for the 4.11.1 release. There are 28 patches in this series, all will be posted as a response to this one. If anyone has any issues with these being applied, please let me know. Responses should be made by Sat May 13 14:12:05 UTC 2017. Anything

[PATCH 4.11 00/28] 4.11.1-stable review

This is the start of the stable review cycle for the 4.11.1 release. There are 28 patches in this series, all will be posted as a response to this one. If anyone has any issues with these being applied, please let me know. Responses should be made by Sat May 13 14:12:05 UTC 2017. Anything

[PATCH 4.11 09/28] tcp: fix access to sk->sk_state in tcp_poll()

4.11-stable review patch. If anyone has any objections, please let me know. -- From: Davide Caratti [ Upstream commit d68be71ea14d609a5f31534003319be5db422595 ] avoid direct access to sk->sk_state when tcp_poll() is called on a socket using active TCP

[PATCH 4.11 09/28] tcp: fix access to sk->sk_state in tcp_poll()

4.11-stable review patch. If anyone has any objections, please let me know. -- From: Davide Caratti [ Upstream commit d68be71ea14d609a5f31534003319be5db422595 ] avoid direct access to sk->sk_state when tcp_poll() is called on a socket using active TCP fastopen with deferred

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