Re: "isert: isert_setup_id: rdma_bind_addr() failed: -19" spam, followed by Recursive Fault on reboot

Hello Hey Steve, I'm trying (failing) to get iSER working. After rebooting with some settings saved in targetcli, I got an endless stream of messages like this: [ 192.701299] isert: isert_setup_id: rdma_bind_addr() failed: -19 [ 192.702733] isert: isert_setup_id: rdma_bind_addr() failed:

Re: "isert: isert_setup_id: rdma_bind_addr() failed: -19" spam, followed by Recursive Fault on reboot

Hello Hey Steve, I'm trying (failing) to get iSER working. After rebooting with some settings saved in targetcli, I got an endless stream of messages like this: [ 192.701299] isert: isert_setup_id: rdma_bind_addr() failed: -19 [ 192.702733] isert: isert_setup_id: rdma_bind_addr() failed:

Re: [PATCH] Staging: omap4iss: fix coding style issues

28.01.2017, 20:11, "Avraham Shukron" : > This is a patch that fixes issues in omap4iss/iss_video.c > Specifically, it fixes "line over 80 characters" issues Hello, are you have a sent this changes patch before? And Greg KH answered you, are you read? Please send the

Re: [PATCH] Staging: omap4iss: fix coding style issues

28.01.2017, 20:11, "Avraham Shukron" : > This is a patch that fixes issues in omap4iss/iss_video.c > Specifically, it fixes "line over 80 characters" issues Hello, are you have a sent this changes patch before? And Greg KH answered you, are you read? Please send the change once, there is no

[RFC PATCH] scsi, block: fix duplicate bdi name registration crashes

Warnings of the following form occur because scsi reuses a devt number while the block layer still has it referenced as the name of the bdi [1]: WARNING: CPU: 1 PID: 93 at fs/sysfs/dir.c:31 sysfs_warn_dup+0x62/0x80 sysfs: cannot create duplicate filename '/devices/virtual/bdi/8:192' [..] Call

[RFC PATCH] scsi, block: fix duplicate bdi name registration crashes

Warnings of the following form occur because scsi reuses a devt number while the block layer still has it referenced as the name of the bdi [1]: WARNING: CPU: 1 PID: 93 at fs/sysfs/dir.c:31 sysfs_warn_dup+0x62/0x80 sysfs: cannot create duplicate filename '/devices/virtual/bdi/8:192' [..] Call

[PATCH 40/60] staging: ptlrpc: leaked rs on difficult reply

From: Niu Yawei reply_out_callback() should call ptlrpc_schedule_difficult_reply() to finalize the rs if it's already not on uncommitted list, otherwise, the rs and the export held by rs could be leaked: - target_send_reply() sends a difficult reply before the transaction

[PATCH 40/60] staging: ptlrpc: leaked rs on difficult reply

From: Niu Yawei reply_out_callback() should call ptlrpc_schedule_difficult_reply() to finalize the rs if it's already not on uncommitted list, otherwise, the rs and the export held by rs could be leaked: - target_send_reply() sends a difficult reply before the transaction committed, the reply

[tip:WIP.x86/boot 11/55] arch/x86/include/asm/xen/page.h:302:7: warning: 'struct device' declared inside parameter list

