Re: Crash on WRITE SAME

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 




On Wed, 2 Jul 2014, Christoph Hellwig wrote:

> On Wed, Jul 02, 2014 at 02:05:14PM -0400, Mikulas Patocka wrote:
> > Hi Sagi
> > 
> > Your commit d77e65350f2d82dfa0557707d505711f5a43c8fd causes crash on SCSI 
> > WRITE SAME command (it can be triggered by issuing the BLKZEROOUT ioctl). 
> > The crash happens in iscsi_tcp_segment_done because sg_next returns NULL.
> 
> Martin already fixes this over a week ago, we're just waiting for James
> to send a pull request to Linus.
> 
> Get this fix from the core-for-3.16 branch of
> git.infradead.org/users/hch/scsi-queue.git for now.

I see.

And what about protection information for commands that transfer partial 
sectors? (for example, UMAP transfers 24 bytes). Should 
scsi_transfer_length return 24 or 32 in this case?

Mikulas
--
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html




[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [SCSI Target Devel]     [Linux SCSI Target Infrastructure]     [Kernel Newbies]     [IDE]     [Security]     [Git]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux ATA RAID]     [Linux IIO]     [Samba]     [Device Mapper]
  Powered by Linux