[Bug 151661] Adaptec 3805 prints "AAC: Host adapter dead -1" every 10 seconds but works fine anyway

https://bugzilla.kernel.org/show_bug.cgi?id=151661 Harold Snel changed: What|Removed |Added CC||har...@snel.ws ---

[PATCH 1/2] ses: use scsi_is_sas_rphy instead of is_sas_attached

Use scsi_is_sas_rphy() instead of is_sas_attached() to decide whether we should obtain the SAS address from a scsi device or not. This will prevent us from tripping on the BUG_ON() in sas_sdev_to_rdev() if the rphy isn't attached to the SAS transport class, like it is with hpsa's logical devices.

[PATCH 2/2] sas: remove is_sas_attached()

As there are no more users of is_sas_attached() left, remove it. Signed-off-by: Johannes Thumshirn --- drivers/scsi/scsi_transport_sas.c | 16 include/scsi/scsi_transport_sas.h | 9 - 2 files changed, 25 deletions(-) diff --git

Re: dm-mpath: always return reservation conflict

On Mon, Aug 15 2016 at 9:08P -0400, Mike Snitzer wrote: > Not sure how Hannes' original patch was overlooked but... It wasn't overlooked. It was very much unresolved. The original thread unraveled to all sorts of PR edge case concerns (and doubt about whether anything

Re: dm-mpath: always return reservation conflict

Not sure how Hannes' original patch was overlooked but... One issue I see with the patch is it will return -EBADE regardless of whether 'queue_if_no_path' is set. That's fine (since path isn't being failed for this case any more). But why not just return error immediately? But taking a step

Re: [PATCH 1/2] ses: use scsi_is_sas_rphy instead of is_sas_attached

r-next] > > > [also build test ERROR on v4.8-rc2 next-20160815] > > > [if your patch is applied to the wrong git tree, please drop us a > > > note to help improve the system] > > > > This is happening because scsi_is_sas_rphy wasn't designed to be > >

[PATCH v2 0/3] Fix panic when a SES device is attached to a hpsa logical volume.

The first patch provides stub implementations for scsi_is_sas_phy() and sas_get_address() for the case that CONFIG_SCSI_SAS_ATTRS is not defined. The second patch implements the actual fix in ses.c by changing the is_sas_attached() call to scsi_is_sas_rphy(). The third and last patch removes

[PATCH v2 2/3] ses: use scsi_is_sas_rphy instead of is_sas_attached

Use scsi_is_sas_rphy() instead of is_sas_attached() to decide whether we should obtain the SAS address from a scsi device or not. This will prevent us from tripping on the BUG_ON() in sas_sdev_to_rdev() if the rphy isn't attached to the SAS transport class, like it is with hpsa's logical devices.

Re: [PATCH 1/2] ses: use scsi_is_sas_rphy instead of is_sas_attached

On Mon, 2016-08-15 at 22:11 +0800, kbuild test robot wrote: > Hi Johannes, > > [auto build test ERROR on scsi/for-next] > [also build test ERROR on v4.8-rc2 next-20160815] > [if your patch is applied to the wrong git tree, please drop us a > note to help improve the system]

[PATCH v2 1/3] sas: provide stub implementations for scsi_is_sas_phy and sas_get_address

Provide stub implementations for scsi_is_sas_phy and sas_get_address for kernel configurations which do not have CONFIG_SCSI_SAS_ATTRS defined. Reported-by: kbuild test robot Suggested-by: James Bottomley Signed-off-by: Johannes Thumshirn

Re: [PATCH 1/2] ses: use scsi_is_sas_rphy instead of is_sas_attached

Hi Johannes, [auto build test ERROR on scsi/for-next] [also build test ERROR on v4.8-rc2 next-20160815] [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/Johannes-Thumshirn/ses-use

Re: [PATCH 1/2] ses: use scsi_is_sas_rphy instead of is_sas_attached

gt; > > > Hi Johannes, > > > > > > > > [auto build test ERROR on scsi/for-next] > > > > [also build test ERROR on v4.8-rc2 next-20160815] > > > > [if your patch is applied to the wrong git tree, please drop us a > > > > note to help i

Re: [PATCH 1/2] ses: use scsi_is_sas_rphy instead of is_sas_attached

On Mon, Aug 15, 2016 at 07:25:53AM -0700, James Bottomley wrote: > On Mon, 2016-08-15 at 22:11 +0800, kbuild test robot wrote: > > Hi Johannes, > > > > [auto build test ERROR on scsi/for-next] > > [also build test ERROR on v4.8-rc2 next-20160815] > > [if your

Re: [PATCH v6 0/2] Block layer support ZAC/ZBC commands

Shaun, > On Aug 14, 2016, at 09:09, Shaun Tancheff wrote: […] >>> >> No, surely not. >> But one of the _big_ advantages for the RB tree is blkdev_discard(). >> Without the RB tree any mkfs program will issue a 'discard' for every >> sector. We will be able to

Re: [RFC] sd: dynamically adjust SD_MAX_WS16_BLOCKS as per the actual logical block size

> "Tom" == Tom Yan writes: Tom, >> 0x7f, the maximum number of block layer sectors that can be >> expressed in a single bio. Tom> Hmm, so when we queue any of the limits, we convert a certain Tom> maximum number of physical sectors (which we has already been Tom>

Re: [PATCH v6 0/2] Block layer support ZAC/ZBC commands

On Mon, Aug 15, 2016 at 11:00 PM, Damien Le Moal wrote: > > Shaun, > >> On Aug 14, 2016, at 09:09, Shaun Tancheff wrote: > […] >>> No, surely not. >>> But one of the _big_ advantages for the RB tree is blkdev_discard(). >>> Without the RB

Re: [RFC] libata-scsi: make sure Maximum Write Same Length is not too large

> "Tom" == Tom Yan writes: Tom, Tom> The thing is, as of ACS-4, blocks that carry DSM/TRIM LBA Range Tom> Entries are always 512-byte. Lovely. And SAT conveniently ignores this entirely. Tom> Honestly, I have no idea how that would work on a 4Kn SSD, if it is Tom> /

Re: [PATCH] scsi: blacklist all RDAC devices for BLIST_NO_ULD_ATTACH

> "Xose" == Xose Vazquez Perez writes: Xose> "Universal Xport" LUN is used for in-band storage array Xose> management. Applied to 4.8/scsi-fixes. -- Martin K. Petersen Oracle Linux Engineering -- To unsubscribe from this list: send the line "unsubscribe

Re: [PATCH v2 2/2] sd: check BLK_DEF_MAX_SECTORS against max_dev_sectors

> "Tom" == Tom Yan writes: Tom, >> It would be pretty unusual for a device that is smart enough to >> report a transfer length limit to be constrained to 1 MB and change. Tom> Well, it is done pretty much for libata's SATL. But why? >> rw_max =

Re: [PATCH v2 2/3] ses: use scsi_is_sas_rphy instead of is_sas_attached

Hi Johannes, [auto build test ERROR on scsi/for-next] [also build test ERROR on v4.8-rc2 next-20160815] [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/Johannes-Thumshirn/Fix-panic-when-a-SES

[PATCH] fcoe: provide translation table between Ethernet and FC port speeds

Provide a translation table between Ethernet and FC port speeds so odd speeds (from a Ethernet POV) like 8 Gbit are correctly mapped to sysfs and open-fcoe's fcoeadm. Before: Description: BCM57840 NetXtreme II 10/20-Gigabit Ethernet Revision: 11 Manufacturer: Broadcom

[PATCH v2 3/3] sas: remove is_sas_attached()

As there are no more users of is_sas_attached() left, remove it. Signed-off-by: Johannes Thumshirn --- drivers/scsi/scsi_transport_sas.c | 16 include/scsi/scsi_transport_sas.h | 6 -- 2 files changed, 22 deletions(-) diff --git

Re: [PATCH v2 1/3] sas: provide stub implementations for scsi_is_sas_phy and sas_get_address

On Mon, 2016-08-15 at 17:12 +0200, Johannes Thumshirn wrote: > +static inline u64 sas_get_address(struct scsi_device *sdev) > +{ > + return 0; > +} To be honest, we don't want this. We do want the code to fail to compile if you ever use sas_get_address where you shouldn't because the code

Re: [PATCH] scsi: blacklist all RDAC devices for BLIST_NO_ULD_ATTACH

On 8/12/16, 5:56 PM, "Xose Vazquez Perez" wrote: "Universal Xport" LUN is used for in-band storage array management. Cc: Sean Stewart Cc: Christophe Varoqui Cc: James E.J. Bottomley

Re: [GIT PULL] [PATCH v4 00/26] Delete CURRENT_TIME and CURRENT_TIME_SEC macros

On Sat, Aug 13, 2016 at 03:48:12PM -0700, Deepa Dinamani wrote: > The series is aimed at getting rid of CURRENT_TIME and CURRENT_TIME_SEC > macros. > The macros are not y2038 safe. There is no plan to transition them into being > y2038 safe. > ktime_get_* api's can be used in their place. And,

RE: [PATCH V4 0/2] smartpqi: initial commit of Microsemi smartpqi driver

> -Original Message- > From: Martin K. Petersen [mailto:martin.peter...@oracle.com] > Sent: Friday, August 12, 2016 3:10 PM > To: Don Brace > Cc: Martin K. Petersen; j...@linux.vnet.ibm.com; Viswas G; Mahesh > Rajashekhara; h...@infradead.org; Scott Teel; Kevin Barnett; Justin Lindley; >

Re: [PATCH] scsi: introduce a quirk for false cache reporting

> "Oliver" == Oliver Neukum writes: Oliver, Oliver> wce_default_on controls the default if the device provides no Oliver> indication. The problem here is that the indication the device Oliver> provides must be overridden, as they are false. Can't you just blacklist the

Re: [Bug 153171] New: scsi host6: runtime PM trying to activate child device host6 but parent (2-2:1.0) is not active

Am 15.08.2016 um 21:55 schrieb bugzilla-dae...@bugzilla.kernel.org: > https://bugzilla.kernel.org/show_bug.cgi?id=153171 > > Bug ID: 153171 >Summary: scsi host6: runtime PM trying to activate child device > host6 but parent (2-2:1.0) is not active >

Re: Time to make dynamically allocated devt the default for scsi disks?

On 08/14/2016 11:23 AM, Dan Williams wrote: [ adding Bart back to the cc ] On Sun, Aug 14, 2016 at 11:08 AM, Dan Williams wrote: On Sun, Aug 14, 2016 at 10:20 AM, James Bottomley wrote: [..] I like it. I still think the bdi

[Bug 153171] scsi host6: runtime PM trying to activate child device host6 but parent (2-2:1.0) is not active

https://bugzilla.kernel.org/show_bug.cgi?id=153171 --- Comment #1 from Cristian Aravena Romero --- Created attachment 228941 --> https://bugzilla.kernel.org/attachment.cgi?id=228941=edit lspci -vvnn -- You are receiving this mail because: You are the assignee for the bug.

[Bug 153171] New: scsi host6: runtime PM trying to activate child device host6 but parent (2-2:1.0) is not active

https://bugzilla.kernel.org/show_bug.cgi?id=153171 Bug ID: 153171 Summary: scsi host6: runtime PM trying to activate child device host6 but parent (2-2:1.0) is not active Product: IO/Storage Version: 2.5 Kernel Version:

Re: [PATCH v2] scsi: fix upper bounds check of sense key in scsi_sense_key_string()

> "Tyrel" == Tyrel Datwyler writes: Tyrel> Commit 655ee63cf371 added a "Completed" sense string with key 0xF Tyrel> to snstext[], but failed to updated the upper bounds check of the Tyrel> sense key in scsi_sense_key_string(). Applied to 4.8/scsi-fixes. --