From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Jesper Juhl <jesper.juhl@gmail.com>
Cc: linux-scsi <linux-scsi@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Fix problem with size of allocation in libsas
Date: Sun, 11 Nov 2007 18:00:03 -0600 [thread overview]
Message-ID: <1194825603.3445.21.camel@localhost.localdomain> (raw)
In-Reply-To: <200711120024.54773.jesper.juhl@gmail.com>
On Mon, 2007-11-12 at 00:24 +0100, Jesper Juhl wrote:
> From: Jesper Juhl <jesper.juhl@gmail.com>
>
> in sas_get_phy_change_count(), the line
> disc_resp = alloc_smp_resp(DISCOVER_RESP_SIZE);
> will allocate 56 bytes due to this define:
> #define DISCOVER_RESP_SIZE 56
> But, the struct is actually 60 bytes in size.
>
> So change the define to be
> #define DISCOVER_RESP_SIZE sizeof(struct smp_resp)
> so we always get the correct size even when people
> fiddle with the structure.
>
> This change also fixes the same problem in
> sas_get_phy_attached_sas_addr()
>
> (Found by the Coverity checker. Compile tested only)
Well, your fix is definitely wrong.
Could you explain the problem a little more? The discover response SMP
frame is 56 bytes as mandated by the standard. I don't see anywhere in
the code where we're actually using a value beyond the 56th byte ...
where is the problem use?
James
next prev parent reply other threads:[~2007-11-12 0:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-11 23:24 [PATCH] Fix problem with size of allocation in libsas Jesper Juhl
2007-11-12 0:00 ` James Bottomley [this message]
2007-11-12 0:13 ` Jesper Juhl
2007-11-12 0:37 ` James Bottomley
2007-11-12 0:48 ` Jesper Juhl
2007-11-12 0:33 ` Douglas Gilbert
2007-11-12 0:45 ` James Bottomley
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1194825603.3445.21.camel@localhost.localdomain \
--to=james.bottomley@hansenpartnership.com \
--cc=jesper.juhl@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox