From: Russell King <rmk@arm.linux.org.uk>
To: Rik van Riel <riel@conectiva.com.br>
Cc: Andrew Morton <akpm@digeo.com>,
torvalds@transmeta.com, linux-kernel@vger.kernel.org,
tytso@thunk.org, rddunlap@osdl.org
Subject: Re: [PATCH][RESEND 3] disassociate_ctty SMP fix
Date: Wed, 5 Feb 2003 09:51:14 +0000 [thread overview]
Message-ID: <20030205095114.A25479@flint.arm.linux.org.uk> (raw)
In-Reply-To: <Pine.LNX.4.50L.0302042356580.32328-100000@imladris.surriel.com>; from riel@conectiva.com.br on Tue, Feb 04, 2003 at 11:58:52PM -0200
On Tue, Feb 04, 2003 at 11:58:52PM -0200, Rik van Riel wrote:
> I guess it's time to fix the caller of this function then,
> since something strange is going on here:
>
> http://bugme.osdl.org/show_bug.cgi?id=54
I don't think the tty is null there. It'll be a filp->private_data
being null.
>From the trace, my guess is that a file descriptor is being left
with a null filp->private_data, yet its on the file descriptor list
for the tty, and its fops is set to tty_fops.
I'll see if I can reproduce it here and work out what's going on.
However, note the following (and I think this is the crux of the problem):
release_dev is _supposed_ to run under the BKL. So how the fsck are we
getting into tty_do_hangup's BKL protected region while also being in
release_dev's BKL protected region? Is it the BKL which has broken?
--
Russell King (rmk@arm.linux.org.uk) The developer of ARM Linux
http://www.arm.linux.org.uk/personal/aboutme.html
next prev parent reply other threads:[~2003-02-05 9:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-05 0:36 [PATCH][RESEND 3] disassociate_ctty SMP fix Rik van Riel
2003-02-05 1:07 ` Rik van Riel
2003-02-05 1:51 ` Andrew Morton
2003-02-05 1:58 ` Rik van Riel
2003-02-05 9:51 ` Russell King [this message]
2003-02-05 14:51 ` Russell King
2003-02-05 16:49 ` Russell King
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=20030205095114.A25479@flint.arm.linux.org.uk \
--to=rmk@arm.linux.org.uk \
--cc=akpm@digeo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rddunlap@osdl.org \
--cc=riel@conectiva.com.br \
--cc=torvalds@transmeta.com \
--cc=tytso@thunk.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