Re: [PATCH] target: Only check max_sectors for passthrough backend I/O

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

 



On Tue, May 08, 2012 at 09:54:28PM -0700, Nicholas A. Bellinger wrote:
> So the issue of concern here is with existing userspace code that is
> using this value to explicitly set max_sectors at target restart time
> based upon the original blkdev queue limits (or smaller) with IBLOCK,
> and can possibly end up rejecting incoming I/O if the max_sectors is set
> too small.

Oh, userspace messes with these values?  When I tested it using
lio-tools it didn't but I guess I didn't use the complicated enough
userspace to do something that silly :)

Your new patch looks fine.

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


[Index of Archives]     [Linux SCSI]     [Kernel Newbies]     [Linux SCSI Target Infrastructure]     [Share Photos]     [IDE]     [Security]     [Git]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux ATA RAID]     [Linux IIO]     [Device Mapper]

  Powered by Linux