From: Fabio Checconi <fchecconi@gmail.com>
To: Jens Axboe <jens.axboe@oracle.com>
Cc: Nikanth Karthikesan <knikanth@suse.de>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Exiting queue and task might race to free cic
Date: Wed, 19 Nov 2008 16:02:26 +0100 [thread overview]
Message-ID: <20081119150226.GD20915@gandalf.sssup.it> (raw)
In-Reply-To: <20081119141531.GG26308@kernel.dk>
> From: Jens Axboe <jens.axboe@oracle.com>
> Date: Wed, Nov 19, 2008 03:15:31PM +0100
>
> On Wed, Nov 19 2008, Nikanth Karthikesan wrote:
> > Hi Jens
> >
> > Looking at the bug reported here
> > http://thread.gmane.org/gmane.linux.kernel/722539
> > it looks like an exiting queue can race with an exiting task.
> >
> > When a queue exits the queue lock is taken and cfq_exit_queue() would free all
> > the cic's associated with the queue.
> >
> > But when a task exits, cfq_exit_io_context() gets cic one by one and then
> > locks the associated queue to call __cfq_exit_single_io_context. It looks like
> > between getting a cic from the ioc and locking the queue, the queue might have
> > exited on another cpu. Isn't this possible?
> >
> > If possible, either verifying whether cic->key is still not null or q->flags
> > does not have QUEUE_FLAG_DEAD set would fix this.
> >
> > Thanks
> > Nikanth Karthikesan
> >
> > Signed-off-by: Nikanth Karthikesan <knikanth@suse.de>
> >
> > ---
> > diff --git a/block/cfq-iosched.c b/block/cfq-iosched.c
> > index 6a062ee..b9b627a 100644
> > --- a/block/cfq-iosched.c
> > +++ b/block/cfq-iosched.c
> > @@ -1318,7 +1318,12 @@ static void cfq_exit_single_io_context(struct
> > io_context *ioc,
> > unsigned long flags;
> >
> > spin_lock_irqsave(q->queue_lock, flags);
> > - __cfq_exit_single_io_context(cfqd, cic);
> > + /*
> > + * cic might have been already exited when an exiting task
> > + * races with an exiting queue.
> > + */
> > + if (likely(cic->key))
> > + __cfq_exit_single_io_context(cfqd, cic);
> > spin_unlock_irqrestore(q->queue_lock, flags);
> > }
> > }
>
> Not sure this is enough, we probably need to copy the key to ensure that
> we get a fresh value. How does this look?
>
> Did you actually trigger this, or is it just from code inspection?
>
> diff --git a/block/cfq-iosched.c b/block/cfq-iosched.c
> index 6a062ee..560cd1c 100644
> --- a/block/cfq-iosched.c
> +++ b/block/cfq-iosched.c
> @@ -1318,7 +1318,14 @@ static void cfq_exit_single_io_context(struct io_context *ioc,
> unsigned long flags;
>
> spin_lock_irqsave(q->queue_lock, flags);
> - __cfq_exit_single_io_context(cfqd, cic);
> +
> + /*
> + * Ensure we get a fresh copy of the ->key to prevent
> + * race between exiting task and queue
> + */
> + smp_read_barrier_depends();
> + if (cic->key)
> + __cfq_exit_single_io_context(cfqd, cic);
> spin_unlock_irqrestore(q->queue_lock, flags);
> }
> }
>
I've seen once the oops reported (the BUG() now @ line 1247), but I've
never been able to reproduce it afterwards. I think that there still
is a window open for a race here:
1314 struct cfq_data *cfqd = cic->key;
1315
=====> here cfq_exit_queue() can free cfqd and assign cic->key = NULL,
and accessing cfqd->queue is not safe. [ If I'm not wrong :) ]
1316 if (cfqd) {
1317 struct request_queue *q = cfqd->queue;
next prev parent reply other threads:[~2008-11-19 14:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-19 9:57 [PATCH] Exiting queue and task might race to free cic Nikanth Karthikesan
2008-11-19 14:15 ` Jens Axboe
2008-11-19 15:02 ` Fabio Checconi [this message]
2008-11-20 4:57 ` Nikanth Karthikesan
2008-11-22 7:17 ` Nikanth Karthikesan
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=20081119150226.GD20915@gandalf.sssup.it \
--to=fchecconi@gmail.com \
--cc=jens.axboe@oracle.com \
--cc=knikanth@suse.de \
--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