- Original Message -
> From: "Laurence Oberman"
> To: "Mike Snitzer"
> Cc: "Bart Van Assche" , dm-de...@redhat.com,
> linux-scsi@vger.kernel.org
> Sent: Tuesday, August 2, 2016 10:18:30 PM
> Subject: Re: dm-mq and end_clone_request()
>
>
>
> - Original Message -
> > From: "M
Hi Arnd,
[auto build test ERROR on scsi/for-next]
[also build test ERROR on v4.7 next-20160802]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci/linux/commits/Arnd-Bergmann/bfa-fix-W-1-build-warnings/20160803
Hi All,
I'm glad to announce SCST 3.2 pre-release code freeze in the SCST SVN branch
3.2.x.
You can get it by command:
$ svn co https://scst.svn.sourceforge.net/svnroot/scst/branches/3.2.x
It is going to be released after few weeks of testing, if no significant issues
found.
SCST is alternat
- Original Message -
> From: "Mike Snitzer"
> To: "Laurence Oberman"
> Cc: "Bart Van Assche" , dm-de...@redhat.com,
> linux-scsi@vger.kernel.org
> Sent: Tuesday, August 2, 2016 10:10:12 PM
> Subject: Re: dm-mq and end_clone_request()
>
> On Tue, Aug 02 2016 at 9:33pm -0400,
> Laurenc
On Tue, Aug 02 2016 at 9:33pm -0400,
Laurence Oberman wrote:
> Hi Bart
>
> I simplified the test to 2 simple scripts and only running against one XFS
> file system.
> Can you validate these and tell me if its enough to emulate what you are
> doing.
> Perhaps our test-suite is too simple.
>
>
Hi Bart
I simplified the test to 2 simple scripts and only running against one XFS file
system.
Can you validate these and tell me if its enough to emulate what you are doing.
Perhaps our test-suite is too simple.
Start the test
# cat run_test.sh
#!/bin/bash
logger "Starting Bart's test"
#for i
Hannes, Shaun,
Let me add some more comments.
> On Aug 2, 2016, at 23:35, Hannes Reinecke wrote:
>
> On 08/01/2016 07:07 PM, Shaun Tancheff wrote:
>> On Mon, Aug 1, 2016 at 4:41 AM, Christoph Hellwig wrote:
>>>
>>> Can you please integrate this with Hannes series so that it uses
>>> his cache
I am yet to get a respose from you based on your promise
--
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
On Tue, Aug 02 2016 at 8:19pm -0400,
Bart Van Assche wrote:
> On 08/02/2016 10:45 AM, Mike Snitzer wrote:
> > Please do these same tests against a v4.7 kernel with the 4 patches from
> > this branch applied (no need for your other debug patches):
> > https://git.kernel.org/cgit/linux/kernel/git/
On Fri, 2016-07-22 at 17:23 -0700, James Smart wrote:
A couple comments.
> Add FC LLDD loopback driver to test FC host and target transport
> within
> nvme-fabrics
>
> To aid in the development and testing of the lower-level api of the
> FC
> transport, this loopback driver has been created to a
On 08/02/2016 10:45 AM, Mike Snitzer wrote:
> Please do these same tests against a v4.7 kernel with the 4 patches from
> this branch applied (no need for your other debug patches):
> https://git.kernel.org/cgit/linux/kernel/git/device-mapper/linux-dm.git/log/?h=dm-4.7-mpath-fixes
>
> I've had good
On Mon, Aug 01 2016 at 6:41pm -0400,
Bart Van Assche wrote:
> On 08/01/2016 01:46 PM, Mike Snitzer wrote:
> > Please retry both variant (CONFIG_DM_MQ_DEFAULT=y first) with this patch
> > applied. Interested to see if things look better for you (WARN_ON_ONCEs
> > added just to see if we hit the
Hi,
I'm not completely sure I got the cause for this one completely right.
Still, it does looks like the correct fix and a good improvement in the
overall, so I'm making it an RFC for now to gather some feedback.
Let me hear your thoughts.
-- >8 --
When notifying blk-mq about CPU removals while
I find that the developers often just specified the numeric value
when calling a macro which is defined with a parameter for access permission.
As we know, these numeric value for access permission have had the
corresponding macro,
and that using macro can improve the robustness and readability of
We get 128 warnings about global functions without a declaration
in the bfa scsi driver when building with W=1, more than any other
driver, e.g.
bfa/bfad.c:1502:1: error: no previous prototype for 'restart_bfa'
bfa/bfad_attr.c:447:1: error: no previous prototype for
'bfad_im_issue_fc_host_lip'
bf
On 08/01/2016 07:07 PM, Shaun Tancheff wrote:
> On Mon, Aug 1, 2016 at 4:41 AM, Christoph Hellwig wrote:
>>
>> Can you please integrate this with Hannes series so that it uses
>> his cache of the zone information?
>
> Adding Hannes and Damien to Cc.
>
> Christoph,
>
> I can make a patch the mar
A significant chunk of the functions in the bfa_fcbuild.c
file are never called, this removes them. I've split this
out from the patch to remove other unused functions, as
we are removing half the file here, and this seems to
be intended as a generic library.
We could mark them as 'static __maybe_
This is a collection of additional functions that are not called anywhere
in the driver, all being removed in this patch.
Alternatively, we could mark them as 'static __maybe_unused', to leave
the implementation around but not cause them to end up in the object
code.
Signed-off-by: Arnd Bergmann
Building with W=1 shows some warnings about local variables that
are initialized but never used:
bfa/bfad_attr.c: In function 'bfad_im_vport_delete':
bfa/bfad_attr.c:490:22: error: variable 'port' set but not used
bfa/bfa_fcs_rport.c: In function 'bfa_fcs_rport_process_adisc':
bfa/bfa_fcs_rport.c:
The global "supported_fc4s" and "max_xfer_size" variables have rather
generic names that might conflict with the same identifiers used in
other drivers, and we cannot make them 'static' because they are both
used across multiple files.
This adds a 'bfa_' prefix to ensure the identifiers are global
I tried to build an allmodconfig kernel with W=1, and the bfa
driver stuck out for having the most warnings in one file, so
I decided to send patches for all of these and make the driver
build cleanly with the extra warnings enabled.
As most warnings were for functions that lacked a 'static',
I ma
I find that the developers often just specified the numeric value
when calling a macro which is defined with a parameter for access permission.
As we know, these numeric value for access permission have had the
corresponding macro,
and that using macro can improve the robustness and readability of
I find that the developers often just specified the numeric value
when calling a macro which is defined with a parameter for access permission.
As we know, these numeric value for access permission have had the
corresponding macro,
and that using macro can improve the robustness and readability of
I find that the developers often just specified the numeric value
when calling a macro which is defined with a parameter for access permission.
As we know, these numeric value for access permission have had the
corresponding macro,
and that using macro can improve the robustness and readability of
I find that the developers often just specified the numeric value
when calling a macro which is defined with a parameter for access permission.
As we know, these numeric value for access permission have had the
corresponding macro,
and that using macro can improve the robustness and readability of
I find that the developers often just specified the numeric value
when calling a macro which is defined with a parameter for access permission.
As we know, these numeric value for access permission have had the
corresponding macro,
and that using macro can improve the robustness and readability of
I find that the developers often just specified the numeric value
when calling a macro which is defined with a parameter for access permission.
As we know, these numeric value for access permission have had the
corresponding macro,
and that using macro can improve the robustness and readability of
I find that the developers often just specified the numeric value
when calling a macro which is defined with a parameter for access permission.
As we know, these numeric value for access permission have had the
corresponding macro,
and that using macro can improve the robustness and readability of
I find that the developers often just specified the numeric value
when calling a macro which is defined with a parameter for access permission.
As we know, these numeric value for access permission have had the
corresponding macro,
and that using macro can improve the robustness and readability of
I find that the developers often just specified the numeric value
when calling a macro which is defined with a parameter for access permission.
As we know, these numeric value for access permission have had the
corresponding macro,
and that using macro can improve the robustness and readability of
I find that the developers often just specified the numeric value
when calling a macro which is defined with a parameter for access permission.
As we know, these numeric value for access permission have had the
corresponding macro,
and that using macro can improve the robustness and readability of
I find that the developers often just specified the numeric value
when calling a macro which is defined with a parameter for access permission.
As we know, these numeric value for access permission have had the
corresponding macro,
and that using macro can improve the robustness and readability of
On Tue, 2016-08-02 at 18:39 +0800, Baole Ni wrote:
> I find that the developers often just specified the numeric value
> when calling a macro which is defined with a parameter for access
> permission. As we know, these numeric value for access permission
> have had the corresponding macro, and th
I find that the developers often just specified the numeric value
when calling a macro which is defined with a parameter for access permission.
As we know, these numeric value for access permission have had the
corresponding macro,
and that using macro can improve the robustness and readability of
I find that the developers often just specified the numeric value
when calling a macro which is defined with a parameter for access permission.
As we know, these numeric value for access permission have had the
corresponding macro,
and that using macro can improve the robustness and readability of
- Original Message -
> From: "Baole Ni"
> To: "don brace" , "len brown" ,
> pa...@ucw.cz,
> gre...@linuxfoundation.org, h...@zytor.com, x...@kernel.org
> Cc: "iss storagedev" , "esc storagedev"
> ,
> linux-scsi@vger.kernel.org, linux-ker...@vger.kernel.org, "chuansheng liu"
> , "baole
I find that the developers often just specified the numeric value
when calling a macro which is defined with a parameter for access permission.
As we know, these numeric value for access permission have had the
corresponding macro,
and that using macro can improve the robustness and readability of
Hannes sent this patch a bit more than a year ago, but it got silently
dropped. When using the pNFS SCSI layout we can easily hit a
failover "livelock" without it as the reservation conflicts on a
newly detected device that doesn't have layouts yet, or after a fency
will keep failing over from one
From: Hannes Reinecke
If dm-mpath encounters an reservation conflict it should not fail the
path (as communication with the target is not affected) but should
rather retry on another path. However, in doing so we might be inducing
a ping-pong between paths, with no guarantee of any forward progre
I find that the developers often just specified the numeric value
when calling a macro which is defined with a parameter for access permission.
As we know, these numeric value for access permission have had the
corresponding macro,
and that using macro can improve the robustness and readability of
On Mon, Jul 25, 2016 at 07:00:33AM +, Wei Yongjun wrote:
> Use kfree_skb() instead of kfree() to free sk_buff.
>
> Signed-off-by: Wei Yongjun
Acked-by: Johannes Thumshirn
--
Johannes Thumshirn Storage
jthumsh...@suse.de
On Tue, Jul 12, 2016 at 10:24:36AM +0200, Oliver Neukum wrote:
> Some SATA to USB bridges fail to cooperate with some
> drives resulting in no cache being present being reported
> to the host. That causes the host to skip sending
> a command to synchronize caches. That causes data loss
> when the d
42 matches
Mail list logo
