[PATCH] ocfs2: ratelimit the 'max lookup times reached' notice

2020-10-01 Thread Mauricio Faria de Oliveira
):ocfs2_check_if_ancestor:1091 max lookup times reached, filesystem may have nested directories, src inode: 18007, dest inode: 17940. ... Signed-off-by: Mauricio Faria de Oliveira --- fs/ocfs2/namei.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/fs/ocfs2/namei.c b/fs/ocfs2/namei.c index

Re: [PATCH v3] powerpc/64: Fix section mismatch warnings for early boot symbols

2018-04-10 Thread Mauricio Faria de Oliveira
On 04/09/2018 11:51 PM, Michael Ellerman wrote: Thanks for picking this one up. I hate to be a pain ... but before we merge this and proliferate these names, I'd like to change the names of some of these early asm functions. They're terribly named due to historical reasons. Indeed :) No

Re: [PATCH v3] powerpc/64: Fix section mismatch warnings for early boot symbols

2018-04-10 Thread Mauricio Faria de Oliveira
On 04/09/2018 11:51 PM, Michael Ellerman wrote: Thanks for picking this one up. I hate to be a pain ... but before we merge this and proliferate these names, I'd like to change the names of some of these early asm functions. They're terribly named due to historical reasons. Indeed :) No

[PATCH v3] powerpc/64: Fix section mismatch warnings for early boot symbols

2018-04-05 Thread Mauricio Faria de Oliveira
rence from the variable start_here_common to the function .init.text:start_kernel() The function start_here_common() references the function __init start_kernel(). This is often because start_here_common lacks a __init annotation or the annotation of start_kernel is wrong. Signed-off-by: Maur

[PATCH v3] powerpc/64: Fix section mismatch warnings for early boot symbols

2018-04-05 Thread Mauricio Faria de Oliveira
rence from the variable start_here_common to the function .init.text:start_kernel() The function start_here_common() references the function __init start_kernel(). This is often because start_here_common lacks a __init annotation or the annotation of start_kernel is wrong. Signed-off-by: Maur

[PATCH v2] powerpc/64: Fix section mismatch warnings for early boot symbols

2018-03-09 Thread Mauricio Faria de Oliveira
: Nicholas Piggin Date: Fri Dec 23 00:14:19 AEDT 2016 Signed-off-by: Mauricio Faria de Oliveira <mauri...@linux.vnet.ibm.com> --- v2: fix missing close parenthesis in conditional (wrong patch file, sorry) scripts/mod/modpost.c | 22 -- 1 file changed, 20 insertions

[PATCH v2] powerpc/64: Fix section mismatch warnings for early boot symbols

2018-03-09 Thread Mauricio Faria de Oliveira
: Nicholas Piggin Date: Fri Dec 23 00:14:19 AEDT 2016 Signed-off-by: Mauricio Faria de Oliveira --- v2: fix missing close parenthesis in conditional (wrong patch file, sorry) scripts/mod/modpost.c | 22 -- 1 file changed, 20 insertions(+), 2 deletions(-) diff --git a/s

[PATCH] powerpc/64: Fix section mismatch warnings for early boot symbols

2018-03-09 Thread Mauricio Faria de Oliveira
: Nicholas Piggin Date: Fri Dec 23 00:14:19 AEDT 2016 Signed-off-by: Mauricio Faria de Oliveira <mauri...@linux.vnet.ibm.com> --- scripts/mod/modpost.c | 22 -- 1 file changed, 20 insertions(+), 2 deletions(-) diff --git a/scripts/mod/modpost.c b/scripts/mod/modpost

[PATCH] powerpc/64: Fix section mismatch warnings for early boot symbols

2018-03-09 Thread Mauricio Faria de Oliveira
: Nicholas Piggin Date: Fri Dec 23 00:14:19 AEDT 2016 Signed-off-by: Mauricio Faria de Oliveira --- scripts/mod/modpost.c | 22 -- 1 file changed, 20 insertions(+), 2 deletions(-) diff --git a/scripts/mod/modpost.c b/scripts/mod/modpost.c index 9917f92..c65d5e2 100644 ---

Re: [PATCH] drivers: of: increase MAX_RESERVED_REGIONS to 32

2017-10-02 Thread Mauricio Faria de Oliveira
On 09/26/2017 05:40 AM, Stewart Smith wrote: The simple fix is to bump the length of the array to 32 which "should be enough for everyone(TM)". Tested-by: Mauricio Faria de Oliveira <mauri...@linux.vnet.ibm.com> # uname -r 4.14.0-rc3 # dmesg [0.00] opal: OPAL detected

Re: [PATCH] drivers: of: increase MAX_RESERVED_REGIONS to 32

2017-10-02 Thread Mauricio Faria de Oliveira
On 09/26/2017 05:40 AM, Stewart Smith wrote: The simple fix is to bump the length of the array to 32 which "should be enough for everyone(TM)". Tested-by: Mauricio Faria de Oliveira # uname -r 4.14.0-rc3 # dmesg [0.00] opal: OPAL detected ! [0.00] crashkernel: me

Re: [PATCH v2 1/4] scsi: scsi_dh_alua: allow I/O in target port unavailable and standby states

2017-07-11 Thread Mauricio Faria de Oliveira
On 07/11/2017 12:32 PM, Mauricio Faria de Oliveira wrote: Also, it seems the Unavailable/Standby states would not be logged without a recheck from alua_check_sense(), since the only callers of alua_rtpg_queue() are alua_activate() and alua_check[_sense]() Well, actually it does get logged

Re: [PATCH v2 1/4] scsi: scsi_dh_alua: allow I/O in target port unavailable and standby states

2017-07-11 Thread Mauricio Faria de Oliveira
On 07/11/2017 12:32 PM, Mauricio Faria de Oliveira wrote: Also, it seems the Unavailable/Standby states would not be logged without a recheck from alua_check_sense(), since the only callers of alua_rtpg_queue() are alua_activate() and alua_check[_sense]() Well, actually it does get logged

