From: Alan Cox <alan@linux.intel.com>
To: Jin Dongming <jin.dongming@np.css.fujitsu.com>
Cc: LKLM <linux-kernel@vger.kernel.org>,
Greg Kroah-Hartman <gregkh@suse.de>,
Kenji Kaneshige <kaneshige.kenji@jp.fujitsu.com>,
Hidetoshi Seto <seto.hidetoshi@jp.fujitsu.com>
Subject: Re: [BUG? -next] login prompt of tty2~6 displayed slowly
Date: Fri, 18 Sep 2009 17:03:43 +0100 [thread overview]
Message-ID: <20090918170343.6fd4e733@linux.intel.com> (raw)
In-Reply-To: <4AB31B87.2040007@np.css.fujitsu.com>
> And I find out that the root cause of this problem is the following
> patch: commit 236cce0066f9c6a4856bc0404e541d3db3b0255e
> Titled "tty: make the kref destructor occur asynchronously"
Technically its a bug in mingetty but in practical terms its a
regression and the new behaviour isn't nice at all.
> When the tty is closed, the content of tty is not released
> immediately. And the flag of tty is set with TTY_CLOSING. So when the
> tty is reopened, the tty may not be released yet. Because the
> TTY_CLOSING in flag of tty is still valid. The kernel returns "-EIO"
> error. And the message "/sbin/mingetty[3062]: tty2: cannot open tty:
> Input/output error" is displayed at the user land.
See the previous discussions on how to fix this. I'm not sure if anyone
has addressed them yet but basically the shutdown and async destructor
need to be split apart so the device is deregistered synchronously and
then destroyed asynchronously
prev parent reply other threads:[~2009-09-18 16:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-18 5:32 [BUG? -next] login prompt of tty2~6 displayed slowly Jin Dongming
2009-09-18 16:03 ` Alan Cox [this message]
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=20090918170343.6fd4e733@linux.intel.com \
--to=alan@linux.intel.com \
--cc=gregkh@suse.de \
--cc=jin.dongming@np.css.fujitsu.com \
--cc=kaneshige.kenji@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=seto.hidetoshi@jp.fujitsu.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