From: "Serge E. Hallyn" <serue@us.ibm.com>
To: Andrew Morton <akpm@osdl.org>
Cc: "Serge E. Hallyn" <serue@us.ibm.com>,
hugh@veritas.com, torvalds@osdl.org,
linux-kernel@vger.kernel.org
Subject: Re: please revert kthread from loop.c
Date: Tue, 11 Jul 2006 22:26:47 -0500 [thread overview]
Message-ID: <20060712032647.GA24595@sergelap.austin.ibm.com> (raw)
In-Reply-To: <20060711171752.4993903a.akpm@osdl.org>
Quoting Andrew Morton (akpm@osdl.org):
> "Serge E. Hallyn" <serue@us.ibm.com> wrote:
> >
> > Convert loop.c from the deprecated kernel_thread to kthread.
> >
>
> I think you have a racelet here:
>
> > + }
> > spin_unlock_irq(&lo->lo_lock);
> >
> > - BUG_ON(!bio);
> > - loop_handle_bio(lo, bio);
> > -
> > - /*
> > - * upped both for pending work and tear-down, lo_pending
> > - * will hit zero then
> > - */
> > - if (unlikely(!pending))
> > - break;
> > + __set_current_state(TASK_INTERRUPTIBLE);
> > + schedule();
> > }
> >
> > - complete(&lo->lo_done);
> > return 0;
> > }
>
>
> : if (kthread_should_stop()) {
> : spin_unlock_irq(&lo->lo_lock);
> : break;
> : }
> : spin_unlock_irq(&lo->lo_lock);
> :
> : __set_current_state(TASK_INTERRUPTIBLE);
> : schedule();
> :
>
> If the wake_up_process() is delivered before the __set_current_state(),
> we'll miss the wakeup.
Makes sense, and the patched kernel passes the parallel tests.
Thanks for the patch.
> If so, this should plug it. The same race is not possible against the
> loop_set_fd() wakeup because the thread isn't running at that stage, yes?
Right, it's not yet running at loop_set_fd(). However what about
kthread_stop() called from loop_clr_fd()? Unfortunately fixing
that seems hairy. Need to think about it...
thanks,
-serge
next prev parent reply other threads:[~2006-07-12 3:27 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-26 18:39 Hugh Dickins
2006-06-27 5:46 ` Serge E. Hallyn
2006-06-28 18:41 ` Hugh Dickins
2006-06-28 19:08 ` Serge E. Hallyn
2006-07-11 19:49 ` Serge E. Hallyn
2006-07-12 0:17 ` Andrew Morton
2006-07-12 3:26 ` Serge E. Hallyn [this message]
2006-07-12 3:46 ` Andrew Morton
2006-07-12 14:31 ` Serge E. Hallyn
2006-07-12 23:02 ` Serge E. Hallyn
2006-07-13 9:38 ` Andrew Morton
2006-07-13 13:36 ` Serge E. Hallyn
2006-07-13 14:57 ` Andrew Morton
2006-07-20 17:00 ` Serge E. Hallyn
2006-07-12 15:13 ` Hugh Dickins
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=20060712032647.GA24595@sergelap.austin.ibm.com \
--to=serue@us.ibm.com \
--cc=akpm@osdl.org \
--cc=hugh@veritas.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.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®