Re: [PATCH v2 1/4] scsi: scsi_dh_alua: allow I/O in target port unavailable and standby states

2017-07-11 Thread Mauricio Faria de Oliveira
go through that function. (and it occurred to me that the state-change check of patch 3 can be done there, simpler.) cheers, -- Mauricio Faria de Oliveira IBM Linux Technology Center

Re: [PATCH v2 1/4] scsi: scsi_dh_alua: allow I/O in target port unavailable and standby states

2017-07-11 Thread Mauricio Faria de Oliveira
go through that function. (and it occurred to me that the state-change check of patch 3 can be done there, simpler.) cheers, -- Mauricio Faria de Oliveira IBM Linux Technology Center

Re: [PATCH v2 0/4] scsi_dh_alua: fix stuck I/O after unavailable/standby states

2017-07-10 Thread Mauricio Faria de Oliveira
On 07/10/2017 07:47 PM, Mauricio Faria de Oliveira wrote: This patchset addresses that problem, and adds a few improvements to the logging of PG state changes. Here are some kernel log snippets with the patchset, if that helps. The 2 port groups temporarily gone into unavailable state

Re: [PATCH v2 0/4] scsi_dh_alua: fix stuck I/O after unavailable/standby states

2017-07-10 Thread Mauricio Faria de Oliveira
On 07/10/2017 07:47 PM, Mauricio Faria de Oliveira wrote: This patchset addresses that problem, and adds a few improvements to the logging of PG state changes. Here are some kernel log snippets with the patchset, if that helps. The 2 port groups temporarily gone into unavailable state

[PATCH v2 1/4] scsi: scsi_dh_alua: allow I/O in target port unavailable and standby states

2017-07-10 Thread Mauricio Faria de Oliveira
ated on path activation (alua_activate(), as it schedules a recheck), thus I/O requests are no longer failed. Signed-off-by: Mauricio Faria de Oliveira <mauri...@linux.vnet.ibm.com> Reported-by: Naresh Bannoth <nbann...@in.ibm.com> --- v2: - also add support for standby state

[PATCH v2 1/4] scsi: scsi_dh_alua: allow I/O in target port unavailable and standby states

2017-07-10 Thread Mauricio Faria de Oliveira
ated on path activation (alua_activate(), as it schedules a recheck), thus I/O requests are no longer failed. Signed-off-by: Mauricio Faria de Oliveira Reported-by: Naresh Bannoth --- v2: - also add support for standby state to alua_check_sense(), alua_prep_fn() (Bart Van Assche ) driv

[PATCH v2 2/4] scsi: scsi_dh_alua: print changes to RTPG state of all PGs

2017-07-10 Thread Mauricio Faria de Oliveira
for the current PG. Signed-off-by: Mauricio Faria de Oliveira <mauri...@linux.vnet.ibm.com> --- v2: - use lockdep_assert_held() instead of documenting locking conventions (Bart Van Assche <bart.vanass...@sandisk.com>) - define two functions (with/without supported states information)

[PATCH v2 2/4] scsi: scsi_dh_alua: print changes to RTPG state of all PGs

2017-07-10 Thread Mauricio Faria de Oliveira
for the current PG. Signed-off-by: Mauricio Faria de Oliveira --- v2: - use lockdep_assert_held() instead of documenting locking conventions (Bart Van Assche ) - define two functions (with/without supported states information) (Bart Van Assche ) - simplify which device is used for printing

[PATCH v2 4/4] scsi: scsi_dh_alua: add sdev_dbg() to track alua_rtpg_work()

2017-07-10 Thread Mauricio Faria de Oliveira
Insert sdev_dbg() calls in the function path which may queue alua_rtpg_work() past initialization, for debugging purposes: - alua_activate() - alua_check_sense() - alua_rtpg_queue() Signed-off-by: Mauricio Faria de Oliveira <mauri...@linux.vnet.ibm.com> --- drivers/scsi/device_h

[PATCH v2 4/4] scsi: scsi_dh_alua: add sdev_dbg() to track alua_rtpg_work()

2017-07-10 Thread Mauricio Faria de Oliveira
Insert sdev_dbg() calls in the function path which may queue alua_rtpg_work() past initialization, for debugging purposes: - alua_activate() - alua_check_sense() - alua_rtpg_queue() Signed-off-by: Mauricio Faria de Oliveira --- drivers/scsi/device_handler/scsi_dh_alua.c | 14 -- 1

[PATCH v2 3/4] scsi: scsi_dh_alua: do not print RTPG state if it remains unavailable/standby

2017-07-10 Thread Mauricio Faria de Oliveira
scheduled in alua_check_sense() to update PG state. So, do not to print such message if unavailable/standby state remains (i.e., the PG did not transition to/from such states). All other cases continue to be printed. Signed-off-by: Mauricio Faria de Oliveira <mauri...@linux.vnet.ibm.com>

[PATCH v2 3/4] scsi: scsi_dh_alua: do not print RTPG state if it remains unavailable/standby

2017-07-10 Thread Mauricio Faria de Oliveira
scheduled in alua_check_sense() to update PG state. So, do not to print such message if unavailable/standby state remains (i.e., the PG did not transition to/from such states). All other cases continue to be printed. Signed-off-by: Mauricio Faria de Oliveira --- v2: - changed v1's alua_state_remains

[PATCH v2 0/4] scsi_dh_alua: fix stuck I/O after unavailable/standby states

2017-07-10 Thread Mauricio Faria de Oliveira
in unavailable/standby are not logged - only changes are. Patch 4 adds few sdev_dbg() calls to track the path to alua_rtpg_work() Tested on v4.12+ (commit b4b8cbf679c4). Mauricio Faria de Oliveira (4): scsi: scsi_dh_alua: allow I/O in target port unavailable and standby states scsi

[PATCH v2 0/4] scsi_dh_alua: fix stuck I/O after unavailable/standby states

2017-07-10 Thread Mauricio Faria de Oliveira
in unavailable/standby are not logged - only changes are. Patch 4 adds few sdev_dbg() calls to track the path to alua_rtpg_work() Tested on v4.12+ (commit b4b8cbf679c4). Mauricio Faria de Oliveira (4): scsi: scsi_dh_alua: allow I/O in target port unavailable and standby states scsi

[PATCH] aio: fix the increment of aio-nr and counting against aio-max-nr

2017-06-08 Thread Mauricio Faria de Oliveira
SED. test cases/13.t completed PASSED. test cases/14.t completed PASSED. test cases/15.t completed PASSED. test cases/16.t completed PASSED. test cases/10.t completed PASSED. test cases/8.t completed PASSED. Signed-off-by: Mauricio Faria de Oliveira <mauri...@linux.vnet.ib

[PATCH] aio: fix the increment of aio-nr and counting against aio-max-nr

2017-06-08 Thread Mauricio Faria de Oliveira
SED. test cases/13.t completed PASSED. test cases/14.t completed PASSED. test cases/15.t completed PASSED. test cases/16.t completed PASSED. test cases/10.t completed PASSED. test cases/8.t completed PASSED. Signed-off-by: Mauricio Faria de Oliveira Reported-by: Lekshmi C

Re: [PATCH] scsi: do not requeue requests unaligned with device sector size

2016-12-21 Thread Mauricio Faria de Oliveira
f how the I/O is being broken up into frames at the transport level and at which offset the transfer was interrupted. Christoph, Hannes, Martin, Thank you all for your comments and pointers to the documentation/spec. I'll carry it on with the HBA and storage folks. cheers, -- Mauricio Faria de Oliveira IBM Linux Technology Center

Re: [PATCH] scsi: do not requeue requests unaligned with device sector size

2016-12-21 Thread Mauricio Faria de Oliveira
f how the I/O is being broken up into frames at the transport level and at which offset the transfer was interrupted. Christoph, Hannes, Martin, Thank you all for your comments and pointers to the documentation/spec. I'll carry it on with the HBA and storage folks. cheers, -- Mauricio Faria de Oliveira IBM Linux Technology Center

[PATCH] scsi: do not requeue requests unaligned with device sector size

2016-12-19 Thread Mauricio Faria de Oliveira
[sda] tag#0 8 sectors total, 4096 bytes done. [...] sd 0:0:0:0: tag#0 0 sectors total, 0 bytes done. Apologies for the ridiculously long commit message with description and test-cases, but this problem has been relatively difficult to reproduce and understand, so I thought the documentation/instr

[PATCH] scsi: do not requeue requests unaligned with device sector size

2016-12-19 Thread Mauricio Faria de Oliveira
[sda] tag#0 8 sectors total, 4096 bytes done. [...] sd 0:0:0:0: tag#0 0 sectors total, 0 bytes done. Apologies for the ridiculously long commit message with description and test-cases, but this problem has been relatively difficult to reproduce and understand, so I thought the documentation/instru

[PATCH RESEND] block: allow WRITE_SAME commands with the SG_IO ioctl

2016-12-15 Thread Mauricio Faria de Oliveira
or 17096824 Links: [1] http://git.qemu.org/?p=qemu.git;a=commit;h=336a6915bc7089fb20fea4ba99972ad9a97c5f52 [2] https://libvirt.org/formatdomain.html#elementsDisks (see 'disk' -> 'device') Signed-off-by: Mauricio Faria de Oliveira <mauri...@linux.vnet.ibm.com> Signed-off-by: Brahadamba

[PATCH RESEND] block: allow WRITE_SAME commands with the SG_IO ioctl

2016-12-15 Thread Mauricio Faria de Oliveira
or 17096824 Links: [1] http://git.qemu.org/?p=qemu.git;a=commit;h=336a6915bc7089fb20fea4ba99972ad9a97c5f52 [2] https://libvirt.org/formatdomain.html#elementsDisks (see 'disk' -> 'device') Signed-off-by: Mauricio Faria de Oliveira Signed-off-by: Brahadambal Srinivasan Reported-by: Manjunatha

[PATCH] block: allow WRITE_SAME commands with the SG_IO ioctl

2016-12-10 Thread Mauricio Faria de Oliveira
or 17096824 Links: [1] http://git.qemu.org/?p=qemu.git;a=commit;h=336a6915bc7089fb20fea4ba99972ad9a97c5f52 [2] https://libvirt.org/formatdomain.html#elementsDisks (see 'disk' -> 'device') Signed-off-by: Mauricio Faria de Oliveira <mauri...@linux.vnet.ibm.com> Signed-off-by: Brahadamba

[PATCH] block: allow WRITE_SAME commands with the SG_IO ioctl

2016-12-10 Thread Mauricio Faria de Oliveira
or 17096824 Links: [1] http://git.qemu.org/?p=qemu.git;a=commit;h=336a6915bc7089fb20fea4ba99972ad9a97c5f52 [2] https://libvirt.org/formatdomain.html#elementsDisks (see 'disk' -> 'device') Signed-off-by: Mauricio Faria de Oliveira Signed-off-by: Brahadambal Srinivasan Reported-by: Manjunatha

Re: [PATCH] lpfc: fix oops/BUG in lpfc_sli_ringtxcmpl_put()

2016-11-23 Thread Mauricio Faria de Oliveira
On 11/23/2016 12:12 PM, Johannes Thumshirn wrote: Looks good and sorry for the bug, Reviewed-by: Johannes Thumshirn <jthumsh...@suse.de> Thanks for the quick review. Not a problem! This problem turned out to be a good learning exercise. :) -- Mauricio Faria de Oliveira IBM Linux Tech

