Re: [PATCH] target: Fix REPORT TARGET PORT GROUPS handling with small allocation length

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

 



On Wed, Oct 19, 2011 at 1:45 PM, Nicholas A. Bellinger
<nab@xxxxxxxxxxxxxxx> wrote:
> It's still a bug if the response length fills beyond the allocation
> length, regardless of if we have a whole page or not for backing memory
> in v3.1 code.

I'm not following you.  With 3.1 code, suppose an initiator sends an allocation
length of 4 ("just give me the response length") and our actual response ends
up being 24 bytes.  The 3.1 code would fill in the full 24 byte response, but
nothing bad would happen because we allocated a whole page anyway.  (We'd
only send back up to the command's allocation length as I understand the code,
so the right response would go on the wire)

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