tree: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git WIP.x86/boot head: 0c6fc11ac343c82d4a2f8348fa6f829e07c12554 commit: 5520b7e7d2d20ae2ab6e07b46c42cd43df9d2799 [11/55] x86/boot/e820: Remove spurious asm/e820/api.h inclusions config: x86_64-randconfig-n0-01291212 (attached as

[tip:WIP.x86/boot 11/55] arch/x86/include/asm/xen/page.h:302:7: warning: 'struct device' declared inside parameter list

tree: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git WIP.x86/boot head: 0c6fc11ac343c82d4a2f8348fa6f829e07c12554 commit: 5520b7e7d2d20ae2ab6e07b46c42cd43df9d2799 [11/55] x86/boot/e820: Remove spurious asm/e820/api.h inclusions config: x86_64-randconfig-n0-01291212 (attached as

Re: [PATCH] f2fs: enhance lookup xattr

Hi Chao, On 01/24, Chao Yu wrote: ... > > - error = read_all_xattrs(inode, ipage, _addr); > + error = lookup_all_xattrs(inode, ipage, index, len, name, > + , _addr); > if (error) > return error; > > - entry =

Re: [PATCH] f2fs: enhance lookup xattr

Hi Chao, On 01/24, Chao Yu wrote: ... > > - error = read_all_xattrs(inode, ipage, _addr); > + error = lookup_all_xattrs(inode, ipage, index, len, name, > + , _addr); > if (error) > return error; > > - entry =

[PATCH] mips: audit and remove any unnecessary uses of module.h

Historically a lot of these existed because we did not have a distinction between what was modular code and what was providing support to modules via EXPORT_SYMBOL and friends. That changed when we forked out support for the latter into the export.h file. This means we should be able to reduce

[PATCH] mips: audit and remove any unnecessary uses of module.h

Historically a lot of these existed because we did not have a distinction between what was modular code and what was providing support to modules via EXPORT_SYMBOL and friends. That changed when we forked out support for the latter into the export.h file. This means we should be able to reduce

Re: [RFC PATCH 0/4] Fast noirq bulk page allocator v2r7

On 01/09/2017 08:35 AM, Mel Gorman wrote: The fourth patch introduces a bulk page allocator with no in-kernel users as an example for Jesper and others who want to build a page allocator for DMA-coherent pages. If you want an in-kernel user as a test, to validate the API's sanity, and to

Re: [RFC PATCH 0/4] Fast noirq bulk page allocator v2r7

On 01/09/2017 08:35 AM, Mel Gorman wrote: The fourth patch introduces a bulk page allocator with no in-kernel users as an example for Jesper and others who want to build a page allocator for DMA-coherent pages. If you want an in-kernel user as a test, to validate the API's sanity, and to

Re: [PATCH 0/2] blackfin: Remove dead DSA code

On 01/01/2017 02:42 PM, Florian Fainelli wrote: > Hi all, > > This patch series removes dead DSA code in the blackfin board specific > code. There is no in tree driver for the KSZ8893M, and clearly this > would not compile anymore. > > Preparatory patch to help remove the legacy DSA platform

Re: [PATCH 0/2] blackfin: Remove dead DSA code

On 01/01/2017 02:42 PM, Florian Fainelli wrote: > Hi all, > > This patch series removes dead DSA code in the blackfin board specific > code. There is no in tree driver for the KSZ8893M, and clearly this > would not compile anymore. > > Preparatory patch to help remove the legacy DSA platform

Re: [PATCH] ARM: dts: imx53-qsb-common: fix FEC pinmux config

On Wed, Jan 25, 2017 at 06:25:48AM +0100, linux-kernel-...@beckhoff.com wrote: > From: Patrick Bruenn > > The pinmux configuration in device tree was different from manual > muxing in /board/freescale/mx53loco/mx53loco.c > All pins were configured as NO_PAD_CTL(1 << 31),

Re: [PATCH] ARM: dts: imx53-qsb-common: fix FEC pinmux config

On Wed, Jan 25, 2017 at 06:25:48AM +0100, linux-kernel-...@beckhoff.com wrote: > From: Patrick Bruenn > > The pinmux configuration in device tree was different from manual > muxing in /board/freescale/mx53loco/mx53loco.c > All pins were configured as NO_PAD_CTL(1 << 31), which was fine as the >

[PATCH 47/60] staging: lustre: mdc: avoid returning freed request

From: "John L. Hammond" In mdc_close() if ptlrpc_request_pack() fails then set req to NULL so that an already freed request is not returned in *request. Signed-off-by: John L. Hammond Intel-bug-id: https://jira.hpdd.intel.com/browse/LU-8811

[PATCH 47/60] staging: lustre: mdc: avoid returning freed request

From: "John L. Hammond" In mdc_close() if ptlrpc_request_pack() fails then set req to NULL so that an already freed request is not returned in *request. Signed-off-by: John L. Hammond Intel-bug-id: https://jira.hpdd.intel.com/browse/LU-8811 Reviewed-on: https://review.whamcloud.com/23843

[PATCH 46/60] staging: lustre: mdc: Make IT_OPEN take lookup bits lock

From: Patrick Farrell An earlier commit accidentally changed handling of IT_OPEN, making it take the MDS_INODELOCK_UPDATE bits lock instead of MDS_INODELOCK_LOOKUP. This does not cause any known bugs. Signed-off-by: Patrick Farrell Intel-bug-id:

[PATCH 46/60] staging: lustre: mdc: Make IT_OPEN take lookup bits lock

From: Patrick Farrell An earlier commit accidentally changed handling of IT_OPEN, making it take the MDS_INODELOCK_UPDATE bits lock instead of MDS_INODELOCK_LOOKUP. This does not cause any known bugs. Signed-off-by: Patrick Farrell Intel-bug-id: https://jira.hpdd.intel.com/browse/LU-8842

[tip:WIP.x86/boot 51/55] arch/x86/kernel/e820.c:120:10-11: WARNING: return of 0/1 in function 'e820__mapped_all' with return type bool

tree: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git WIP.x86/boot head: 0c6fc11ac343c82d4a2f8348fa6f829e07c12554 commit: 81b3e090fa1f237d49c8feb2fa4afe2aabd3a4ff [51/55] x86/boot/e820: Use bool in query APIs coccinelle warnings: (new ones prefixed by >>) >>

[tip:WIP.x86/boot 51/55] arch/x86/kernel/e820.c:120:10-11: WARNING: return of 0/1 in function 'e820__mapped_all' with return type bool

tree: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git WIP.x86/boot head: 0c6fc11ac343c82d4a2f8348fa6f829e07c12554 commit: 81b3e090fa1f237d49c8feb2fa4afe2aabd3a4ff [51/55] x86/boot/e820: Use bool in query APIs coccinelle warnings: (new ones prefixed by >>) >>

RE: [PATCH v2 0/2] scsi: storvsc: Add support for FC lightweight host.

> -Original Message- > From: Christoph Hellwig [mailto:h...@infradead.org] > Sent: Thursday, January 26, 2017 6:52 AM > To: Cathy Avery > Cc: KY Srinivasan ; h...@infradead.org; Haiyang Zhang > ; j...@linux.vnet.ibm.com; >

RE: [PATCH v2 0/2] scsi: storvsc: Add support for FC lightweight host.

> -Original Message- > From: Christoph Hellwig [mailto:h...@infradead.org] > Sent: Thursday, January 26, 2017 6:52 AM > To: Cathy Avery > Cc: KY Srinivasan ; h...@infradead.org; Haiyang Zhang > ; j...@linux.vnet.ibm.com; > martin.peter...@oracle.com; dan.carpen...@oracle.com; >

[PATCH 38/60] staging: lustre: llite: Adding timed wait in ll_umount_begin

From: Rahul Deshmukh There exists timing race between umount and other thread which will increment the reference count on mnt e.g. getattr. If umount thread lose the race then umount fails with EBUSY error. To avoid this timed wait is added so that umount thread will

[PATCH 38/60] staging: lustre: llite: Adding timed wait in ll_umount_begin

From: Rahul Deshmukh There exists timing race between umount and other thread which will increment the reference count on mnt e.g. getattr. If umount thread lose the race then umount fails with EBUSY error. To avoid this timed wait is added so that umount thread will wait for user to decrement

[PATCH 32/50] x86/boot/e820: Create coherent API function names for E820 range operations

We have these three related functions: extern void e820_add_region(u64 start, u64 size, int type); extern u64 e820_update_range(u64 start, u64 size, unsigned old_type, unsigned new_type); extern u64 e820_remove_range(u64 start, u64 size, unsigned old_type, int checktype); But it's not

[PATCH 32/50] x86/boot/e820: Create coherent API function names for E820 range operations

We have these three related functions: extern void e820_add_region(u64 start, u64 size, int type); extern u64 e820_update_range(u64 start, u64 size, unsigned old_type, unsigned new_type); extern u64 e820_remove_range(u64 start, u64 size, unsigned old_type, int checktype); But it's not

[PATCH 42/50] xen, x86/boot/e820: Simplify Xen's xen_e820_table construct

The Xen guest memory setup code has: static struct e820_entry xen_e820_table[E820_MAX_ENTRIES] __initdata; static u32 xen_e820_table_entries __initdata; ... which is really a 'struct e820_table', open-coded. Convert the Xen code over to use a single struct e820_table, as this

[PATCH 42/50] xen, x86/boot/e820: Simplify Xen's xen_e820_table construct

The Xen guest memory setup code has: static struct e820_entry xen_e820_table[E820_MAX_ENTRIES] __initdata; static u32 xen_e820_table_entries __initdata; ... which is really a 'struct e820_table', open-coded. Convert the Xen code over to use a single struct e820_table, as this

Re: [PATCH 0/6] ncr5380: Miscellaneous minor patches

On Sat, 28 Jan 2017, Ondrej Zary wrote: > On Monday 16 January 2017 00:50:57 Finn Thain wrote: > > This series removes some unused code and related comments, addresses > > the warnings generated by 'make W=1' and 'make C=1' and fixes a > > theoretical bug in the bus reset method in atari_scsi.

Re: [PATCH 0/6] ncr5380: Miscellaneous minor patches

On Sat, 28 Jan 2017, Ondrej Zary wrote: > On Monday 16 January 2017 00:50:57 Finn Thain wrote: > > This series removes some unused code and related comments, addresses > > the warnings generated by 'make W=1' and 'make C=1' and fixes a > > theoretical bug in the bus reset method in atari_scsi.

Re: [PATCH v5 1/8] PCI: Recognize Thunderbolt devices

On Sat, Jan 28, 2017 at 03:52:08PM -0600, Bjorn Helgaas wrote: > On Sun, Jan 15, 2017 at 09:03:45PM +0100, Lukas Wunner wrote: > > We're about to allow runtime PM on Thunderbolt ports in > > pci_bridge_d3_possible() and unblock runtime PM for Thunderbolt host > > hotplug ports in

Re: [PATCH v5 1/8] PCI: Recognize Thunderbolt devices

On Sat, Jan 28, 2017 at 03:52:08PM -0600, Bjorn Helgaas wrote: > On Sun, Jan 15, 2017 at 09:03:45PM +0100, Lukas Wunner wrote: > > We're about to allow runtime PM on Thunderbolt ports in > > pci_bridge_d3_possible() and unblock runtime PM for Thunderbolt host > > hotplug ports in

[PATCH 44/60] staging: lustre: libcfs: fix error messages

From: Dmitry Eremin Don't treat unability to set CPU partition affinity as error. Improve those warning messages. Signed-off-by: Dmitry Eremin Intel-bug-id: https://jira.hpdd.intel.com/browse/LU-8703 Reviewed-on:

[PATCH 44/60] staging: lustre: libcfs: fix error messages

From: Dmitry Eremin Don't treat unability to set CPU partition affinity as error. Improve those warning messages. Signed-off-by: Dmitry Eremin Intel-bug-id: https://jira.hpdd.intel.com/browse/LU-8703 Reviewed-on: https://review.whamcloud.com/23307 Reviewed-by: Patrick Farrell Reviewed-by:

BUG at net/sctp/socket.c:7425

Hello, I'm running the syzkaller fuzzer for v4.10-rc4 (0aa0313f9d576affd7747cc3f179feb097d28990) and have such a crash in sctp code: [ 38.423932] [ cut here ] [ 38.424298] kernel BUG at net/sctp/socket.c:7425! [ 38.424583] invalid opcode: [#1] SMP KASAN [

BUG at net/sctp/socket.c:7425

Hello, I'm running the syzkaller fuzzer for v4.10-rc4 (0aa0313f9d576affd7747cc3f179feb097d28990) and have such a crash in sctp code: [ 38.423932] [ cut here ] [ 38.424298] kernel BUG at net/sctp/socket.c:7425! [ 38.424583] invalid opcode: [#1] SMP KASAN [

[PATCH 60/60] staging: lustre: libcfs: fix minimum size check for libcfs ioctl

The check for the smallest ioctl data in libcfs_ioctl_getdata() is incorrect. Instead of checking against struct libcfs_ioctl_data compare the size to struct libcfs_ioctl_hdr. Reported-by: Doug Oucharek Signed-off-by: James Simmons ---

[PATCH 01/60] staging: lustre: llite: Remove access of stripe in ll_setattr_raw

From: Jinshan Xiong In ll_setattr_raw(), it needs to know if a file is released when the file is being truncated. It used to get this information by accessing lov_stripe_md. This turns out not necessary. This patch removes the access of lov_stripe_md and solves the

[PATCH 60/60] staging: lustre: libcfs: fix minimum size check for libcfs ioctl

The check for the smallest ioctl data in libcfs_ioctl_getdata() is incorrect. Instead of checking against struct libcfs_ioctl_data compare the size to struct libcfs_ioctl_hdr. Reported-by: Doug Oucharek Signed-off-by: James Simmons --- drivers/staging/lustre/lnet/libcfs/linux/linux-module.c |

[PATCH 01/60] staging: lustre: llite: Remove access of stripe in ll_setattr_raw

From: Jinshan Xiong In ll_setattr_raw(), it needs to know if a file is released when the file is being truncated. It used to get this information by accessing lov_stripe_md. This turns out not necessary. This patch removes the access of lov_stripe_md and solves the problem in

[PATCH 58/60] staging: lustre: osc: avoid 64 divide in osc_cache_too_much

The use of 64 bit time introduces an expensive 64 bit division operation. Since the time lapse being calculated in osc_cache_too_much will never be more than seventy years we can cast the time lapse to an long and perform a normal 32 bit divison operation instead. Signed-off-by: James Simmons

[PATCH 59/60] staging: lustre: ptlrpc : remove userland usage from ptlrpc

The reason for __REQ_LAYOUT_USER__ was to expose a section of code in layout.c to userland for a utility similar to wireshark. This was done before wireshark existed but now that it does we no longer need to do this type of hack. This also reduces lustre_acl.h to strictly a kernel header now.

[PATCH 58/60] staging: lustre: osc: avoid 64 divide in osc_cache_too_much

The use of 64 bit time introduces an expensive 64 bit division operation. Since the time lapse being calculated in osc_cache_too_much will never be more than seventy years we can cast the time lapse to an long and perform a normal 32 bit divison operation instead. Signed-off-by: James Simmons

[PATCH 59/60] staging: lustre: ptlrpc : remove userland usage from ptlrpc

The reason for __REQ_LAYOUT_USER__ was to expose a section of code in layout.c to userland for a utility similar to wireshark. This was done before wireshark existed but now that it does we no longer need to do this type of hack. This also reduces lustre_acl.h to strictly a kernel header now.

[PATCH 57/60] staging: lustre: lmv: remove nlink check in lmv_revalidate_slaves

From: wang di If an application attempts to remove millions of files in a single directory it will fail. This failure was tracked down to the nlink < 2 check in lmv_revalidate_slaves, because after nlink reaches to maximum value of LDISKFS_LINK_MAX (65000), the nlink broadcast

[PATCH 57/60] staging: lustre: lmv: remove nlink check in lmv_revalidate_slaves

From: wang di If an application attempts to remove millions of files in a single directory it will fail. This failure was tracked down to the nlink < 2 check in lmv_revalidate_slaves, because after nlink reaches to maximum value of LDISKFS_LINK_MAX (65000), the nlink broadcast back from the

[PATCH 56/60] staging: lustre: llite: don't invoke direct_IO for the EOF case

From: Yang Sheng The function generic_file_read_iter() does not check EOF before invoke direct_IO callback. So we have to check it ourselves. Signed-off-by: Yang Sheng Intel-bug-id: https://jira.hpdd.intel.com/browse/LU-8969 Reviewed-on:

[PATCH 56/60] staging: lustre: llite: don't invoke direct_IO for the EOF case

From: Yang Sheng The function generic_file_read_iter() does not check EOF before invoke direct_IO callback. So we have to check it ourselves. Signed-off-by: Yang Sheng Intel-bug-id: https://jira.hpdd.intel.com/browse/LU-8969 Reviewed-on: https://review.whamcloud.com/24552 Reviewed-by: Bob

[PATCH 54/60] staging: lustre: fid: Change positional struct initializers to C99

From: Steve Guminski This patch makes no functional changes. Struct initializers in the fid directory that use C89 or GCC-only syntax are updated to C99 syntax. The C99 syntax prevents incorrect initialization if values are accidently placed in the wrong position,

[PATCH 55/60] staging: lustre: obd: move s3 in lmd_parse to inner loop

Building the lustre client with W=1 reports the following error: obdclass/obd_mount.c: In function lmd_parse: obdclass/obd_mount.c:880: warning: variable set but not used The solution is to move s3 to the inner loop where it is only used. Signed-off-by: James Simmons

[PATCH 54/60] staging: lustre: fid: Change positional struct initializers to C99

From: Steve Guminski This patch makes no functional changes. Struct initializers in the fid directory that use C89 or GCC-only syntax are updated to C99 syntax. The C99 syntax prevents incorrect initialization if values are accidently placed in the wrong position, allows changes in the struct

[PATCH 55/60] staging: lustre: obd: move s3 in lmd_parse to inner loop

Building the lustre client with W=1 reports the following error: obdclass/obd_mount.c: In function lmd_parse: obdclass/obd_mount.c:880: warning: variable set but not used The solution is to move s3 to the inner loop where it is only used. Signed-off-by: James Simmons Intel-bug-id:

[PATCH 52/60] staging: lustre: linkea: linkEA size limitation

From: Fan Yong Under DNE mode, if we do not restrict the linkEA size, and if there are too many cross-MDTs hard links to the same object, then it will casue the llog overflow. On the other hand, too many linkEA entries in the linkEA will serious affect the linkEA performance

[PATCH 52/60] staging: lustre: linkea: linkEA size limitation

From: Fan Yong Under DNE mode, if we do not restrict the linkEA size, and if there are too many cross-MDTs hard links to the same object, then it will casue the llog overflow. On the other hand, too many linkEA entries in the linkEA will serious affect the linkEA performance because we only

[PATCH 50/60] staging: lustre: ptlrpc: remove unused pc->pc_env

From: Dmitry Eremin Environment for request interpreters is not used any more. Signed-off-by: Dmitry Eremin Intel-bug-id: https://jira.hpdd.intel.com/browse/LU-8887 Reviewed-on: https://review.whamcloud.com/24061 Reviewed-by: John L. Hammond

[PATCH 50/60] staging: lustre: ptlrpc: remove unused pc->pc_env

From: Dmitry Eremin Environment for request interpreters is not used any more. Signed-off-by: Dmitry Eremin Intel-bug-id: https://jira.hpdd.intel.com/browse/LU-8887 Reviewed-on: https://review.whamcloud.com/24061 Reviewed-by: John L. Hammond Reviewed-by: Bob Glossman Reviewed-by: Oleg Drokin

[PATCH 51/60] staging: lustre: ptlrpc: update MODULE_PARAM_DESC in ptlrpcd.c

From: Dmitry Eremin Update max_ptlrpcds module parameter descriptions to let users know its obsolete. Change cpt to CPT for the module parameter description ptlrpcd_per_cpt_max so it matches documentation. Signed-off-by: Dmitry Eremin

[PATCH 53/60] staging: lustre: ptlrpc: update replay cursor when close during replay

From: Niu Yawei The replay cursor should be updated properly when close happened during replay, otherwise, ptlrpc_replay_next() could run into a dead loop due to an invalid replay cursor: - replay cursor is moved to an open request during replay; - application close that

[PATCH 51/60] staging: lustre: ptlrpc: update MODULE_PARAM_DESC in ptlrpcd.c

From: Dmitry Eremin Update max_ptlrpcds module parameter descriptions to let users know its obsolete. Change cpt to CPT for the module parameter description ptlrpcd_per_cpt_max so it matches documentation. Signed-off-by: Dmitry Eremin Intel-bug-id: https://jira.hpdd.intel.com/browse/LU-8890

[PATCH 53/60] staging: lustre: ptlrpc: update replay cursor when close during replay

From: Niu Yawei The replay cursor should be updated properly when close happened during replay, otherwise, ptlrpc_replay_next() could run into a dead loop due to an invalid replay cursor: - replay cursor is moved to an open request during replay; - application close that open file, so the

[PATCH 49/60] staging: lustre: socklnd: remove socklnd_init_msg

Remove the inline function socklnd_init_msg. Its only used by the kernel code so no point keeping it in an UAPI header. Signed-off-by: James Simmons Intel-bug-id: https://jira.hpdd.intel.com/browse/LU-6142 Reviewed-on: https://review.whamcloud.com/18506 Reviewed-by: Dmitry

[PATCH 48/60] staging: lustre: ksocklnd: ignore timedout TX on closing connection

From: Liang Zhen ksocklnd reaper thread always tries to close the connection for the first timedout zero-copy TX. This is wrong if this connection is already being closed, because the reaper will see the same TX again and again and cannot find out other timedout zero-copy

[PATCH 49/60] staging: lustre: socklnd: remove socklnd_init_msg

Remove the inline function socklnd_init_msg. Its only used by the kernel code so no point keeping it in an UAPI header. Signed-off-by: James Simmons Intel-bug-id: https://jira.hpdd.intel.com/browse/LU-6142 Reviewed-on: https://review.whamcloud.com/18506 Reviewed-by: Dmitry Eremin Reviewed-by:

[PATCH 48/60] staging: lustre: ksocklnd: ignore timedout TX on closing connection

From: Liang Zhen ksocklnd reaper thread always tries to close the connection for the first timedout zero-copy TX. This is wrong if this connection is already being closed, because the reaper will see the same TX again and again and cannot find out other timedout zero-copy TXs and close

[PATCH 43/60] staging: lustre: obd: remove OBD_NOTIFY_CREATE

From: "John L. Hammond" None of the obd_notify() handlers listen for the OBD_NOTIFY_CREATE event, so remove it and its sole use in lov_add_target(). Signed-off-by: John L. Hammond Intel-bug-id: https://jira.hpdd.intel.com/browse/LU-8403

[PATCH 43/60] staging: lustre: obd: remove OBD_NOTIFY_CREATE

From: "John L. Hammond" None of the obd_notify() handlers listen for the OBD_NOTIFY_CREATE event, so remove it and its sole use in lov_add_target(). Signed-off-by: John L. Hammond Intel-bug-id: https://jira.hpdd.intel.com/browse/LU-8403 Reviewed-on: https://review.whamcloud.com/21420

[PATCH 45/60] staging: lustre: libcfs: Change positional struct initializers to C99

From: Steve Guminski This patch makes no functional changes. Struct initializers in the libcfs directory that use C89 or GCC-only syntax are updated to C99 syntax. The C99 syntax prevents incorrect initialization if values are accidently placed in the wrong

[PATCH 41/60] staging: lustre: osc: osc_match_base prototype differs from declaration

From: Steve Guminski The patch updates the prototype in osc_internal.h to match the enums used in the declaration. The osc_match_base declaration in lustre/osc/osc_request.c uses enums for stricter checking on the type and mode parameters: int osc_match_base(struct

[PATCH 45/60] staging: lustre: libcfs: Change positional struct initializers to C99

From: Steve Guminski This patch makes no functional changes. Struct initializers in the libcfs directory that use C89 or GCC-only syntax are updated to C99 syntax. The C99 syntax prevents incorrect initialization if values are accidently placed in the wrong position, allows changes in the

[PATCH 41/60] staging: lustre: osc: osc_match_base prototype differs from declaration

From: Steve Guminski The patch updates the prototype in osc_internal.h to match the enums used in the declaration. The osc_match_base declaration in lustre/osc/osc_request.c uses enums for stricter checking on the type and mode parameters: int osc_match_base(struct obd_export *exp,

[PATCH 42/60] staging: lustre: ptlrpc: allow blocking asts to be delayed

From: Vladimir Saveliev ptlrpc_import_delay_req() refuses to delay blocking asts when import is not in LUSTRE_IMP_FULL yet. That leads to client eviction assuming that it failed to respond. Allow delays for blocking asts being resent. Signed-off-by: Vladimir

[PATCH 42/60] staging: lustre: ptlrpc: allow blocking asts to be delayed

From: Vladimir Saveliev ptlrpc_import_delay_req() refuses to delay blocking asts when import is not in LUSTRE_IMP_FULL yet. That leads to client eviction assuming that it failed to respond. Allow delays for blocking asts being resent. Signed-off-by: Vladimir Saveliev Intel-bug-id:

[PATCH 39/60] staging: libcfs: remove integer types abstraction from libcfs

Replace the ulong_ptr_t and long_ptr_t with standard kernel types. Signed-off-by: James Simmons Intel-bug-id: https://jira.hpdd.intel.com/browse/LU-6245 Reviewed-on: http://review.whamcloud.com/20204 Reviewed-by: Frank Zago Reviewed-by: Dmitry Eremin

[PATCH 39/60] staging: libcfs: remove integer types abstraction from libcfs

Replace the ulong_ptr_t and long_ptr_t with standard kernel types. Signed-off-by: James Simmons Intel-bug-id: https://jira.hpdd.intel.com/browse/LU-6245 Reviewed-on: http://review.whamcloud.com/20204 Reviewed-by: Frank Zago Reviewed-by: Dmitry Eremin Reviewed-by: Oleg Drokin Signed-off-by:

[PATCH 37/60] staging: lustre: llite: specify READA debug mask for ras_update

From: Bobi Jam So that debug log only contains relevant messages for debugging purpose. Signed-off-by: Bobi Jam Intel-bug-id: https://jira.hpdd.intel.com/browse/LU-8413 Reviewed-on: http://review.whamcloud.com/22753 Reviewed-by: Andreas Dilger

[PATCH 37/60] staging: lustre: llite: specify READA debug mask for ras_update

From: Bobi Jam So that debug log only contains relevant messages for debugging purpose. Signed-off-by: Bobi Jam Intel-bug-id: https://jira.hpdd.intel.com/browse/LU-8413 Reviewed-on: http://review.whamcloud.com/22753 Reviewed-by: Andreas Dilger Reviewed-by: Fan Yong Reviewed-by: Oleg Drokin

[PATCH 34/60] staging: lustre: libcfs: default CPT matches NUMA topology

From: Dmitry Eremin Change default value of CPT pattern and make it match NUMA topology Signed-off-by: Liang Zhen Signed-off-by: Dmitry Eremin Intel-bug-id: https://jira.hpdd.intel.com/browse/LU-5050 Reviewed-on:

[PATCH 34/60] staging: lustre: libcfs: default CPT matches NUMA topology

From: Dmitry Eremin Change default value of CPT pattern and make it match NUMA topology Signed-off-by: Liang Zhen Signed-off-by: Dmitry Eremin Intel-bug-id: https://jira.hpdd.intel.com/browse/LU-5050 Reviewed-on: http://review.whamcloud.com/22377 Reviewed-by: James Simmons Reviewed-by: Olaf

[PATCH 36/60] staging: lustre: header: remove assert from interval_set()

In the case of interval_tree.h only interval_set() uses LASSERT which is removed in this patch and interval_set() instead reports a real error. The header libcfs.h for interval_tree.h is not needed anymore so we can just use the standard linux kernel headers instead.h Signed-off-by: James Simmons

[PATCH 35/60] staging: lustre: lov: ld_target could be NULL

From: Bobi Jam lov_device::ld_target[ost_idx] could be NULL if the OST target is not filled in lov_device::ld_lov::lov_tgt_desc[ost_idx] yet. Signed-off-by: Bobi Jam Intel-bug-id: https://jira.hpdd.intel.com/browse/LU-8018 Reviewed-on:

[PATCH 36/60] staging: lustre: header: remove assert from interval_set()

In the case of interval_tree.h only interval_set() uses LASSERT which is removed in this patch and interval_set() instead reports a real error. The header libcfs.h for interval_tree.h is not needed anymore so we can just use the standard linux kernel headers instead.h Signed-off-by: James Simmons

[PATCH 35/60] staging: lustre: lov: ld_target could be NULL

From: Bobi Jam lov_device::ld_target[ost_idx] could be NULL if the OST target is not filled in lov_device::ld_lov::lov_tgt_desc[ost_idx] yet. Signed-off-by: Bobi Jam Intel-bug-id: https://jira.hpdd.intel.com/browse/LU-8018 Reviewed-on: http://review.whamcloud.com/21411 Reviewed-by: Jinshan

[PATCH 04/60] staging: lustre: mdc: quiet console message for known -EINTR

From: Andreas Dilger If a user process is waiting for MDS recovery during close, but the process is interrupted, the file is still closed but it prints a message on the console. Quiet the console message for -EINTR, since this is expected behaviour. Signed-off-by:

[PATCH 04/60] staging: lustre: mdc: quiet console message for known -EINTR

From: Andreas Dilger If a user process is waiting for MDS recovery during close, but the process is interrupted, the file is still closed but it prints a message on the console. Quiet the console message for -EINTR, since this is expected behaviour. Signed-off-by: Andreas Dilger Intel-bug-id:

[PATCH 32/60] staging: lustre: osc: limits the number of chunks in write RPC

From: Jinshan Xiong OSC has to make sure that it won't issue write RPCs with too many chunks otherwise it will casue ZFS to create transactions much bigger than DMU_MAX_ACCESS in size, which will end up with write failure. Signed-off-by: Jinshan Xiong

[PATCH 32/60] staging: lustre: osc: limits the number of chunks in write RPC

From: Jinshan Xiong OSC has to make sure that it won't issue write RPCs with too many chunks otherwise it will casue ZFS to create transactions much bigger than DMU_MAX_ACCESS in size, which will end up with write failure. Signed-off-by: Jinshan Xiong Signed-off-by: Dmitry Eremin

[PATCH 06/60] staging: lustre: clio: revise readahead to support 16MB IO

From: Jinshan Xiong Read ahead currently doesn't handle 16MB RPC packets correctly by assuming the packets are a default size instead of querying the size. This work adjust the read ahead policy to issue read ahead RPC by the underlying RPC size. Signed-off-by: Jinshan

[PATCH 33/60] staging: lustre: libcfs: avoid stomping on module param cpu_pattern

From: Dmitry Eremin The function cfs_cpt_table_create_pattern() alters the string passed to it. Currently we are passing in the module parameter string cpu_pattern which is incorrect. Instead lets duplicate the module parameter string and pass that to the function

[PATCH 23/60] staging: lustre: lmv: remove unused placement parameter

From: "John L. Hammond" Remove the unused lmv.*.placement parameter along with supporting functions and struct members. Signed-off-by: John L. Hammond Intel-bug-id: https://jira.hpdd.intel.com/browse/LU-7674 Reviewed-on:

[PATCH 06/60] staging: lustre: clio: revise readahead to support 16MB IO

From: Jinshan Xiong Read ahead currently doesn't handle 16MB RPC packets correctly by assuming the packets are a default size instead of querying the size. This work adjust the read ahead policy to issue read ahead RPC by the underlying RPC size. Signed-off-by: Jinshan Xiong Signed-off-by: Gu

[PATCH 33/60] staging: lustre: libcfs: avoid stomping on module param cpu_pattern

From: Dmitry Eremin The function cfs_cpt_table_create_pattern() alters the string passed to it. Currently we are passing in the module parameter string cpu_pattern which is incorrect. Instead lets duplicate the module parameter string and pass that to the function cfs_cpt_table_create_pattern().

[PATCH 23/60] staging: lustre: lmv: remove unused placement parameter

From: "John L. Hammond" Remove the unused lmv.*.placement parameter along with supporting functions and struct members. Signed-off-by: John L. Hammond Intel-bug-id: https://jira.hpdd.intel.com/browse/LU-7674 Reviewed-on: http://review.whamcloud.com/18019 Reviewed-by: Ben Evans Reviewed-by:

[PATCH 31/60] staging: lustre: clio: sync write should update mtime

From: Niu Yawei Sync write should update m/ctime promptly, otherwise, stale m/ctime could be updated on the OST object by the sync write RPC. Signed-off-by: Niu Yawei Intel-bug-id: https://jira.hpdd.intel.com/browse/LU-7310 Reviewed-on:

[PATCH 00/60] staging: lustre: batches of fixes for lustre client

Batch of missing fixes for lustre for the upstream client. Alex Zhuravlev (1): staging: lustre: obdclass: do not call lu_site_purge() for single object exceed Alexander Boyko (1): staging: lustre: ptlrpc: skip lock if export failed Andreas Dilger (3): staging: lustre: mdc: quiet console

  1   2   3   4   5   6   7   >