Re: [PATCH] lpfc: fix oops/BUG in lpfc_sli_ringtxcmpl_put()

2016-11-23 Thread Mauricio Faria de Oliveira
On 11/23/2016 12:12 PM, Johannes Thumshirn wrote: Looks good and sorry for the bug, Reviewed-by: Johannes Thumshirn Thanks for the quick review. Not a problem! This problem turned out to be a good learning exercise. :) -- Mauricio Faria de Oliveira IBM Linux Technology Center

Re: [PATCH] lpfc: fix oops/BUG in lpfc_sli_ringtxcmpl_put()

2016-11-23 Thread Mauricio Faria de Oliveira
Due credit; an oversight. On 11/23/2016 10:33 AM, Mauricio Faria de Oliveira wrote: Reported-by: Harsha Thyagaraja <hathy...@in.ibm.com> Cc: sta...@vger.kernel.org # v4.8 Fixes: 22466da5b4b7 ("lpfc: Fix possible NULL pointer dereference") Signed-off-by: Mauricio Faria de

Re: [PATCH] lpfc: fix oops/BUG in lpfc_sli_ringtxcmpl_put()

2016-11-23 Thread Mauricio Faria de Oliveira
Due credit; an oversight. On 11/23/2016 10:33 AM, Mauricio Faria de Oliveira wrote: Reported-by: Harsha Thyagaraja Cc: sta...@vger.kernel.org # v4.8 Fixes: 22466da5b4b7 ("lpfc: Fix possible NULL pointer dereference") Signed-off-by: Mauricio Faria de Oliveira -- Maurici

[PATCH] lpfc: fix oops/BUG in lpfc_sli_ringtxcmpl_put()

2016-11-23 Thread Mauricio Faria de Oliveira
et_from_kernel_thread+0x5c/0xbc <...> Cc: sta...@vger.kernel.org # v4.8 Fixes: 22466da5b4b7 ("lpfc: Fix possible NULL pointer dereference") Signed-off-by: Mauricio Faria de Oliveira <mauri...@linux.vnet.ibm.com> --- drivers/scsi/lpfc/lpfc_sli.c | 14 -- 1 file

[PATCH] lpfc: fix oops/BUG in lpfc_sli_ringtxcmpl_put()

2016-11-23 Thread Mauricio Faria de Oliveira
et_from_kernel_thread+0x5c/0xbc <...> Cc: sta...@vger.kernel.org # v4.8 Fixes: 22466da5b4b7 ("lpfc: Fix possible NULL pointer dereference") Signed-off-by: Mauricio Faria de Oliveira --- drivers/scsi/lpfc/lpfc_sli.c | 14 -- 1 file changed, 8 insertions(+), 6 deletio

[PATCH] qla2xxx: do not abort all commands in the adapter during EEH recovery

2016-11-14 Thread Mauricio Faria de Oliveira
orry for this oversight.) With it applied, both PCI device remove and EEH recovery works fine. Fixes: 1535aa75a3d8 ("scsi: qla2xxx: fix invalid DMA access after command aborts in PCI device remove") Signed-off-by: Mauricio Faria de Oliveira <mauri...@linux.vnet.ibm.com>

[PATCH] qla2xxx: do not abort all commands in the adapter during EEH recovery

2016-11-14 Thread Mauricio Faria de Oliveira
orry for this oversight.) With it applied, both PCI device remove and EEH recovery works fine. Fixes: 1535aa75a3d8 ("scsi: qla2xxx: fix invalid DMA access after command aborts in PCI device remove") Signed-off-by: Mauricio Faria de Oliveira --- drivers/scsi/qla2xxx/qla_os.c | 21

[PATCH 2/2] qla2xxx: fix invalid DMA access after command aborts in PCI device remove

2016-11-07 Thread Mauricio Faria de Oliveira
and handle responses. Reported-by: Naresh Bannoth <nbann...@in.ibm.com> Signed-off-by: Mauricio Faria de Oliveira <mauri...@linux.vnet.ibm.com> --- drivers/scsi/qla2xxx/qla_os.c | 9 + 1 file changed, 9 insertions(+) diff --git a/drivers/scsi/qla2xxx/qla_os.c b/drivers/scsi/qla2

[PATCH 1/2] qla2xxx: do not queue commands when unloading

2016-11-07 Thread Mauricio Faria de Oliveira
700a10] qla2xxx_queuecommand+0x50/0x3f0 [qla2xxx] So, fail commands in qla2xxx_queuecommand() if the UNLOADING bit is set. Signed-off-by: Mauricio Faria de Oliveira <mauri...@linux.vnet.ibm.com> --- drivers/scsi/qla2xxx/qla_os.c | 5 + 1 file changed, 5 insertions(+) diff --git a/drivers/

[PATCH 2/2] qla2xxx: fix invalid DMA access after command aborts in PCI device remove

2016-11-07 Thread Mauricio Faria de Oliveira
and handle responses. Reported-by: Naresh Bannoth Signed-off-by: Mauricio Faria de Oliveira --- drivers/scsi/qla2xxx/qla_os.c | 9 + 1 file changed, 9 insertions(+) diff --git a/drivers/scsi/qla2xxx/qla_os.c b/drivers/scsi/qla2xxx/qla_os.c index fdb135b..c50dd22 100644 --- a/drivers/scsi

[PATCH 1/2] qla2xxx: do not queue commands when unloading

2016-11-07 Thread Mauricio Faria de Oliveira
700a10] qla2xxx_queuecommand+0x50/0x3f0 [qla2xxx] So, fail commands in qla2xxx_queuecommand() if the UNLOADING bit is set. Signed-off-by: Mauricio Faria de Oliveira --- drivers/scsi/qla2xxx/qla_os.c | 5 + 1 file changed, 5 insertions(+) diff --git a/drivers/scsi/qla2xxx/qla_os.c b/driver

