[PATCH V2 resend] libata:fix kernel panic when hotplug

In normal condition,if we use sas protocol and hotplug a sata disk on a port,the sas driver will send event "PORTE_BYTES_DMAED" and call function "sas_porte_bytes_dmaed". But if a sata disk is run io and unplug it,then plug a new sata disk,this operation may cause a kernel panic like this: [

Re: [PATCH V2] libata:fix kernel panic when hotplug

Hi, [auto build test ERROR on tj-libata/for-next] [also build test ERROR on v4.7-rc3 next-20160615] [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/DingXiang/libata-fix-kernel-panic-when-hotplug

[PATCH V2] libata:fix kernel panic when hotplug

From: Ding Xiang In normal condition,if we use sas protocol and hotplug a sata disk on a port,the sas driver will send event "PORTE_BYTES_DMAED" and call function "sas_porte_bytes_dmaed". But if a sata disk is run io and unplug it,then plug a new sata disk,this operation

Re: [PATCH v5] ibmvscsis: Initial commit of IBM VSCSI Tgt Driver

On Wed, 2016-06-15 at 18:41 -0500, Bryant G. Ly wrote: > The driver provides a virtual SCSI device on IBM Power Servers. [] >  MAINTAINERS  |   11 + >  drivers/scsi/Kconfig |   27 +- >  drivers/scsi/Makefile|2 +- >  

[PATCH 1/3] cxlflash: Fix to drain operations from previous reset

From: "Manoj N. Kumar" While running 'sg_reset -H' in a loop with a user-space application active, hit the following exception: cpu 0x2: Vector: 300 (Data Access) pc: : afu_attach+0x50/0x240 [cxlflash] lr: : cxlflash_afu_recover+0x3dc/0x7d0 [cxlflash] pid

[PATCH 3/3] cxlflash: Shutdown notify support for CXL Flash cards

Some CXL Flash cards need notification of device shutdown in order to flush pending I/Os. A PCI notification hook for shutdown has been added where the driver notifies the card and returns. When the device is removed in the PCI remove path, notification code will wait for shutdown processing to

[PATCH 2/3] cxlflash: Add device dependent flags

Device dependent flags are needed to support functions that are specific to a particular device. One such case is - some CXL Flash cards need to be notified of device shutdown. For other CXL devices, this feature does not prove to be useful yet. Such distinct features need to be identified in the

[PATCH 0/3] cxlflash: Shutdown notification and reset patch

This patch set contains support to notify CXL Flash devices of an impending shutdown and a fix to drain operations prior to a reset. This series is intended for 4.8 and is bisectable. Manoj N. Kumar (1): cxlflash: Fix to drain operations from previous reset Uma Krishnan (2): cxlflash: Add

Re: [PATCH 0/1] cxlflash: Fix in EEH recovery

Please ignore this email. It was sent in error. Sorry for the confusion. On 6/15/2016 6:46 PM, Uma Krishnan wrote: This patch addresses a deadlock issue seen during EEH recovery and is intended for 4.7. Manoj N. Kumar (1): cxlflash: Fix to resolve dead-lock during EEH recovery

Re: [PATCH v4] ibmvscsis: Initial commit of IBM VSCSI Tgt Driver

On 6/14/16, 9:57 AM, "Christoph Hellwig" wrote: >On Tue, Jun 14, 2016 at 10:46:09AM +0200, Bart Van Assche wrote: >> All what's needed is something like the (untested) patch below. As one >> can see no new function pointers have been added to target_core_fabric_ops. >> All

[PATCH 0/1] cxlflash: Fix in EEH recovery

This patch addresses a deadlock issue seen during EEH recovery and is intended for 4.7. Manoj N. Kumar (1): cxlflash: Fix to resolve dead-lock during EEH recovery drivers/scsi/cxlflash/superpipe.c | 15 +++ 1 file changed, 15 insertions(+) -- 2.1.0 -- To unsubscribe from this

Re: [PATCH v4] ibmvscsis: Initial commit of IBM VSCSI Tgt Driver

On 6/14/16, 3:46 AM, "Bart Van Assche" wrote: >On 06/14/2016 08:35 AM, Nicholas A. Bellinger wrote: >> On Fri, 2016-06-10 at 12:05 -0700, Bart Van Assche wrote: >>> On 06/09/2016 02:26 PM, Bryant G. Ly wrote: +/** + * ibmvscsis_modify_std_inquiry() - Modify

Re: [PATCH v4] ibmvscsis: Initial commit of IBM VSCSI Tgt Driver

On 6/14/16, 3:09 AM, "Bart Van Assche" wrote: >On 06/09/2016 11:26 PM, Bryant G. Ly wrote: >> This driver is a pick up of the old IBM VIO scsi Target Driver >> that was started by Nick and Fujita 2-4 years ago. >> http://comments.gmane.org/gmane.linux.scsi/90119 >

Re: BLKZEROOUT not zeroing md dev on VMDK

On Wed, Jun 15, 2016 at 06:17:37PM +, Arvind Kumar wrote: > It is possibly some race. We saw a WRITE SAME related issue in past > for which Petr sent out a patch but looks like the patch didn't make > it. :( > > https://groups.google.com/forum/#!topic/linux.kernel/1WGDSlyY0y0 Indeed - the

[PATCH 2/2] scsi: wd7000: print sector number as 64-bit

Enabling format checking in dprintk() shows that wd7000_biosparam uses an incorrect format string for sector_t: drivers/scsi/wd7000.c: In function 'wd7000_biosparam': drivers/scsi/wd7000.c:1594:21: error: format '%d' expects argument of type 'int', but argument 3 has type 'sector_t {aka long

[PATCH 1/2] scsi: lpfc: avoid harmless comparison warning

When building with -Wextra, we get a lot of warnings for the lpfc driver concerning expressions that are always true, starting with: drivers/scsi/lpfc/lpfc_attr.c: In function 'lpfc_enable_npiv_init': drivers/scsi/lpfc/lpfc_attr.c:2786:77: error: comparison of unsigned expression >= 0 is always

Re: [PATCH] ses: Fix racy cleanup of /sys in remove_dev()

On Thursday 06/02 at 15:50 -0700, Calvin Owens wrote: > On 05/13/2016 01:28 PM, Calvin Owens wrote: > > Currently we free the resources backing the enclosure device before we > > call device_unregister(). This is racy: during rmmod of low-level SCSI > > drivers that hook into enclosure, we end up

[PATCH] MAINTAINERS: Update email address for AACRAID

Update the email address for AACRAID from Adaptec to Microsemi Signed-off-by: Dave Carroll --- MAINTAINERS | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/MAINTAINERS b/MAINTAINERS index 2ebe195..a327ba2 100644 --- a/MAINTAINERS +++ b/MAINTAINERS

BUSINESS VORSCHLAG

BUSINESS VORSCHLAG Ich vertrete eine Investition Interesse von Dubai für die wir Ihre Teilnahme als Vertreter Übersee suchen. Die Antwort auf e-Mail unten, wenn interessiert. E-Mail: philipber...@gmail.com -- To unsubscribe from this list: send the line "unsubscribe linux-scsi" in the body of a

Re: BLKZEROOUT not zeroing md dev on VMDK

It is possibly some race. We saw a WRITE SAME related issue in past for which Petr sent out a patch but looks like the patch didn't make it. :( https://groups.google.com/forum/#!topic/linux.kernel/1WGDSlyY0y0 Thanks! Arvind From: Sitsofe Wheeler

Re: block: don't check request size in blk_cloned_rq_check_limits()

On 06/15/2016 05:33 AM, Hannes Reinecke wrote: > On 06/15/2016 12:03 PM, Jens Axboe wrote: >> On 06/15/2016 08:33 AM, Hannes Reinecke wrote: >>> And as I've mentioned before: what is the purpose of this check? >>> >>> 'max_sectors' and 'max_hw_sectors' are checked during request assembly, >>> and

[PATCH] lpfc: Fix possible NULL pointer dereference

Check for the existance of pciob->vport before accessing it. Signed-off-by: Johannes Thumshirn --- drivers/scsi/lpfc/lpfc_sli.c | 13 - 1 file changed, 4 insertions(+), 9 deletions(-) diff --git a/drivers/scsi/lpfc/lpfc_sli.c b/drivers/scsi/lpfc/lpfc_sli.c index

[Bug 120371] New: UBSAN splat in drivers/scsi/scsi_devinfo.c:458:21

https://bugzilla.kernel.org/show_bug.cgi?id=120371 Bug ID: 120371 Summary: UBSAN splat in drivers/scsi/scsi_devinfo.c:458:21 Product: IO/Storage Version: 2.5 Kernel Version: 4.7.0-rc3 Hardware: All OS: Linux

[PATCH] Fix an sd reregistration race, v5

Avoid that the sd driver registers a BDI device with a name that is still in use. This patch avoids that the following warning is triggered sporadically: WARNING: CPU: 7 PID: 203 at fs/sysfs/dir.c:31 sysfs_warn_dup+0x68/0x80() sysfs: cannot create duplicate filename '/devices/virtual/bdi/8:32'

Re: [PATCH] Fix a bdi reregistration race, v3

On 06/04/2016 01:25 AM, Bart Van Assche wrote: Earlier today I discovered a subtle bug in v3 of this patch. It would be appreciated if you could give v4 a try. The only substantial difference between v3 and v4 is that a "if (dev->class != _class)" test has been added. (again replying to my own

Re: block: don't check request size in blk_cloned_rq_check_limits()

On 06/15/2016 12:03 PM, Jens Axboe wrote: > On 06/15/2016 08:33 AM, Hannes Reinecke wrote: >> And as I've mentioned before: what is the purpose of this check? >> >> 'max_sectors' and 'max_hw_sectors' are checked during request assembly, >> and those limits are not changed even after calling >>

Re: block: don't check request size in blk_cloned_rq_check_limits()

On 06/15/2016 08:33 AM, Hannes Reinecke wrote: And as I've mentioned before: what is the purpose of this check? 'max_sectors' and 'max_hw_sectors' are checked during request assembly, and those limits are not changed even after calling blk_recalc_rq_segments(). And if we go over any

Re: [PATCH] 53c700: fix BUG on untagged commands

On 06/14/2016 05:05 PM, Christoph Hellwig wrote: > Looks fine: > > Acked-by: Christoph Hellwig > > But it should really go together with something like this: > > --- > From e54d1462ae244db3189a8b69018bc5f3e3d3b468 Mon Sep 17 00:00:00 2001 > From: Christoph Hellwig >

Re: block: don't check request size in blk_cloned_rq_check_limits()

On 06/15/2016 03:39 AM, Martin K. Petersen wrote: >> "Hannes" == Hannes Reinecke writes: > > Hannes> Well, the primary issue is that 'blk_cloned_rq_check_limits()' > Hannes> doesn't check for BLOCK_PC, > > Yes it does. It calls blk_rq_get_max_sectors() which has an explicit >