On Mon, 26 Jul 2010 12:27:43 +0400, Kulikov Vasiliy wrote: > worker_loop() uses schedule_timeout() without setting state to > STATE_(UN)INTERRUPTIBLE. As it is called in cycle without checking of > pending signals, use schedule_timeout_uninterruptible(). > > Signed-off-by: Kulikov Vasiliy<segooon@xxxxxxxxx> > --- > fs/btrfs/async-thread.c | 2 +- > 1 files changed, 1 insertions(+), 1 deletions(-) > > diff --git a/fs/btrfs/async-thread.c b/fs/btrfs/async-thread.c > index 7ec1409..54eb070 100644 > --- a/fs/btrfs/async-thread.c > +++ b/fs/btrfs/async-thread.c > @@ -362,7 +362,7 @@ again: > * worker->working is still 1, so nobody > * is going to try and wake us up > */ > - schedule_timeout(1); > + schedule_timeout_uninterruptible(1); I found there is the same problem in the other place of the btrfs, could you fix them? Thanks! Miao > smp_mb(); > if (!list_empty(&worker->pending) || > !list_empty(&worker->prio_pending)) -- To unsubscribe from this list: send the line "unsubscribe kernel-janitors" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