[PATCH 0/2] qla2xxx: fix errors in PCI device remove with ongoing I/O

2016-11-07 Thread Mauricio Faria de Oliveira
xxx [001d:70:00.0]-801c:1: Abort command issued nexus=1:0:0 -- 1 2003. <...> qla2xxx [001d:70:00.1]-801c:2: Abort command issued nexus=2:3:0 -- 1 2003. <...> (command does return; adapter can be re-added correctly) Mauricio Faria de Oliveira (2): qla2xxx: do no

[PATCH 0/2] qla2xxx: fix errors in PCI device remove with ongoing I/O

2016-11-07 Thread Mauricio Faria de Oliveira
xxx [001d:70:00.0]-801c:1: Abort command issued nexus=1:0:0 -- 1 2003. <...> qla2xxx [001d:70:00.1]-801c:2: Abort command issued nexus=2:3:0 -- 1 2003. <...> (command does return; adapter can be re-added correctly) Mauricio Faria de Oliveira (2): qla2xxx: do no

Re: aio: questions with ioctx_alloc() and large num_possible_cpus()

2016-10-05 Thread Mauricio Faria de Oliveira
, -- Mauricio Faria de Oliveira IBM Linux Technology Center

Re: aio: questions with ioctx_alloc() and large num_possible_cpus()

2016-10-05 Thread Mauricio Faria de Oliveira
, -- Mauricio Faria de Oliveira IBM Linux Technology Center

Re: aio: questions with ioctx_alloc() and large num_possible_cpus()

2016-10-05 Thread Mauricio Faria de Oliveira
systems. Regards, -- Mauricio Faria de Oliveira IBM Linux Technology Center

Re: aio: questions with ioctx_alloc() and large num_possible_cpus()

2016-10-05 Thread Mauricio Faria de Oliveira
systems. Regards, -- Mauricio Faria de Oliveira IBM Linux Technology Center

Re: aio: questions with ioctx_alloc() and large num_possible_cpus()

2016-10-05 Thread Mauricio Faria de Oliveira
cpus() * 4", and what is the scenario where the math is based on? I've been thinking and assuming values for a while now, and didn't figure out the point where / how it occurs. Thanks for your support, -- Mauricio Faria de Oliveira IBM Linux Technology Center

Re: aio: questions with ioctx_alloc() and large num_possible_cpus()

2016-10-05 Thread Mauricio Faria de Oliveira
cpus() * 4", and what is the scenario where the math is based on? I've been thinking and assuming values for a while now, and didn't figure out the point where / how it occurs. Thanks for your support, -- Mauricio Faria de Oliveira IBM Linux Technology Center

aio: questions with ioctx_alloc() and large num_possible_cpus()

2016-10-04 Thread Mauricio Faria de Oliveira
e actually requested by userspace?) or the number of times io_setup(N, ) returned successfully (say, io contexts), regardless of the total/sum of their nr_events? - any other comments/suggestions are appreciated. Thanks in advance, -- Mauricio Faria de Oliveira IBM Linux Technology Center

aio: questions with ioctx_alloc() and large num_possible_cpus()

2016-10-04 Thread Mauricio Faria de Oliveira
e actually requested by userspace?) or the number of times io_setup(N, ) returned successfully (say, io contexts), regardless of the total/sum of their nr_events? - any other comments/suggestions are appreciated. Thanks in advance, -- Mauricio Faria de Oliveira IBM Linux Technology Center

Re: [PATCH 4.4 000/118] 4.4.22-stable review

2016-09-28 Thread Mauricio Faria de Oliveira
On 09/28/2016 05:45 AM, Andrew Donnellan wrote: 2dd9c11b9d4 applies cleanly on top of 4.4 and works for me in the cxl case. Mauricio - any objections from the pseries/dlpar side? No objections. -- Mauricio Faria de Oliveira IBM Linux Technology Center

Re: [PATCH 4.4 000/118] 4.4.22-stable review

2016-09-28 Thread Mauricio Faria de Oliveira
On 09/28/2016 05:45 AM, Andrew Donnellan wrote: 2dd9c11b9d4 applies cleanly on top of 4.4 and works for me in the cxl case. Mauricio - any objections from the pseries/dlpar side? No objections. -- Mauricio Faria de Oliveira IBM Linux Technology Center

Re: [PATCH v4 0/3] dma-mapping, powerpc, nvme: introduce the DMA_ATTR_NO_WARN attribute

2016-08-08 Thread Mauricio Faria de Oliveira
that could help with it, I'd be happy to write something simpler/more discreet. Thanks for the suggestions and discussions. [1] https://lists.ozlabs.org/pipermail/linuxppc-dev/2016-June/144196.html -- Mauricio Faria de Oliveira IBM Linux Technology Center

Re: [PATCH v4 0/3] dma-mapping, powerpc, nvme: introduce the DMA_ATTR_NO_WARN attribute

2016-08-08 Thread Mauricio Faria de Oliveira
that could help with it, I'd be happy to write something simpler/more discreet. Thanks for the suggestions and discussions. [1] https://lists.ozlabs.org/pipermail/linuxppc-dev/2016-June/144196.html -- Mauricio Faria de Oliveira IBM Linux Technology Center

Re: [PATCH v4 0/3] dma-mapping, powerpc, nvme: introduce the DMA_ATTR_NO_WARN attribute

2016-08-05 Thread Mauricio Faria de Oliveira
to), but it wasn't accepted [1]; so I guess it apparently is, in some cases. [1] https://lists.ozlabs.org/pipermail/linuxppc-dev/2016-June/144196.html thanks -- Mauricio Faria de Oliveira IBM Linux Technology Center

Re: [PATCH v4 0/3] dma-mapping, powerpc, nvme: introduce the DMA_ATTR_NO_WARN attribute

