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
--
[email protected]
On Wed, 2 Jul 2008, Alasdair G Kergon wrote:
> 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) {
Thanks for the suggestions.
In looking at it a little bit, it seems that ps.type is initialized in the
function stored in the ctr field of the target_type structure and this
function is called in the function stored in the message field of the same
structure. The function in the message structure seems to be only called
from the function target_message in dm-ioctl.c, but I don't see the
relation to an invocation of the ctr field. Is that guaranteed to be
invoked earlier?
julia
On Wed, Jul 02, 2008 at 01:51:41PM +0200, Julia Lawall wrote:
> In looking at it a little bit, it seems that ps.type is initialized in the
> function stored in the ctr field of the target_type structure and this
> function is called in the function stored in the message field of the same
> structure. The function in the message structure seems to be only called
> from the function target_message in dm-ioctl.c, but I don't see the
> relation to an invocation of the ctr field. Is that guaranteed to be
> invoked earlier?
ctr is short for constructor (perhaps we should rename these functions one day)
and it has to run first to set up the data structures which a subsequent
target_message may reference.
Alasdair
--
[email protected]