From: Bart Van Assche <bvanassche@acm.org>
To: Mike Snitzer <snitzer@redhat.com>
Cc: dm-devel@redhat.com, linux-scsi@vger.kernel.org,
"Martin K . Petersen" <martin.petersen@oracle.com>
Subject: Re: dm-mpath: Fix setup_scsi_dh()
Date: Mon, 17 Sep 2018 07:51:50 -0700 [thread overview]
Message-ID: <31642b58-a1de-a162-e9db-46e5a589e2b9@acm.org> (raw)
In-Reply-To: <20180917142046.GA52842@redhat.com>
On 9/17/18 7:20 AM, Mike Snitzer wrote:
>> - Avoid that m->hw_handler_name becomes a dangling pointer if the
>> RETAIN_ATTACHED_HW_HANDLER flag is set and scsi_dh_attach() returns
>> -EBUSY.
>
> What is the concern about a dangling pointer? How does that manifest?
> Stale scsi_dh name stored in hw_handler_name? Pretty sure it gets freed
> and reassigned as needed (at the start of setup_scsi_dh).
Hello Mike,
Thanks for having taken a look. Before commit e8f74a0f0011, if both
MPATHF_RETAIN_ATTACHED_HW_HANDLER and m->hw_handler_name are set before
setup_scsi_dh() is called and if scsi_dh_attach() returns -EBUSY,
scsi_dh_attached_handler_name() was called twice and allocated memory
twice for the handler name. Since commit e8f74a0f0011, in that scenario,
the following code related to the handler name is executed:
kfree(m->hw_handler_name);
m->hw_handler_name = attached_handler_name;
[ scsi_dh_attach() returns -EBUSY ]
kfree(m->hw_handler_name);
m->hw_handler_name = attached_handler_name;
I think this sequence makes m->hw_handler_name a dangling pointer.
> diff --git a/drivers/md/dm-mpath.c b/drivers/md/dm-mpath.c
> index d94ba6f72ff5..688ac9e719a7 100644
> --- a/drivers/md/dm-mpath.c
> +++ b/drivers/md/dm-mpath.c
> @@ -806,14 +806,14 @@ static int parse_path_selector(struct dm_arg_set *as, struct priority_group *pg,
> }
>
> static int setup_scsi_dh(struct block_device *bdev, struct multipath *m,
> - const char *attached_handler_name, char **error)
> + char **attached_handler_name, char **error)
> {
> struct request_queue *q = bdev_get_queue(bdev);
> int r;
>
> if (test_bit(MPATHF_RETAIN_ATTACHED_HW_HANDLER, &m->flags)) {
> retain:
> - if (attached_handler_name) {
> + if (*attached_handler_name) {
> /*
> * Clear any hw_handler_params associated with a
> * handler that isn't already attached.
> @@ -830,7 +830,8 @@ static int setup_scsi_dh(struct block_device *bdev, struct multipath *m,
> * handler instead of the original table passed in.
> */
> kfree(m->hw_handler_name);
> - m->hw_handler_name = attached_handler_name;
> + m->hw_handler_name = *attached_handler_name;
> + *attached_handler_name = NULL;
> }
> }
>
> @@ -867,7 +868,7 @@ static struct pgpath *parse_path(struct dm_arg_set *as, struct path_selector *ps
> struct pgpath *p;
> struct multipath *m = ti->private;
> struct request_queue *q;
> - const char *attached_handler_name;
> + char *attached_handler_name = NULL;
>
> /* we need at least a path arg */
> if (as->argc < 1) {
> @@ -890,7 +891,7 @@ static struct pgpath *parse_path(struct dm_arg_set *as, struct path_selector *ps
> attached_handler_name = scsi_dh_attached_handler_name(q, GFP_KERNEL);
> if (attached_handler_name || m->hw_handler_name) {
> INIT_DELAYED_WORK(&p->activate_path, activate_path_work);
> - r = setup_scsi_dh(p->path.dev->bdev, m, attached_handler_name, &ti->error);
> + r = setup_scsi_dh(p->path.dev->bdev, m, &attached_handler_name, &ti->error);
> if (r) {
> dm_put_device(ti, p->path.dev);
> goto bad;
> @@ -905,6 +906,8 @@ static struct pgpath *parse_path(struct dm_arg_set *as, struct path_selector *ps
>
> return p;
> bad:
> + if (attached_handler_name)
> + kfree(attached_handler_name);
> free_pgpath(p);
> return ERR_PTR(r);
> }
Except that the if (attached_handler_name) should be removed from before
the kfree() call, the above looks good to me. But since we can avoid
changing the type of attached_handler_name from char * into char ** by
moving the kfree() call into setup_scsi_dh(), I prefer to avoid to make
that change.
Thanks,
Bart.
next prev parent reply other threads:[~2018-09-17 14:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-17 3:33 [PATCH] dm-mpath: Fix setup_scsi_dh() Bart Van Assche
2018-09-17 14:20 ` Mike Snitzer
2018-09-17 14:51 ` Bart Van Assche [this message]
2018-09-17 15:11 ` Mike Snitzer
2018-09-17 15:34 ` Bart Van Assche
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=31642b58-a1de-a162-e9db-46e5a589e2b9@acm.org \
--to=bvanassche@acm.org \
--cc=dm-devel@redhat.com \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=snitzer@redhat.com \
/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