2016-08-05 Thread Mauricio Faria de Oliveira
to), but it wasn't accepted [1]; so I guess it apparently is, in some cases. [1] https://lists.ozlabs.org/pipermail/linuxppc-dev/2016-June/144196.html thanks -- Mauricio Faria de Oliveira IBM Linux Technology Center

Re: [PATCH v4 0/3] dma-mapping, powerpc, nvme: introduce the DMA_ATTR_NO_WARN attribute

2016-08-04 Thread Mauricio Faria de Oliveira
y can return either BLK_MQ_RQ_QUEUE_BUSY or BLK_MQ_RQ_QUEUE_ERROR - so the former is OK.) Does that make sense? Thanks for the review. -- Mauricio Faria de Oliveira IBM Linux Technology Center

Re: [PATCH v4 0/3] dma-mapping, powerpc, nvme: introduce the DMA_ATTR_NO_WARN attribute

2016-08-04 Thread Mauricio Faria de Oliveira
y can return either BLK_MQ_RQ_QUEUE_BUSY or BLK_MQ_RQ_QUEUE_ERROR - so the former is OK.) Does that make sense? Thanks for the review. -- Mauricio Faria de Oliveira IBM Linux Technology Center

[PATCH 1/3] dma-mapping: introduce the DMA_ATTR_NO_WARN attribute

2016-08-01 Thread Mauricio Faria de Oliveira
Introduce the DMA_ATTR_NO_WARN attribute, and document it. Signed-off-by: Mauricio Faria de Oliveira <mauri...@linux.vnet.ibm.com> --- Documentation/DMA-attributes.txt | 17 + include/linux/dma-mapping.h | 5 + 2 files changed, 22 insertions(+) diff

[PATCH 2/3] powerpc: implement the DMA_ATTR_NO_WARN attribute

2016-08-01 Thread Mauricio Faria de Oliveira
Add support for the DMA_ATTR_NO_WARN attribute on powerpc iommu code. Signed-off-by: Mauricio Faria de Oliveira <mauri...@linux.vnet.ibm.com> --- arch/powerpc/kernel/iommu.c | 6 -- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/arch/powerpc/kernel/iommu.c b/arch/p

[PATCH 3/3] nvme: use the DMA_ATTR_NO_WARN attribute

2016-08-01 Thread Mauricio Faria de Oliveira
Use the DMA_ATTR_NO_WARN attribute for the dma_map_sg() call of the nvme driver that returns BLK_MQ_RQ_QUEUE_BUSY (not for BLK_MQ_RQ_QUEUE_ERROR). Signed-off-by: Mauricio Faria de Oliveira <mauri...@linux.vnet.ibm.com> Reviewed-by: Gabriel Krisman Bertazi <kris...@linux.vnet.ibm.com>

[PATCH 1/3] dma-mapping: introduce the DMA_ATTR_NO_WARN attribute

2016-08-01 Thread Mauricio Faria de Oliveira
Introduce the DMA_ATTR_NO_WARN attribute, and document it. Signed-off-by: Mauricio Faria de Oliveira --- Documentation/DMA-attributes.txt | 17 + include/linux/dma-mapping.h | 5 + 2 files changed, 22 insertions(+) diff --git a/Documentation/DMA-attributes.txt b

[PATCH 2/3] powerpc: implement the DMA_ATTR_NO_WARN attribute

2016-08-01 Thread Mauricio Faria de Oliveira
Add support for the DMA_ATTR_NO_WARN attribute on powerpc iommu code. Signed-off-by: Mauricio Faria de Oliveira --- arch/powerpc/kernel/iommu.c | 6 -- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/arch/powerpc/kernel/iommu.c b/arch/powerpc/kernel/iommu.c index 37d6e74

[PATCH 3/3] nvme: use the DMA_ATTR_NO_WARN attribute

2016-08-01 Thread Mauricio Faria de Oliveira
Use the DMA_ATTR_NO_WARN attribute for the dma_map_sg() call of the nvme driver that returns BLK_MQ_RQ_QUEUE_BUSY (not for BLK_MQ_RQ_QUEUE_ERROR). Signed-off-by: Mauricio Faria de Oliveira Reviewed-by: Gabriel Krisman Bertazi --- drivers/nvme/host/pci.c | 3 ++- 1 file changed, 2 insertions

[PATCH v4 0/3] dma-mapping, powerpc, nvme: introduce the DMA_ATTR_NO_WARN attribute

2016-08-01 Thread Mauricio Faria de Oliveira
ss warnings from checkpatch.pl (line wrapping and typos) Tested on next-20160801. Mauricio Faria de Oliveira (3): dma-mapping: introduce the DMA_ATTR_NO_WARN attribute powerpc: implement the DMA_ATTR_NO_WARN attribute nvme: use the DMA_ATTR_NO_WARN attribute Documentation/DMA-att

[PATCH v4 0/3] dma-mapping, powerpc, nvme: introduce the DMA_ATTR_NO_WARN attribute

2016-08-01 Thread Mauricio Faria de Oliveira
e wrapping and typos) Tested on next-20160801. Mauricio Faria de Oliveira (3): dma-mapping: introduce the DMA_ATTR_NO_WARN attribute powerpc: implement the DMA_ATTR_NO_WARN attribute nvme: use the DMA_ATTR_NO_WARN attribute Documentation/DMA-attributes.txt | 17 + arch/powe

[PATCH v3 3/3] powerpc: implement DMA_ATTR_NO_WARN

2016-07-08 Thread Mauricio Faria de Oliveira
Add support for the DMA_ATTR_NO_WARN attribute on powerpc iommu code. Signed-off-by: Mauricio Faria de Oliveira <mauri...@linux.vnet.ibm.com> --- Changelog: v3: - powerpc: none v2: - all: address warnings from checkpatch.pl (line wrapping and typos) arch/powerpc/kernel/iommu

[PATCH v3 1/3] dma: introduce DMA_ATTR_NO_WARN

