mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Oleg Nesterov <oleg@tv-sign.ru>
To: Zilvinas Valinskas <zilvinas@wilibox.com>
Cc: Andrew Morton <akpm@linux-foundation.org>, linux-kernel@vger.kernel.org
Subject: Re: Kernel NFS lockd freezes notebook on shutdown (Linux 2.6.22-rc1 + CFS v12)
Date: Sat, 19 May 2007 00:28:05 +0400	[thread overview]
Message-ID: <20070518202805.GA298@tv-sign.ru> (raw)
In-Reply-To: <1179485230.3800.20.camel@zv.wilibox.com>

On 05/18, Zilvinas Valinskas wrote:
>
> On Thu, 2007-05-17 at 22:45 +0400, Oleg Nesterov wrote:
> >
> > However, I can't understand why cleanup_workqueue_thread() hangs anyway.
> > It shouldn't. Looks like rpciod/1 was preempted, and can't get CPU. According
> > to kernel-nfs-freeze.log it is TASK_RUNNING. Strange.
> >
> > It is very sad, because this code was supposed to be cleanuped anyway,
> > but if it is really buggy, it would be great to know why.
>
> Can this be related to :
>
> CONFIG_PREEMPT=y

Yes, but this preemption should be very unlikely, but it happens every time
for you, strange. lockd in turn spins with preemption enabled, but somehow
rpciod/1 can't make progress. system_state == SYSTEM_HALT, but this shouldn't
affect preempt_schedule_irq(). So I think there is something else.

> workqueue.objdump - without any patch.

So it hangs waiting for cwq->thread == NULL, as expected.

OK. I still can't see how this code could be wrong, but it is bad anyway and
should be changed. The 2nd patch was done more than a month ago, but was
delayed for some stupid reasons. I'll send it today.

Still, it is not clear to me what happens, and you have other crashes with
nfs stop/start

	http://marc.info/?l=linux-kernel&m=117939027602591
	http://marc.info/?l=linux-kernel&m=117939257630947

which probaly need some attention.

Thanks!

Oleg.


  reply	other threads:[~2007-05-18 20:28 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-16 18:00 Zilvinas Valinskas
2007-05-16 19:15 ` Andrew Morton
2007-05-16 22:55   ` Oleg Nesterov
2007-05-17  6:17     ` Zilvinas Valinskas
2007-05-17  8:21     ` Zilvinas Valinskas
2007-05-17  9:00       ` Zilvinas Valinskas
2007-05-17 18:45       ` Oleg Nesterov
2007-05-18 10:47         ` Zilvinas Valinskas
2007-05-18 20:28           ` Oleg Nesterov [this message]
2007-05-20 10:37             ` zilvinas
2007-05-20 17:01               ` J. Bruce Fields
2007-05-20 19:21               ` Oleg Nesterov
2007-05-18 12:17   ` Zilvinas Valinskas
2007-05-18 15:34     ` Andrew Morton

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=20070518202805.GA298@tv-sign.ru \
    --to=oleg@tv-sign.ru \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=zilvinas@wilibox.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

Powered by JetHome