KASAN: use-after-free Read in tipc_nametbl_stop

Hello, syzbot hit the following crash on net-next commit 5d1365940a68dd57b031b6e3c07d7d451cd69daf (Thu Apr 12 18:09:05 2018 +) Merge git://git.kernel.org/pub/scm/linux/kernel/git/davem/net syzbot dashboard link: https://syzkaller.appspot.com/bug?extid=d64b64afc55660106556 So far this

KASAN: use-after-free Read in tipc_nametbl_stop

Hello, syzbot hit the following crash on net-next commit 5d1365940a68dd57b031b6e3c07d7d451cd69daf (Thu Apr 12 18:09:05 2018 +) Merge git://git.kernel.org/pub/scm/linux/kernel/git/davem/net syzbot dashboard link: https://syzkaller.appspot.com/bug?extid=d64b64afc55660106556 So far this

Wrong module .text address in 4.16.0

I just installed 4.16.0 and discovered the module .text address is wrong. It happens on s390 and x86 platforms. I have not tested others. Here is the issue, I have used module qeth_l2 on s390 which is the ethernet device driver: root@s35lp76 ~]# lsmod Module Size Used by

Wrong module .text address in 4.16.0

I just installed 4.16.0 and discovered the module .text address is wrong. It happens on s390 and x86 platforms. I have not tested others. Here is the issue, I have used module qeth_l2 on s390 which is the ethernet device driver: root@s35lp76 ~]# lsmod Module Size Used by

Re: [PATCH v13 6/6] PCI/DPC: Do not do recovery for hotplug enabled system

On 2018-04-16 11:03, p...@codeaurora.org wrote: On 2018-04-16 08:47, Bjorn Helgaas wrote: On Sat, Apr 14, 2018 at 11:53:17AM -0400, Sinan Kaya wrote: You indicated that you want to unify the AER and DPC behavior. Let's settle on what we want to do one more time. We have been going forth and

Re: [PATCH v13 6/6] PCI/DPC: Do not do recovery for hotplug enabled system

On 2018-04-16 11:03, p...@codeaurora.org wrote: On 2018-04-16 08:47, Bjorn Helgaas wrote: On Sat, Apr 14, 2018 at 11:53:17AM -0400, Sinan Kaya wrote: You indicated that you want to unify the AER and DPC behavior. Let's settle on what we want to do one more time. We have been going forth and

Re: [PATCH v13 6/6] PCI/DPC: Do not do recovery for hotplug enabled system

On 2018-04-16 08:47, Bjorn Helgaas wrote: On Sat, Apr 14, 2018 at 11:53:17AM -0400, Sinan Kaya wrote: You indicated that you want to unify the AER and DPC behavior. Let's settle on what we want to do one more time. We have been going forth and back on the direction. My thinking is that as

linux-next: Tree for Apr 16