2016-07-08 Thread Mauricio Faria de Oliveira
Introduce the DMA_ATTR_NO_WARN attribute, and document it. Signed-off-by: Mauricio Faria de Oliveira <mauri...@linux.vnet.ibm.com> --- Changelog: v3: - dma: none. v2: - all: address warnings from checkpatch.pl (line wrapping and typos) Documentation/DMA-attributes.tx

[PATCH v3 3/3] powerpc: implement DMA_ATTR_NO_WARN

2016-07-08 Thread Mauricio Faria de Oliveira
Add support for the DMA_ATTR_NO_WARN attribute on powerpc iommu code. Signed-off-by: Mauricio Faria de Oliveira --- Changelog: v3: - powerpc: none v2: - all: address warnings from checkpatch.pl (line wrapping and typos) arch/powerpc/kernel/iommu.c | 6 -- 1 file changed, 4 insertions

[PATCH v3 1/3] dma: introduce DMA_ATTR_NO_WARN

2016-07-08 Thread Mauricio Faria de Oliveira
Introduce the DMA_ATTR_NO_WARN attribute, and document it. Signed-off-by: Mauricio Faria de Oliveira --- Changelog: v3: - dma: none. v2: - all: address warnings from checkpatch.pl (line wrapping and typos) Documentation/DMA-attributes.txt | 17 + include/linux/dma-attrs.h

[PATCH v3 2/3] nvme: implement DMA_ATTR_NO_WARN

2016-07-08 Thread Mauricio Faria de Oliveira
Use the DMA_ATTR_NO_WARN attribute on dma_map_sg() calls of nvme driver. Signed-off-by: Mauricio Faria de Oliveira <mauri...@linux.vnet.ibm.com> Reviewed-by: Gabriel Krisman Bertazi <kris...@linux.vnet.ibm.com> --- Changelog: v3: - nvme: use DMA_ATTR_NO_WARN when ret = BLK_MQ_RQ_QU

[PATCH v3 2/3] nvme: implement DMA_ATTR_NO_WARN

2016-07-08 Thread Mauricio Faria de Oliveira
Use the DMA_ATTR_NO_WARN attribute on dma_map_sg() calls of nvme driver. Signed-off-by: Mauricio Faria de Oliveira Reviewed-by: Gabriel Krisman Bertazi --- Changelog: v3: - nvme: use DMA_ATTR_NO_WARN when ret = BLK_MQ_RQ_QUEUE_BUSY (io will be requeued) but not when ret

[PATCH v3 0/3] dma, nvme, powerpc: introduce and implement DMA_ATTR_NO_WARN

2016-07-08 Thread Mauricio Faria de Oliveira
nvme: use DMA_ATTR_NO_WARN when ret = BLK_MQ_RQ_QUEUE_BUSY (io will be requeued) but not when ret = BLK_MQ_RQ_QUEUE_ERROR (io will be failed). thanks: Masayoshi Mizuma <m.miz...@jp.fujitsu.com> v2: - all: address warnings from checkpatch.pl (line wrapping and typos) Mauricio Faria de Oli

[PATCH v3 0/3] dma, nvme, powerpc: introduce and implement DMA_ATTR_NO_WARN

2016-07-08 Thread Mauricio Faria de Oliveira
nvme: use DMA_ATTR_NO_WARN when ret = BLK_MQ_RQ_QUEUE_BUSY (io will be requeued) but not when ret = BLK_MQ_RQ_QUEUE_ERROR (io will be failed). thanks: Masayoshi Mizuma v2: - all: address warnings from checkpatch.pl (line wrapping and typos) Mauricio Faria de Oliveira (3): dma:

Re: [PATCH v2 2/3] nvme: implement DMA_ATTR_NO_WARN

2016-07-08 Thread Mauricio Faria de Oliveira
On 07/08/2016 04:54 AM, Masayoshi Mizuma wrote: Here, I think the error messages should not be suppressed because the return value of nvme_map_data() is BLK_MQ_RQ_QUEUE_ERROR, so the IO returns as -EIO. Agree; good point. fixed in v3. Thanks for reviewing. -- Mauricio Faria de Oliveira IBM

Re: [PATCH v2 2/3] nvme: implement DMA_ATTR_NO_WARN

2016-07-08 Thread Mauricio Faria de Oliveira
On 07/08/2016 04:54 AM, Masayoshi Mizuma wrote: Here, I think the error messages should not be suppressed because the return value of nvme_map_data() is BLK_MQ_RQ_QUEUE_ERROR, so the IO returns as -EIO. Agree; good point. fixed in v3. Thanks for reviewing. -- Mauricio Faria de Oliveira IBM

Re: [PATCH 2/3] nvme: implement DMA_ATTR_NO_WARN

2016-07-07 Thread Mauricio Faria de Oliveira
On 07/06/2016 09:41 PM, Gabriel Krisman Bertazi wrote: checkpatch.pl complains about line wrapping. Other than that, this looks good to me. I'll submit a v2 w/ that and typos fixed. Thanks for reviewing. -- Mauricio Faria de Oliveira IBM Linux Technology Center

Re: [PATCH 2/3] nvme: implement DMA_ATTR_NO_WARN

2016-07-07 Thread Mauricio Faria de Oliveira
On 07/06/2016 09:41 PM, Gabriel Krisman Bertazi wrote: checkpatch.pl complains about line wrapping. Other than that, this looks good to me. I'll submit a v2 w/ that and typos fixed. Thanks for reviewing. -- Mauricio Faria de Oliveira IBM Linux Technology Center

[PATCH v2 1/3] dma: introduce DMA_ATTR_NO_WARN

2016-07-07 Thread Mauricio Faria de Oliveira
Introduce the DMA_ATTR_NO_WARN attribute, and document it. Signed-off-by: Mauricio Faria de Oliveira <mauri...@linux.vnet.ibm.com> --- Changelog: v2: - address warnings from checkpatch.pl (line wrapping and typos) Documentation/DMA-attributes.txt | 17 + include/lin

