From: Alasdair G Kergon <agk@redhat.com>
To: device-mapper development <dm-devel@redhat.com>
Cc: linux-kernel@vger.kernel.org, kernel-janitors@vger.kernel.org
Subject: Re: [dm-devel] [PATCH 2/6] drivers/md: remove null pointer dereference
Date: Wed, 2 Jul 2008 11:54:34 +0100 [thread overview]
Message-ID: <20080702105434.GF22522@agk.fab.redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0805121537100.3694@ask.diku.dk>
On Mon, May 12, 2008 at 03:37:31PM +0200, Julia Lawall wrote:
> If pgpath->pg->ps.type is NULL, it is not possible to access its name
> field. So I have simply modified the error message to drop the printing of
> the name field.
>
> This problem was found using the following semantic match
> (http://www.emn.fr/x-info/coccinelle/)
> --- a/drivers/md/dm-mpath.c 2008-04-16 13:27:57.000000000 +0200
> +++ b/drivers/md/dm-mpath.c 2008-05-12 09:19:35.000000000 +0200
> @@ -884,8 +884,7 @@ static int reinstate_path(struct pgpath
> goto out;
>
> if (!pgpath->pg->ps.type) {
> - DMWARN("Reinstate path not supported by path selector %s",
> - pgpath->pg->ps.type->name);
> + DMWARN("Reinstate path not supported by path selector");
> r = -EINVAL;
> goto out;
> }
Thanks for reporting this.
A more-sophisticated checker might discover that the test can never fail
- see parse_path_selector() - and so the real problem here is that it is
the wrong test.
The next line is:
r = pgpath->pg->ps.type->reinstate_path(&pgpath->pg->ps, &pgpath->path);
and the error message makes it clear that the intent was to ensure that
the reinstate_path method exists before attempting to use it.
IOW
if (!pgpath->pg->ps.type->reinstate_path) {
Alasdair
--
agk@redhat.com
next prev parent reply other threads:[~2008-07-02 10:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-12 13:37 Julia Lawall
2008-07-02 10:54 ` Alasdair G Kergon [this message]
2008-07-02 11:51 ` [dm-devel] " Julia Lawall
2008-07-02 19:03 ` Alasdair G Kergon
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=20080702105434.GF22522@agk.fab.redhat.com \
--to=agk@redhat.com \
--cc=dm-devel@redhat.com \
--cc=kernel-janitors@vger.kernel.org \
--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
all inboxes | Powered by JetHome®