From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Michael Guntsche <mike@it-loops.com>
Cc: linux-kernel@vger.kernel.org, alan@linux.intel.com
Subject: Re: BUG: scheduling while atomic
Date: Sat, 27 Jun 2009 14:06:43 +0100 [thread overview]
Message-ID: <20090627140643.7140f6a9@lxorguk.ukuu.org.uk> (raw)
In-Reply-To: <23AED400-6DA5-462F-94F0-BEE34AC08A7A@it-loops.com>
On Sat, 27 Jun 2009 13:10:23 +0200
Michael Guntsche <mike@it-loops.com> wrote:
> Hello list, Alan,
>
> I got the same error with pptpgw as Sergey after switching form
> 2.6.30 to recent git (rc1).
Yes - I've no idea what is going on with the pptpgw traces at the moment.
The path is
pptpgw reads from the tty side (it uses a pty/tty pair and runs
ppp over it)
This calls the ldisc n_tty_read
We copy some data and this makes room in the buffers
ww call check_unthrottle (with no spinlocks held)
This decides that thre is now room to ask the other end
to send more
which calls tty_unthrottle (which takes only a mutex)
which calls pty_unthrottle
which wakes the other side of the pty/tty pair for writing
this calls the ppp ldisc wakeup handler for the other side
which blows up somewhere around the tasklet code for no reason I
can make sense of yet
and all of this should be (and seems to be) getting called with sleeping
allowed and no spinlocks taken in error.
You could stuff calls to might_sleep() in pty_unthrottle and
check_unthrottle and see which ones are triggered if any.
next prev parent reply other threads:[~2009-06-27 13:05 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-27 11:10 Michael Guntsche
2009-06-27 13:06 ` Alan Cox [this message]
2009-06-27 16:07 ` Michael Guntsche
2009-07-06 7:43 ` Herbert Xu
2009-07-06 8:31 ` Herbert Xu
2009-07-06 15:28 ` Michael Guntsche
2009-07-06 15:32 ` Alan Cox
2009-07-06 17:17 ` Alan Cox
2009-07-06 18:07 ` Michael Guntsche
2009-07-06 18:18 ` Alan Cox
2009-07-06 18:37 ` Michael Guntsche
2009-07-06 10:00 ` Alan Cox
-- strict thread matches above, loose matches on Subject: below --
2012-02-13 8:08 Florian Tobias Schandinat
2010-08-27 7:59 Sergey Senozhatsky
2010-08-27 19:02 ` Rafael J. Wysocki
2010-08-28 6:42 ` Pavel Machek
2010-08-30 7:29 ` Sergey Senozhatsky
2010-08-30 10:04 ` Sergey Senozhatsky
2009-06-19 18:15 Sergey Senozhatsky
2009-06-20 17:43 ` Rabin Vincent
2009-06-20 18:54 ` Sergey Senozhatsky
2009-06-22 9:04 ` Alan Cox
2009-06-22 9:57 ` Alan Cox
2009-06-22 11:33 ` Sergey Senozhatsky
2009-06-22 12:36 ` Alan Cox
2009-06-22 13:59 ` Sergey Senozhatsky
2009-07-06 7:55 ` Herbert Xu
2006-12-08 15:47 Christian
2006-06-02 9:39 fonseka
2006-06-02 12:37 ` Roger Luethi
2006-06-02 14:07 ` fonseka
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=20090627140643.7140f6a9@lxorguk.ukuu.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=alan@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mike@it-loops.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
all inboxes | Powered by JetHome®