[PATCH v2 0/3] dma, nvme, powerpc: introduce and implement DMA_ATTR_NO_WARN

2016-07-07 Thread Mauricio Faria de Oliveira
s warnings from checkpatch.pl (line wrapping and typos) Mauricio Faria de Oliveira (3): dma: introduce DMA_ATTR_NO_WARN nvme: implement DMA_ATTR_NO_WARN powerpc: implement DMA_ATTR_NO_WARN Documentation/DMA-attributes.txt | 17 + arch/powerpc/kernel/iommu.c | 6 -

[PATCH v2 3/3] powerpc: implement DMA_ATTR_NO_WARN

2016-07-07 Thread Mauricio Faria de Oliveira
Add support for the DMA_ATTR_NO_WARN attribute on powerpc iommu code. Signed-off-by: Mauricio Faria de Oliveira <mauri...@linux.vnet.ibm.com> --- Changelog: v2: - address warnings from checkpatch.pl (line wrapping and typos) arch/powerpc/kernel/iommu.c | 6 -- 1 file chan

[PATCH v2 1/3] dma: introduce DMA_ATTR_NO_WARN

2016-07-07 Thread Mauricio Faria de Oliveira
Introduce the DMA_ATTR_NO_WARN attribute, and document it. Signed-off-by: Mauricio Faria de Oliveira --- Changelog: v2: - address warnings from checkpatch.pl (line wrapping and typos) Documentation/DMA-attributes.txt | 17 + include/linux/dma-attrs.h| 1 + 2 files

[PATCH v2 0/3] dma, nvme, powerpc: introduce and implement DMA_ATTR_NO_WARN

2016-07-07 Thread Mauricio Faria de Oliveira
s warnings from checkpatch.pl (line wrapping and typos) Mauricio Faria de Oliveira (3): dma: introduce DMA_ATTR_NO_WARN nvme: implement DMA_ATTR_NO_WARN powerpc: implement DMA_ATTR_NO_WARN Documentation/DMA-attributes.txt | 17 + arch/powerpc/kernel/iommu.c | 6 -

[PATCH v2 3/3] powerpc: implement DMA_ATTR_NO_WARN

2016-07-07 Thread Mauricio Faria de Oliveira
Add support for the DMA_ATTR_NO_WARN attribute on powerpc iommu code. Signed-off-by: Mauricio Faria de Oliveira --- Changelog: v2: - address warnings from checkpatch.pl (line wrapping and typos) arch/powerpc/kernel/iommu.c | 6 -- 1 file changed, 4 insertions(+), 2 deletions(-) diff

[PATCH v2 2/3] nvme: implement DMA_ATTR_NO_WARN

2016-07-07 Thread Mauricio Faria de Oliveira
Use the DMA_ATTR_NO_WARN attribute on dma_map_sg() calls of nvme driver. Signed-off-by: Mauricio Faria de Oliveira <mauri...@linux.vnet.ibm.com> Reviewed-by: Gabriel Krisman Bertazi <kris...@linux.vnet.ibm.com> --- Changelog: v2: - address warnings from checkpatch.pl (line wrappi

[PATCH v2 2/3] nvme: implement DMA_ATTR_NO_WARN

2016-07-07 Thread Mauricio Faria de Oliveira
Use the DMA_ATTR_NO_WARN attribute on dma_map_sg() calls of nvme driver. Signed-off-by: Mauricio Faria de Oliveira Reviewed-by: Gabriel Krisman Bertazi --- Changelog: v2: - address warnings from checkpatch.pl (line wrapping and typos) drivers/nvme/host/pci.c | 12 ++-- 1 file

[PATCH 0/3] dma, nvme, powerpc: introduce and implement DMA_ATTR_NO_WARN

2016-07-06 Thread Mauricio Faria de Oliveira
with error messages at least on powerpc: "iommu_alloc failed") - Patch 3/3 implements support for it on powerpc arch (where this problem was observed. It's possible to extend support for more archs if the patchset is welcome). Mauricio Faria de Oliveira

[PATCH 1/3] dma: introduce DMA_ATTR_NO_WARN

2016-07-06 Thread Mauricio Faria de Oliveira
Introduce the DMA_ATTR_NO_WARN attribute, and document it. Signed-off-by: Mauricio Faria de Oliveira <mauri...@linux.vnet.ibm.com> --- Documentation/DMA-attributes.txt | 17 + include/linux/dma-attrs.h| 1 + 2 files changed, 18 insertions(+) diff --git a/Documen

[PATCH 0/3] dma, nvme, powerpc: introduce and implement DMA_ATTR_NO_WARN

2016-07-06 Thread Mauricio Faria de Oliveira
with error messages at least on powerpc: "iommu_alloc failed") - Patch 3/3 implements support for it on powerpc arch (where this problem was observed. It's possible to extend support for more archs if the patchset is welcome). Mauricio Faria de Oliveira

[PATCH 1/3] dma: introduce DMA_ATTR_NO_WARN

2016-07-06 Thread Mauricio Faria de Oliveira
Introduce the DMA_ATTR_NO_WARN attribute, and document it. Signed-off-by: Mauricio Faria de Oliveira --- Documentation/DMA-attributes.txt | 17 + include/linux/dma-attrs.h| 1 + 2 files changed, 18 insertions(+) diff --git a/Documentation/DMA-attributes.txt b

[PATCH 3/3] powerpc: implement DMA_ATTR_NO_WARN

2016-07-06 Thread Mauricio Faria de Oliveira
Add support for the DMA_ATTR_NO_WARN attribute on powerpc iommu code. Signed-off-by: Mauricio Faria de Oliveira <mauri...@linux.vnet.ibm.com> --- arch/powerpc/kernel/iommu.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/arch/powerpc/kernel/iommu.c b/arch/powerpc/

  1   2   >