Re: [PATCH 0/5] UNMAP handling fixes

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

 



On Mon, 2012-07-16 at 15:34 -0700, Roland Dreier wrote:
> From: Roland Dreier <roland@xxxxxxxxxxxxxxx>
> 
> Hi Nic,
> 
> A short series that cleans up handling of UNMAP commands.  The main
> thing is not crashing horribly if an initiator sends us a 0-length
> descriptor length...
> 
> Roland Dreier (5):
>   target: Add generation of LOGICAL BLOCK ADDRESS OUT OF RANGE
>   target: Add range checking to UNMAP emulation
>   target: Fix reading of data length fields for UNMAP commands
>   target: Fix possible integer underflow in UNMAP emulation
>   target: Check number of unmap descriptors against our limit
> 
>  drivers/target/target_core_iblock.c    |   43 ++++++++++++++++++++++----------
>  drivers/target/target_core_transport.c |   10 ++++++++
>  include/target/target_core_base.h      |    1 +
>  3 files changed, 41 insertions(+), 13 deletions(-)
> 

Ugh, I thought we had squashed the majority of UNMAP bugs, but
apparently not..  Thanks alot for getting these addressed

Applied to for-next via the upcoming for-3.6 PULL, but I'm thinking all
five look like stable kernel patch candidates for-3.5 as well.

Thanks again Roland!

--nab

--
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