port_detect is only called from the module_init routine and thus implicitly
serialized, so remove the driver lock which was held over potentially
sleeping function calls.
Signed-off-by: Christoph Hellwig
Reported-by: Arthur Marsh
Tested-by: Arthur Marsh
---
drivers/scsi/eata.c | 9 -
1
On Mon, Jul 14, 2014 at 08:15:17AM +0200, Hannes Reinecke wrote:
> Limiting max_lun to 255 will make the driver to _not_ respond to LUNs higher
> than that; ie Well-known LUN won't work here.
> Also the SCSI stack will be using REPORT LUNS anyway since you're
> advertising SPC-2 compliance. So your
On Mon, Jul 14, 2014 at 10:29:04AM +0200, Paul Bolle wrote:
> 0) Commit 73685a458f2e ("tgt: removal") landed in next-20140714. It
> states that "the CONFIG_SCSI_TGT, CONFIG_SCSI_SRP_TGT_ATTRS and
> CONFIG_SCSI_FC_TGT_ATTRS kbuild variable[s] [...] are no longer needed&qu
0) Commit 73685a458f2e ("tgt: removal") landed in next-20140714. It
states that "the CONFIG_SCSI_TGT, CONFIG_SCSI_SRP_TGT_ATTRS and
CONFIG_SCSI_FC_TGT_ATTRS kbuild variable[s] [...] are no longer needed".
It removed the Kconfig entry for SCSI_SRP_TGT_ATTRS, but it left the
entr
Back when the mpt3sas driver was first posted I suggested that it should
be merged into mpt2sas, but my proposal didn't get much traction.
Illumos has now produced a shared driver and shown that the difference
are basically limited to a different S/G list format [1], and a quick
experiment on the
On 07/14/2014 10:30 AM, Christoph Hellwig wrote:
On Mon, Jul 14, 2014 at 08:15:17AM +0200, Hannes Reinecke wrote:
Limiting max_lun to 255 will make the driver to _not_ respond to LUNs higher
than that; ie Well-known LUN won't work here.
Also the SCSI stack will be using REPORT LUNS anyway since
On Mon, Jul 14, 2014 at 10:57:53AM +0200, Hannes Reinecke wrote:
> Okay, that's fine by me.
Should I take this as a reviewed-by tag?
--
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.k
On 07/14/2014 11:00 AM, Christoph Hellwig wrote:
On Mon, Jul 14, 2014 at 10:57:53AM +0200, Hannes Reinecke wrote:
Okay, that's fine by me.
Should I take this as a reviewed-by tag?
Yes, please do.
Cheers,
Hannes
--
Dr. Hannes Reinecke zSeries & Storage
h...@suse.de
On 7/8/2014 5:48 PM, Christoph Hellwig wrote:
I've pushed out a new scsi-mq.3 branch, which has been rebased on the
latest core-for-3.17 tree + the "RFC: clean up command setup" series
from June 29th. Robert Elliot found a problem with not fully zeroed
out UNMAP CDBs, which is fixed by the sane
On 07/14/2014 10:35 AM, Christoph Hellwig wrote:
Back when the mpt3sas driver was first posted I suggested that it should
be merged into mpt2sas, but my proposal didn't get much traction.
Illumos has now produced a shared driver and shown that the difference
are basically limited to a different
On 14-07-13 06:55 PM, Elliott, Robert (Server Storage) wrote:
-Original Message-
From: linux-scsi-ow...@vger.kernel.org [mailto:linux-scsi-
ow...@vger.kernel.org] On Behalf Of Douglas Gilbert
Sent: Monday, 07 July, 2014 8:31 AM
To: SCSI development list
Subject: [PATCH v2] scsi_debug:
On Mon, 2014-07-14 at 11:22 +0200, Hannes Reinecke wrote:
> On 07/14/2014 10:35 AM, Christoph Hellwig wrote:
> > Back when the mpt3sas driver was first posted I suggested that it should
> > be merged into mpt2sas, but my proposal didn't get much traction.
> >
> > Illumos has now produced a shared d
On 07/14/2014 04:17 PM, James Bottomley wrote:
On Mon, 2014-07-14 at 11:22 +0200, Hannes Reinecke wrote:
On 07/14/2014 10:35 AM, Christoph Hellwig wrote:
Back when the mpt3sas driver was first posted I suggested that it should
be merged into mpt2sas, but my proposal didn't get much traction.
I
On Mon, 2014-07-14 at 16:39 +0200, Hannes Reinecke wrote:
> On 07/14/2014 04:17 PM, James Bottomley wrote:
> > On Mon, 2014-07-14 at 11:22 +0200, Hannes Reinecke wrote:
> >> On 07/14/2014 10:35 AM, Christoph Hellwig wrote:
> >>> Back when the mpt3sas driver was first posted I suggested that it shou
On Tue, Jul 1, 2014 at 9:11 PM, Andy Grover wrote:
> Shaohua Li wrote an initial implementation of this, late last year[1].
> Starting from that, I started working on some alternate implementation
> choices, and ended up with something rather different.
>
> Please take a look and let me know what
On 07/14/2014 04:57 PM, James Bottomley wrote:
On Mon, 2014-07-14 at 16:39 +0200, Hannes Reinecke wrote:
On 07/14/2014 04:17 PM, James Bottomley wrote:
[ .. ]
This isn't really a democracy; it's about who maintains the drivers and
right now it's LSI (or whatever their new name is).
One of th
On 07/14/2014 05:10 PM, Hannes Reinecke wrote:
> On 07/14/2014 04:57 PM, James Bottomley wrote:
>> On Mon, 2014-07-14 at 16:39 +0200, Hannes Reinecke wrote:
>>> On 07/14/2014 04:17 PM, James Bottomley wrote:
> [ .. ]
This isn't really a democracy; it's about who maintains the drivers and
Hi Robert,
On Sun, Jul 13, 2014 at 05:15:15PM +, Elliott, Robert (Server Storage)
wrote:
> > > I will see if that solves the problem with the scsi-mq-3 tree, or
> > > at least some of the bisect trees leading up to it.
> >
> > scsi-mq-3 is still going after 45 minutes. I'll leave it running
On Sat, 12 Jul 2014 03:13:07 +
"Elliott, Robert (Server Storage)" wrote:
>
>
> > -Original Message-
> > From: linux-scsi-ow...@vger.kernel.org [mailto:linux-scsi-
> > ow...@vger.kernel.org] On Behalf Of Joe Lawrence
> ...
> > In your crash stack trace, the scsi error handler has iss
> "James" == James Bottomley writes:
James> I support the concept, since I think everyone told LSI at the
James> time that splitting the drivers would become a maintenance
James> nightmare.
And it is. I'd like to see these drivers merged as well.
James> One of the big reasons we don't have
20 matches
Mail list logo
