https://bugzilla.kernel.org/show_bug.cgi?id=197877
Bug ID: 197877
Summary: arcmsr fails to initialize Areca ARC-1110/ARC-1120 on
some systems
Product: SCSI Drivers
Version: 2.5
Kernel Version: 3.18+
Hardware: Intel
Since commit 28a0bc4120d3 ("scsi: sd: Implement blacklist option for
WRITE SAME w/ UNMAP") bit 31 is a valid device information flag.
Separate device information flags and return codes such that it
becomes possible to check whether or not scsi_get_device_flags_keyed().
succeeded. This patch also
Additionally, suppress recently introduced sparse warnings related
to blacklist flags.
Signed-off-by: Bart Van Assche
Cc: Christoph Hellwig
Cc: Hannes Reinecke
Cc: Johannes Thumshirn
---
drivers/scsi/scsi_devinfo.c
This patch does not change any functionality.
Signed-off-by: Bart Van Assche
Cc: Christoph Hellwig
Cc: Hannes Reinecke
Cc: Johannes Thumshirn
---
drivers/scsi/scsi_devinfo.c | 9 +
drivers/scsi/scsi_priv.h| 4
Hello Martin,
There are multiple issues with the device information flag handling (a.k.a.
blacklist flags):
* For neither scsi_get_device_flags() nor scsi_get_device_flags_keyed() it
is possible to determine whether an error code has been returned or whether
the flag with bit position 31 was
Hello Martin,
There are multiple issues with the device information flag handling (a.k.a.
blacklist flags):
* For neither scsi_get_device_flags() nor scsi_get_device_flags_keyed() it
is possible to determine whether an error code has been returned or whether
the flag with bit position 31 was
This patch does not change any functionality.
Signed-off-by: Bart Van Assche
Cc: Christoph Hellwig
Cc: Hannes Reinecke
Cc: Johannes Thumshirn
---
drivers/scsi/scsi_devinfo.c | 9 +
drivers/scsi/scsi_priv.h| 4
Additionally, suppress recently introduced sparse warnings related
to blacklist flags.
Signed-off-by: Bart Van Assche
Cc: Christoph Hellwig
Cc: Hannes Reinecke
Cc: Johannes Thumshirn
---
drivers/scsi/scsi_devinfo.c
Since commit 28a0bc4120d3 ("scsi: sd: Implement blacklist option for
WRITE SAME w/ UNMAP") bit 31 is a valid device information flag.
Separate device information flags and return codes such that it
becomes possible to check whether or not scsi_get_device_flags_keyed().
succeeded. This patch also
On Tue, Nov 14, 2017 at 8:36 AM, James Bottomley
wrote:
>
> Hannes Reinecke (14):
> scsi: scsi_devinfo: Reformat blacklist flags
Ugh, that's just really ugly, but it's also wrong.
Just having long lines would probably have been much preferable, and
https://bugzilla.kernel.org/show_bug.cgi?id=197875
Bart Van Assche (bvanass...@acm.org) changed:
What|Removed |Added
CC||bvanass...@acm.org
https://bugzilla.kernel.org/show_bug.cgi?id=197875
Chuck Burt (chuck.burt+kernel@gmail.com) changed:
What|Removed |Added
Kernel Version|4.13.x |4.13+
--
https://bugzilla.kernel.org/show_bug.cgi?id=197875
Bug ID: 197875
Summary: Processes hang on attempted access of WDC WD30-EZRX
3TB HDD on HP Z420 Workstation
Product: IO/Storage
Version: 2.5
Kernel Version: 4.13.x
We've been adding this as a quirk on a per device basis hoping that
newer disk enclosures would do better, but that has not happened,
so simply apply this quirk to all Seagate devices.
Signed-off-by: Hans de Goede
---
drivers/usb/storage/uas-detect.h | 4
1 file
On Tue, 2017-11-14 at 08:55 +0800, Ming Lei wrote:
> Hi James,
>
> On Mon, Nov 13, 2017 at 10:55:52AM -0800, James Bottomley wrote:
> >
> > On Sat, 2017-11-11 at 10:43 +0800, Ming Lei wrote:
> > >
> > > So from CPU1's review, cmd->cmnd is in a remote NUMA node,
> > > __scsi_format_command() is
On 4/12/17 12:30 AM, Nicholas A. Bellinger wrote:
> On Mon, 2017-04-10 at 18:08 +0200, Christoph Hellwig wrote:
>> Use the pscsi driver to support arbitrary command passthrough
>> instead.
>>
> The people who are actively using iblock_execute_write_same_direct() are
> doing so in the context of
Hi,
On 11/14/2017 04:25 PM, Alan Stern wrote:
On Tue, 14 Nov 2017, Hans de Goede wrote:
Hi,
On 14-11-17 15:00, Hans de Goede wrote:
Just like all previous UAS capable Seagate disk enclosures, this
one needs a US_FL_NO_ATA_1X quirk.
Cc: sta...@vger.kernel.org # 3.16
Reported-by: Wido
On Tue, 2017-11-14 at 18:01 +0100, Jack Wang wrote:
> I suspect we run into same bug you were trying to fix in this patch
> set. we're running in v4.4.50
>
> I was trying to reproduce it, but no lucky yet, do you still have your
> reproducer?
Hello Jack,
I can reproduce this about every fifth
2016-11-14 19:35 GMT+01:00 Bart Van Assche :
> On 11/12/2016 09:47 PM, James Bottomley wrote:
>>
>> On Fri, 2016-11-11 at 16:38 -0800, Bart Van Assche wrote:
>>>
>>> Hello James and Martin,
>>>
>>> This short patch series fixes a deadlock that I ran into for the
>>>
This is mostly updates of the usual suspects: lpfc, qla2xxx, hisi_sas,
megaraid_sas, pm80xx, mpt3sas, be2iscsi, hpsa. and a host of minor
updates.
There's no major behaviour change or additions to the core in all of
this, so the potential for regressions should be small (biggest
potential being
On Tue, 14 Nov 2017, Hans de Goede wrote:
> Hi,
>
> On 14-11-17 15:00, Hans de Goede wrote:
> > Just like all previous UAS capable Seagate disk enclosures, this
> > one needs a US_FL_NO_ATA_1X quirk.
> >
> > Cc: sta...@vger.kernel.org # 3.16
> > Reported-by: Wido
> >
Hi,
On 14-11-17 15:00, Hans de Goede wrote:
Just like all previous UAS capable Seagate disk enclosures, this
one needs a US_FL_NO_ATA_1X quirk.
Cc: sta...@vger.kernel.org # 3.16
Reported-by: Wido
Signed-off-by: Hans de Goede
So far we've been adding
Just like all previous UAS capable Seagate disk enclosures, this
one needs a US_FL_NO_ATA_1X quirk.
Cc: sta...@vger.kernel.org # 3.16
Reported-by: Wido
Signed-off-by: Hans de Goede
---
drivers/usb/storage/unusual_uas.h | 7 +++
1 file changed, 7
23 matches
Mail list logo