From: scameron@beardog.cce.hp.com
To: Julia Lawall <Julia.Lawall@lip6.fr>
Cc: linux-kernel@vger.kernel.org, axboe@kernel.dk
Subject: Re: [PATCH 7/10] cciss: use safer test on the result of find_first_zero_bit
Date: Wed, 4 Jun 2014 09:51:35 -0500 [thread overview]
Message-ID: <20140604145135.GC6970@beardog.cce.hp.com> (raw)
> Find_first_zero_bit considers BITS_PER_LONG bits at a time, and thus may
> return a larger number than the maximum position argument if that position
> is not a multiple of BITS_PER_LONG.
>
> The semantic match that finds this problem is as follows:
> (http://coccinelle.lip6.fr/)
>
> // <smpl>
> @@
> expression e1,e2,e3;
> statement S1,S2;
> @@
>
> e1 = find_first_zero_bit(e2,e3)
> ...
> if (e1
> - ==
> + >=
> e3)
> S1 else S2
> // </smpl>
>
> Signed-off-by: Julia Lawall <Julia.Lawall@lip6.fr>
>
> ---
> drivers/block/cciss.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff -u -p a/drivers/block/cciss.c b/drivers/block/cciss.c
> --- a/drivers/block/cciss.c
> +++ b/drivers/block/cciss.c
> @@ -980,7 +980,7 @@ static CommandList_struct *cmd_alloc(ctl
>
> do {
> i = find_first_zero_bit(h->cmd_pool_bits, h->nr_cmds);
> - if (i == h->nr_cmds)
> + if (i >= h->nr_cmds)
> return NULL;
> } while (test_and_set_bit(i, h->cmd_pool_bits) != 0);
> c = h->cmd_pool + i;
Thanks. Ack.
You can add
Reviewed-by: Stephen M. Cameron <scameron@beardog.cce.hp.com>
to this patch if you want.
You might consider adding "Cc: stable@vger.kernel.org" into the
sign-off area as well.
-- steve
next reply other threads:[~2014-06-04 14:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-04 14:51 scameron [this message]
2014-06-04 15:10 ` [PATCH 7/10] cciss: use safer test on the result of find_first_zero_bit Julia Lawall
2014-06-04 16:55 ` Jens Axboe
2014-06-04 16:59 ` Julia Lawall
2014-06-04 17:02 ` Jens Axboe
-- strict thread matches above, loose matches on Subject: below --
2014-06-04 9:07 [PATCH 0/10] " Julia Lawall
2014-06-04 9:07 ` [PATCH 7/10] cciss: " Julia Lawall
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=20140604145135.GC6970@beardog.cce.hp.com \
--to=scameron@beardog.cce.hp.com \
--cc=Julia.Lawall@lip6.fr \
--cc=axboe@kernel.dk \
--cc=linux-kernel@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