Hi all, Changes since 20180413: The bpf tree gained a build failure for which I applied a patch. Non-merge commits (relative to Linus' tree): 379 366 files changed, 7652 insertions(+), 4560 deletions(-) I have

Re: [PATCH v13 6/6] PCI/DPC: Do not do recovery for hotplug enabled system

On 2018-04-16 08:47, Bjorn Helgaas wrote: On Sat, Apr 14, 2018 at 11:53:17AM -0400, Sinan Kaya wrote: You indicated that you want to unify the AER and DPC behavior. Let's settle on what we want to do one more time. We have been going forth and back on the direction. My thinking is that as

linux-next: Tree for Apr 16

Hi all, Changes since 20180413: The bpf tree gained a build failure for which I applied a patch. Non-merge commits (relative to Linus' tree): 379 366 files changed, 7652 insertions(+), 4560 deletions(-) I have

Re: [PATCHv5] gpio: Remove VLA from gpiolib

On 16/04/2018 13:19, Phil Reid wrote: G'day Laura, One more comment. On 16/04/2018 12:41, Phil Reid wrote: G'day Laura, On 14/04/2018 05:24, Laura Abbott wrote: The new challenge is to remove VLAs from the kernel (see https://lkml.org/lkml/2018/3/7/621) to eventually turn on -Wvla. Using a

Re: [PATCHv5] gpio: Remove VLA from gpiolib

On 16/04/2018 13:19, Phil Reid wrote: G'day Laura, One more comment. On 16/04/2018 12:41, Phil Reid wrote: G'day Laura, On 14/04/2018 05:24, Laura Abbott wrote: The new challenge is to remove VLAs from the kernel (see https://lkml.org/lkml/2018/3/7/621) to eventually turn on -Wvla. Using a

[PATCH] mailbox: arm_mhu: add support for mhuv2

ARM has launched a next version of MHU i.e. MHUv2 with its latest subsystems. The main change is that the MHUv2 is now a distributed IP with different peripheral views (registers) for the sender and receiver. Another main difference is that MHUv1 duplex channels are now split into simplex/half

[PATCH] mailbox: arm_mhu: add support for mhuv2

ARM has launched a next version of MHU i.e. MHUv2 with its latest subsystems. The main change is that the MHUv2 is now a distributed IP with different peripheral views (registers) for the sender and receiver. Another main difference is that MHUv1 duplex channels are now split into simplex/half

Re: [PATCHv5] gpio: Remove VLA from gpiolib

G'day Laura, One more comment. On 16/04/2018 12:41, Phil Reid wrote: G'day Laura, On 14/04/2018 05:24, Laura Abbott wrote: The new challenge is to remove VLAs from the kernel (see https://lkml.org/lkml/2018/3/7/621) to eventually turn on -Wvla. Using a kmalloc array is the easy way to fix

Re: [PATCHv5] gpio: Remove VLA from gpiolib

G'day Laura, One more comment. On 16/04/2018 12:41, Phil Reid wrote: G'day Laura, On 14/04/2018 05:24, Laura Abbott wrote: The new challenge is to remove VLAs from the kernel (see https://lkml.org/lkml/2018/3/7/621) to eventually turn on -Wvla. Using a kmalloc array is the easy way to fix

Re: [PATCH v4 08/15] KVM: s390: interfaces to (de)configure guest's AP matrix

Hi Tony, I love your patch! Yet something to improve: [auto build test ERROR on s390/features] [also build test ERROR on v4.17-rc1 next-20180413] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url:

Re: [PATCH v4 08/15] KVM: s390: interfaces to (de)configure guest's AP matrix

Hi Tony, I love your patch! Yet something to improve: [auto build test ERROR on s390/features] [also build test ERROR on v4.17-rc1 next-20180413] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url:

nds32 build failures

I thought I should give the brand new architecture a try. Unfortunately, that was not very successful. Build reference: v4.17-rc1 gcc version: nds32le-elf-gcc (GCC) 7.3.0 Building nds32:defconfig ... failed arch/nds32/include/asm/nds32.h: In function 'GIE_ENABLE':

nds32 build failures

I thought I should give the brand new architecture a try. Unfortunately, that was not very successful. Build reference: v4.17-rc1 gcc version: nds32le-elf-gcc (GCC) 7.3.0 Building nds32:defconfig ... failed arch/nds32/include/asm/nds32.h: In function 'GIE_ENABLE':

Re: [linux-sunxi] [PATCH v2 00/10] Allwinner H3 DVFS support

On Mon, Apr 16, 2018 at 12:41 PM, Chen-Yu Tsai wrote: > Hi, > > On Tue, Feb 6, 2018 at 12:48 PM, Icenowy Zheng wrote: >> This patchset tries to add DVFS support for Allwinner H3 SoC, >> considering two kinds of adjustable regulators used on H3 boards: >> SY8106A

Re: [linux-sunxi] [PATCH v2 00/10] Allwinner H3 DVFS support

On Mon, Apr 16, 2018 at 12:41 PM, Chen-Yu Tsai wrote: > Hi, > > On Tue, Feb 6, 2018 at 12:48 PM, Icenowy Zheng wrote: >> This patchset tries to add DVFS support for Allwinner H3 SoC, >> considering two kinds of adjustable regulators used on H3 boards: >> SY8106A I2C-controlled regulator and

Re: [PATCHv5] gpio: Remove VLA from gpiolib

G'day Laura, On 14/04/2018 05:24, Laura Abbott wrote: The new challenge is to remove VLAs from the kernel (see https://lkml.org/lkml/2018/3/7/621) to eventually turn on -Wvla. Using a kmalloc array is the easy way to fix this but kmalloc is still more expensive than stack allocation. Introduce

Re: [PATCHv5] gpio: Remove VLA from gpiolib

G'day Laura, On 14/04/2018 05:24, Laura Abbott wrote: The new challenge is to remove VLAs from the kernel (see https://lkml.org/lkml/2018/3/7/621) to eventually turn on -Wvla. Using a kmalloc array is the easy way to fix this but kmalloc is still more expensive than stack allocation. Introduce

Re: [linux-sunxi] [PATCH v2 00/10] Allwinner H3 DVFS support

Hi, On Tue, Feb 6, 2018 at 12:48 PM, Icenowy Zheng wrote: > This patchset tries to add DVFS support for Allwinner H3 SoC, > considering two kinds of adjustable regulators used on H3 boards: > SY8106A I2C-controlled regulator and SY8113B regulator (controllable > by GPIO with

Re: [linux-sunxi] [PATCH v2 00/10] Allwinner H3 DVFS support

Hi, On Tue, Feb 6, 2018 at 12:48 PM, Icenowy Zheng wrote: > This patchset tries to add DVFS support for Allwinner H3 SoC, > considering two kinds of adjustable regulators used on H3 boards: > SY8106A I2C-controlled regulator and SY8113B regulator (controllable > by GPIO with some special designs

Re: [PATCH v3 4/4] mm/sparse: Optimize memmap allocation during sparse_init()

On 04/14/2018 07:19 PM, Baoquan He wrote: >>> Yes, this place is the hardest to understand. The temorary arrays are >>> allocated beforehand with the size of 'nr_present_sections'. The error >>> paths you mentioned is caused by allocation failure of mem_map or >>> map_map, but whatever it's error

Re: [PATCH v3 4/4] mm/sparse: Optimize memmap allocation during sparse_init()

On 04/14/2018 07:19 PM, Baoquan He wrote: >>> Yes, this place is the hardest to understand. The temorary arrays are >>> allocated beforehand with the size of 'nr_present_sections'. The error >>> paths you mentioned is caused by allocation failure of mem_map or >>> map_map, but whatever it's error

Re: [PATCH v5 1/3] regulator: axp20x: add drivevbus support for axp803

On Thu, Apr 5, 2018 at 2:46 PM, Maxime Ripard wrote: > On Thu, Apr 05, 2018 at 12:11:39PM +0530, Jagan Teki wrote: >> On Tue, Mar 27, 2018 at 11:01 AM, Jagan Teki >> wrote: >> > Like axp221, axp223, axp813 the axp803 is also supporting

Re: [PATCH v5 1/3] regulator: axp20x: add drivevbus support for axp803

On Thu, Apr 5, 2018 at 2:46 PM, Maxime Ripard wrote: > On Thu, Apr 05, 2018 at 12:11:39PM +0530, Jagan Teki wrote: >> On Tue, Mar 27, 2018 at 11:01 AM, Jagan Teki >> wrote: >> > Like axp221, axp223, axp813 the axp803 is also supporting external >> > regulator to drive the OTG VBus through

Re: [PATCH] mtd: nand: mtk: use of_device_get_match_data()

On Mon, 2018-04-16 at 10:33 +0800, Ryder Lee wrote: > The usage of of_device_get_match_data() reduce the code size a bit. > > Also, the only way to call .probe() is to match an entry in > .of_match_table[], so of_device_id cannot be NULL. > > Signed-off-by: Ryder Lee >

Re: [PATCH] mtd: nand: mtk: use of_device_get_match_data()

On Mon, 2018-04-16 at 10:33 +0800, Ryder Lee wrote: > The usage of of_device_get_match_data() reduce the code size a bit. > > Also, the only way to call .probe() is to match an entry in > .of_match_table[], so of_device_id cannot be NULL. > > Signed-off-by: Ryder Lee > --- >

Re: [PATCH] printk: Ratelimit messages printed by console drivers

On (04/16/18 10:47), Sergey Senozhatsky wrote: > On (04/14/18 11:35), Sergey Senozhatsky wrote: > > On (04/13/18 10:12), Steven Rostedt wrote: > > > > > > > The interval is set to one hour. It is rather arbitrary selected time. > > > > It is supposed to be a compromise between never print these

Re: [PATCH v4 4/4] zram: introduce zram memory tracking

On Sun, Apr 15, 2018 at 09:17:45PM -0700, Randy Dunlap wrote: > On 04/15/2018 08:31 PM, Minchan Kim wrote: > > zRam as swap is useful for small memory device. However, swap means > > those pages on zram are mostly cold pages due to VM's LRU algorithm. > > Especially, once init data for application

Re: [PATCH] printk: Ratelimit messages printed by console drivers

On (04/16/18 10:47), Sergey Senozhatsky wrote: > On (04/14/18 11:35), Sergey Senozhatsky wrote: > > On (04/13/18 10:12), Steven Rostedt wrote: > > > > > > > The interval is set to one hour. It is rather arbitrary selected time. > > > > It is supposed to be a compromise between never print these

Re: [PATCH v4 4/4] zram: introduce zram memory tracking

On Sun, Apr 15, 2018 at 09:17:45PM -0700, Randy Dunlap wrote: > On 04/15/2018 08:31 PM, Minchan Kim wrote: > > zRam as swap is useful for small memory device. However, swap means > > those pages on zram are mostly cold pages due to VM's LRU algorithm. > > Especially, once init data for application

[PATCH] perf tools: set kernel end address properly

The map_groups__fixup_end() was called to set end addresses of kernel map and module maps. But now machine__create_modules() is set the end address of modules properly so the only remaining piece is the kernel map. We can set it with adjacent module's address directly instead of calling the

[PATCH] perf tools: set kernel end address properly

The map_groups__fixup_end() was called to set end addresses of kernel map and module maps. But now machine__create_modules() is set the end address of modules properly so the only remaining piece is the kernel map. We can set it with adjacent module's address directly instead of calling the

[PATCH 05/25] staging: lustre: libcfs: remove excess space

From: Amir Shehata The function cfs_cpt_table_print() was adding two spaces to the string buffer. Just add it once. Signed-off-by: Amir Shehata Intel-bug-id: https://jira.hpdd.intel.com/browse/LU-7734 Reviewed-on:

[PATCH 02/22] staging: lustre: obd: create it_has_reply_body()

From: Vitaly Fertman The lookup_intent it_op fields in many cases will be compared to the settings of IT_OPEN | IT_UNLINK | IT_LOOKUP | IT_GETATTR. Create a simple inline function for this common case. Signed-off-by: Vitaly Fertman

[PATCH 05/25] staging: lustre: libcfs: remove excess space

From: Amir Shehata The function cfs_cpt_table_print() was adding two spaces to the string buffer. Just add it once. Signed-off-by: Amir Shehata Intel-bug-id: https://jira.hpdd.intel.com/browse/LU-7734 Reviewed-on: http://review.whamcloud.com/18916 Reviewed-by: Olaf Weber Reviewed-by: Doug

[PATCH 02/22] staging: lustre: obd: create it_has_reply_body()

From: Vitaly Fertman The lookup_intent it_op fields in many cases will be compared to the settings of IT_OPEN | IT_UNLINK | IT_LOOKUP | IT_GETATTR. Create a simple inline function for this common case. Signed-off-by: Vitaly Fertman Intel-bug-id: https://jira.hpdd.intel.com/browse/LU-7433

[PATCH 04/22] staging: lustre: ldlm: xattr locks are lost on mdt

From: Vitaly Fertman On the server side mdt_intent_getxattr() can return EFAULT if a buffer cannot be found, it is returned after lock_replace, where a new lock is installed into lockp. An error forces ldlm_lock_enqueue() to destroy the original lock, but

[PATCH 01/22] staging: lustre: llite: initialize xattr->xe_namelen

When the allocation of xattr->xe_name was moved to kstrdup() setting xattr->xe_namelen was dropped. This field is used in several parts of the xattr cache code so it broke xattr handling. Initialize xattr->xe_namelen when allocating xattr->xe_name succeeds. Also change the debugging statement to

[PATCH 00/22] staging: lustre: llite: fix xattr handling

From: James Simmons Lustre utilities and user land APIs heavly depend on special xattr handling. Sadly much of the xattr handling for lustre client has been broken for awhile. This is all the fixes needed to make xattr handling work properly with the latest kernels. Bobi Jam

[PATCH 04/22] staging: lustre: ldlm: xattr locks are lost on mdt

From: Vitaly Fertman On the server side mdt_intent_getxattr() can return EFAULT if a buffer cannot be found, it is returned after lock_replace, where a new lock is installed into lockp. An error forces ldlm_lock_enqueue() to destroy the original lock, but ldlm_handle_enqueue0() drops the

[PATCH 01/22] staging: lustre: llite: initialize xattr->xe_namelen

When the allocation of xattr->xe_name was moved to kstrdup() setting xattr->xe_namelen was dropped. This field is used in several parts of the xattr cache code so it broke xattr handling. Initialize xattr->xe_namelen when allocating xattr->xe_name succeeds. Also change the debugging statement to

[PATCH 00/22] staging: lustre: llite: fix xattr handling

From: James Simmons Lustre utilities and user land APIs heavly depend on special xattr handling. Sadly much of the xattr handling for lustre client has been broken for awhile. This is all the fixes needed to make xattr handling work properly with the latest kernels. Bobi Jam (3): staging:

[PATCH 07/22] staging: lustre: llite: refactor lustre.lov xattr handling

From: Niu Yawei The function ll_xattr_set() contains special code to handle the lustre specific xattr lustre.lov. Move all this code to a new function ll_setstripe_ea(). Signed-off-by: Bobi Jam Signed-off-by: Niu Yawei

[PATCH 05/22] staging: lustre: llite: handle xattr cache refill race

From: "John L. Hammond" In ll_xattr_cache_refill() if the xattr cache was invalid (and no request was sent) then return -EAGAIN so that ll_getxattr_common() caller will fetch the xattr from the MDT. Signed-off-by: John L. Hammond Intel-bug-id:

[PATCH 07/22] staging: lustre: llite: refactor lustre.lov xattr handling

From: Niu Yawei The function ll_xattr_set() contains special code to handle the lustre specific xattr lustre.lov. Move all this code to a new function ll_setstripe_ea(). Signed-off-by: Bobi Jam Signed-off-by: Niu Yawei Intel-bug-id: https://jira.hpdd.intel.com/browse/LU-8998 Reviewed-on:

[PATCH 05/22] staging: lustre: llite: handle xattr cache refill race

From: "John L. Hammond" In ll_xattr_cache_refill() if the xattr cache was invalid (and no request was sent) then return -EAGAIN so that ll_getxattr_common() caller will fetch the xattr from the MDT. Signed-off-by: John L. Hammond Intel-bug-id: https://jira.hpdd.intel.com/browse/LU-10132

[PATCH 10/22] staging: lustre: llite: return from ll_adjust_lum() if lump is NULL

From: Bobi Jam No need to check several times if lump is NULL. Just test once and return 0 if NULL. Signed-off-by: Bobi Jam Intel-bug-id: https://jira.hpdd.intel.com/browse/LU-9484 Reviewed-on: https://review.whamcloud.com/27126 Reviewed-by: Dmitry

Re: [PATCH v4 4/4] zram: introduce zram memory tracking

On 04/15/2018 08:31 PM, Minchan Kim wrote: > zRam as swap is useful for small memory device. However, swap means > those pages on zram are mostly cold pages due to VM's LRU algorithm. > Especially, once init data for application are touched for launching, > they tend to be not accessed any more

[PATCH 03/22] staging: lustre: obd: change debug reporting in lmv_enqueue()

From: Vitaly Fertman Remove LL_IT2STR(it) from debug macros in lmv_enqueue(). The removal makes it possible to simplify the md_enqueue() functions. Signed-off-by: Vitaly Fertman Intel-bug-id: https://jira.hpdd.intel.com/browse/LU-7433

[PATCH 10/22] staging: lustre: llite: return from ll_adjust_lum() if lump is NULL

From: Bobi Jam No need to check several times if lump is NULL. Just test once and return 0 if NULL. Signed-off-by: Bobi Jam Intel-bug-id: https://jira.hpdd.intel.com/browse/LU-9484 Reviewed-on: https://review.whamcloud.com/27126 Reviewed-by: Dmitry Eremin Reviewed-by: Niu Yawei Reviewed-by:

Re: [PATCH v4 4/4] zram: introduce zram memory tracking

On 04/15/2018 08:31 PM, Minchan Kim wrote: > zRam as swap is useful for small memory device. However, swap means > those pages on zram are mostly cold pages due to VM's LRU algorithm. > Especially, once init data for application are touched for launching, > they tend to be not accessed any more

[PATCH 03/22] staging: lustre: obd: change debug reporting in lmv_enqueue()

From: Vitaly Fertman Remove LL_IT2STR(it) from debug macros in lmv_enqueue(). The removal makes it possible to simplify the md_enqueue() functions. Signed-off-by: Vitaly Fertman Intel-bug-id: https://jira.hpdd.intel.com/browse/LU-7433 Seagate-bug-id: MRP-3072 MRP-3137 Reviewed-on:

[PATCH 06/22] staging: lustre: llite: Remove filtering of seclabel xattr

From: Robin Humble The security.capability xattr is used to implement File Capabilities in recent Linux versions. Capabilities are a fine grained approach to granting executables elevated privileges. eg. /bin/ping can have capabilities cap_net_admin, cap_net_raw+ep

[PATCH 09/22] staging: lustre: llite: break up ll_setstripe_ea function

From: Bobi Jam Place all the handling of information of trusted.lov that is not stripe related into the new function ll_adjust_lum(). Now ll_setstripe_ea() only handles striping information. Signed-off-by: Bobi Jam Intel-bug-id:

[PATCH 06/22] staging: lustre: llite: Remove filtering of seclabel xattr

From: Robin Humble The security.capability xattr is used to implement File Capabilities in recent Linux versions. Capabilities are a fine grained approach to granting executables elevated privileges. eg. /bin/ping can have capabilities cap_net_admin, cap_net_raw+ep instead of being setuid root.

[PATCH 09/22] staging: lustre: llite: break up ll_setstripe_ea function

From: Bobi Jam Place all the handling of information of trusted.lov that is not stripe related into the new function ll_adjust_lum(). Now ll_setstripe_ea() only handles striping information. Signed-off-by: Bobi Jam Intel-bug-id: https://jira.hpdd.intel.com/browse/LU-9484 Reviewed-on:

[PATCH 14/22] staging: lustre: llite: record in stats attempted removal of lma/link xattr

Keep track of attempted deletions as well as changing of the lma/link xattrs. Signed-off-by: James Simmons Intel-bug-id: https://jira.hpdd.intel.com/browse/LU-9183 Reviewed-on: https://review.whamcloud.com/27240 Reviewed-by: Dmitry Eremin

[PATCH 14/22] staging: lustre: llite: record in stats attempted removal of lma/link xattr

Keep track of attempted deletions as well as changing of the lma/link xattrs. Signed-off-by: James Simmons Intel-bug-id: https://jira.hpdd.intel.com/browse/LU-9183 Reviewed-on: https://review.whamcloud.com/27240 Reviewed-by: Dmitry Eremin Reviewed-by: Bob Glossman Reviewed-by: Sebastien

[PATCH 12/22] staging: lustre: llite: fix invalid size test in ll_setstripe_ea()

The size check at the start of ll_setstripe_ea() is only valid for a directory. Move that check to the section of code handling the S_ISDIR case. Signed-off-by: James Simmons Intel-bug-id: https://jira.hpdd.intel.com/browse/LU-9183 Reviewed-on:

[PATCH 08/22] staging: lustre: llite: add simple comment about lustre.lov xattrs

From: Niu Yawei Simple comment added to ll_xattr_set. Signed-off-by: Bobi Jam Signed-off-by: Niu Yawei Intel-bug-id: https://jira.hpdd.intel.com/browse/LU-8998 Reviewed-on: https://review.whamcloud.com/24851 Reviewed-by: Andreas

[PATCH 11/22] staging: lustre: llite: eat -EEXIST on setting trusted.lov

From: Bobi Jam Tools like rsync, tar, cp may copy and restore the xattrs on a file. The client previously ignored the setting of trusted.lov/lustre.lov if the layout had already been specified, to avoid causing these tools to fail for no reason. For PFL files we still need

[PATCH 12/22] staging: lustre: llite: fix invalid size test in ll_setstripe_ea()

The size check at the start of ll_setstripe_ea() is only valid for a directory. Move that check to the section of code handling the S_ISDIR case. Signed-off-by: James Simmons Intel-bug-id: https://jira.hpdd.intel.com/browse/LU-9183 Reviewed-on: https://review.whamcloud.com/27240 Reviewed-by:

[PATCH 08/22] staging: lustre: llite: add simple comment about lustre.lov xattrs

From: Niu Yawei Simple comment added to ll_xattr_set. Signed-off-by: Bobi Jam Signed-off-by: Niu Yawei Intel-bug-id: https://jira.hpdd.intel.com/browse/LU-8998 Reviewed-on: https://review.whamcloud.com/24851 Reviewed-by: Andreas Dilger Reviewed-by: Lai Siyao Reviewed-by: Jinshan Xiong

[PATCH 11/22] staging: lustre: llite: eat -EEXIST on setting trusted.lov

From: Bobi Jam Tools like rsync, tar, cp may copy and restore the xattrs on a file. The client previously ignored the setting of trusted.lov/lustre.lov if the layout had already been specified, to avoid causing these tools to fail for no reason. For PFL files we still need to silently eat

[PATCH 13/22] staging: lustre: llite: remove newline in fullname strings

In creating the full name of a xattr a new line was added that was seen by the remote MDS server which confused it. Remove the newline. Signed-off-by: James Simmons Intel-bug-id: https://jira.hpdd.intel.com/browse/LU-9183 Reviewed-on: https://review.whamcloud.com/27240

[PATCH 13/22] staging: lustre: llite: remove newline in fullname strings

In creating the full name of a xattr a new line was added that was seen by the remote MDS server which confused it. Remove the newline. Signed-off-by: James Simmons Intel-bug-id: https://jira.hpdd.intel.com/browse/LU-9183 Reviewed-on: https://review.whamcloud.com/27240 Reviewed-by: Dmitry Eremin

[PATCH 19/22] staging: lustre: llite: add support set_acl method in inode operations

From: Dmitry Eremin Linux kernel v3.14 adds set_acl method to inode operations. This patch adds support to Lustre for proper acl management. Signed-off-by: Dmitry Eremin Signed-off-by: John L. Hammond Intel-bug-id:

[PATCH 19/22] staging: lustre: llite: add support set_acl method in inode operations

From: Dmitry Eremin Linux kernel v3.14 adds set_acl method to inode operations. This patch adds support to Lustre for proper acl management. Signed-off-by: Dmitry Eremin Signed-off-by: John L. Hammond Intel-bug-id: https://jira.hpdd.intel.com/browse/LU-9183 Reviewed-on:

[PATCH 20/22] staging: lustre: llite: use xattr_handler name for ACLs

From: "John L. Hammond" If struct xattr_handler has a name member then use it (rather than prefix) for the ACL xattrs. This avoids a bug where ACL operations failed for some kernels. Signed-off-by: John L. Hammond Intel-bug-id:

[PATCH 20/22] staging: lustre: llite: use xattr_handler name for ACLs

From: "John L. Hammond" If struct xattr_handler has a name member then use it (rather than prefix) for the ACL xattrs. This avoids a bug where ACL operations failed for some kernels. Signed-off-by: John L. Hammond Intel-bug-id: https://jira.hpdd.intel.com/browse/LU-10785 Reviewed-on:

[PATCH 18/22] staging: lustre: llite: style changes in xattr.c

Small style changes to match more the kernel code standard and it make it more readable. Signed-off-by: James Simmons Intel-bug-id: https://jira.hpdd.intel.com/browse/LU-9183 Reviewed-on: https://review.whamcloud.com/27240 Reviewed-by: Dmitry Eremin

[PATCH 16/22] staging: lustre: llite: use proper types in the xattr code

Convert __uXX types to uXX types since this is kernel code. The function ll_lov_user_md_size() returns ssize_t so change lum_size from int to ssize_t. Signed-off-by: James Simmons Intel-bug-id: https://jira.hpdd.intel.com/browse/LU-9183 Reviewed-on:

[PATCH 18/22] staging: lustre: llite: style changes in xattr.c

Small style changes to match more the kernel code standard and it make it more readable. Signed-off-by: James Simmons Intel-bug-id: https://jira.hpdd.intel.com/browse/LU-9183 Reviewed-on: https://review.whamcloud.com/27240 Reviewed-by: Dmitry Eremin Reviewed-by: Bob Glossman Reviewed-by:

[PATCH 16/22] staging: lustre: llite: use proper types in the xattr code

Convert __uXX types to uXX types since this is kernel code. The function ll_lov_user_md_size() returns ssize_t so change lum_size from int to ssize_t. Signed-off-by: James Simmons Intel-bug-id: https://jira.hpdd.intel.com/browse/LU-9183 Reviewed-on: https://review.whamcloud.com/27240

[PATCH 17/22] staging: lustre: llite: cleanup xattr code comments

Add proper punctuation to the comments. Change buf_size to size for comment in ll_listxattr() since buf_size doesn't exit which will confuse someone reading the code. Signed-off-by: James Simmons Intel-bug-id: https://jira.hpdd.intel.com/browse/LU-9183 Reviewed-on:

[PATCH 17/22] staging: lustre: llite: cleanup xattr code comments

Add proper punctuation to the comments. Change buf_size to size for comment in ll_listxattr() since buf_size doesn't exit which will confuse someone reading the code. Signed-off-by: James Simmons Intel-bug-id: https://jira.hpdd.intel.com/browse/LU-9183 Reviewed-on:

[PATCH 21/22] staging: lustre: llite: correct removexattr detection

In ll_xattr_set_common() detect the removexattr() case correctly by testing for a NULL value as well as XATTR_REPLACE. Signed-off-by: John L. Hammond Intel-bug-id: https://jira.hpdd.intel.com/browse/LU-10787 Reviewed-on: https://review.whamcloud.com/ Reviewed-by: Dmitry

[PATCH 21/22] staging: lustre: llite: correct removexattr detection

In ll_xattr_set_common() detect the removexattr() case correctly by testing for a NULL value as well as XATTR_REPLACE. Signed-off-by: John L. Hammond Intel-bug-id: https://jira.hpdd.intel.com/browse/LU-10787 Reviewed-on: https://review.whamcloud.com/ Reviewed-by: Dmitry Eremin Reviewed-by:

[PATCH 22/22] staging: lustre: llite: remove unused parameters from md_{get,set}xattr()

From: "John L. Hammond" md_getxattr() and md_setxattr() each have several unused parameters. Remove them and improve the naming or remaining parameters. Signed-off-by: John L. Hammond Intel-bug-id: https://jira.hpdd.intel.com/browse/LU-10792

[PATCH 22/22] staging: lustre: llite: remove unused parameters from md_{get,set}xattr()

From: "John L. Hammond" md_getxattr() and md_setxattr() each have several unused parameters. Remove them and improve the naming or remaining parameters. Signed-off-by: John L. Hammond Intel-bug-id: https://jira.hpdd.intel.com/browse/LU-10792 Reviewed-on: https://review.whamcloud.com/

[PATCH 15/22] staging: lustre: llite: cleanup posix acl xattr code

Having an extra ifdef makes the code harder to read. For the case of ll_xattr_get_common() we have a variable initialized at the start of the function but it is only used in XATTR_ACL_ACCESS_T code block. Lets move that variable to that location since its only used there and make the code look

[PATCH 15/22] staging: lustre: llite: cleanup posix acl xattr code

Having an extra ifdef makes the code harder to read. For the case of ll_xattr_get_common() we have a variable initialized at the start of the function but it is only used in XATTR_ACL_ACCESS_T code block. Lets move that variable to that location since its only used there and make the code look

[PATCH 01/25] staging: lustre: libcfs: remove useless CPU partition code

From: Dmitry Eremin * remove scratch buffer and mutex which guard it. * remove global cpumask and spinlock which guard it. * remove cpt_version for checking CPUs state change during setup because of just disable CPUs state change during setup. * remove whole global

[PATCH 01/25] staging: lustre: libcfs: remove useless CPU partition code

From: Dmitry Eremin * remove scratch buffer and mutex which guard it. * remove global cpumask and spinlock which guard it. * remove cpt_version for checking CPUs state change during setup because of just disable CPUs state change during setup. * remove whole global struct cfs_cpt_data

[PATCH 03/25] staging: lustre: libcfs: implement cfs_cpt_cpumask for UMP case

From: Amir Shehata The function cfs_cpt_cpumask() exist for SMP systems but when CONFIG_SMP is disabled it only returns NULL. Fill in this missing function. Also properly initialize ctb_mask for the UMP case. Signed-off-by: Amir Shehata

[PATCH 06/25] staging: lustre: libcfs: replace num_possible_cpus() with nr_cpu_ids

From: Amir Shehata Move from num_possible_cpus() to nr_cpu_ids. Signed-off-by: Amir Shehata Intel-bug-id: https://jira.hpdd.intel.com/browse/LU-7734 Reviewed-on: http://review.whamcloud.com/18916 Reviewed-by: Olaf Weber

[PATCH 08/25] staging: lustre: libcfs: add cpu distance handling

From: Amir Shehata Add functionality to calculate the distance between two CPTs. Expose those distance in debugfs so people deploying a setup can debug what is being created for CPTs. Signed-off-by: Amir Shehata Intel-bug-id:

[PATCH 03/25] staging: lustre: libcfs: implement cfs_cpt_cpumask for UMP case

From: Amir Shehata The function cfs_cpt_cpumask() exist for SMP systems but when CONFIG_SMP is disabled it only returns NULL. Fill in this missing function. Also properly initialize ctb_mask for the UMP case. Signed-off-by: Amir Shehata Intel-bug-id: https://jira.hpdd.intel.com/browse/LU-7734

[PATCH 06/25] staging: lustre: libcfs: replace num_possible_cpus() with nr_cpu_ids

From: Amir Shehata Move from num_possible_cpus() to nr_cpu_ids. Signed-off-by: Amir Shehata Intel-bug-id: https://jira.hpdd.intel.com/browse/LU-7734 Reviewed-on: http://review.whamcloud.com/18916 Reviewed-by: Olaf Weber Reviewed-by: Doug Oucharek Signed-off-by: James Simmons ---

[PATCH 08/25] staging: lustre: libcfs: add cpu distance handling

From: Amir Shehata Add functionality to calculate the distance between two CPTs. Expose those distance in debugfs so people deploying a setup can debug what is being created for CPTs. Signed-off-by: Amir Shehata Intel-bug-id: https://jira.hpdd.intel.com/browse/LU-7734 Reviewed-on:

[PATCH 09/25] staging: lustre: libcfs: use distance in cpu and node handling

From: Amir Shehata Take into consideration the location of NUMA nodes and core when calling cfs_cpt_[un]set_cpu() and cfs_cpt_[un]set_node(). This enables functioning on platforms with 100s of cores and NUMA nodes. Signed-off-by: Amir Shehata

[PATCH 09/25] staging: lustre: libcfs: use distance in cpu and node handling

From: Amir Shehata Take into consideration the location of NUMA nodes and core when calling cfs_cpt_[un]set_cpu() and cfs_cpt_[un]set_node(). This enables functioning on platforms with 100s of cores and NUMA nodes. Signed-off-by: Amir Shehata Intel-bug-id:

[PATCH 11/25] staging: lustre: libcfs: invert error handling for cfs_cpt_table_print

From: Amir Shehata Instead of setting rc to -EFBIG for several cases in the loop lets initialize rc to -EFBIG and just break out of the loop in case of failure. Just set rc to zero once we successfully finish the loop. Signed-off-by: Amir Shehata

[PATCH 11/25] staging: lustre: libcfs: invert error handling for cfs_cpt_table_print

From: Amir Shehata Instead of setting rc to -EFBIG for several cases in the loop lets initialize rc to -EFBIG and just break out of the loop in case of failure. Just set rc to zero once we successfully finish the loop. Signed-off-by: Amir Shehata Intel-bug-id:

  1   2   3   4   5   6   >