From: Kirill Korotaev <dev@sw.ru>
To: William Lee Irwin III <wli@holomorphy.com>,
torvalds@osdl.org, dtor_core@ameritech.net,
linux-kernel@vger.kernel.org
Subject: Re: INIT hangs with tonight BK pull (2.6.9-rc1+)
Date: Fri, 03 Sep 2004 12:09:10 +0400 [thread overview]
Message-ID: <413826A6.4000503@sw.ru> (raw)
In-Reply-To: <20040903073230.GM3106@holomorphy.com>
>>After doing BK pull last night INIT gets stuck in do_tty_hangup after
>>executing rc.sysinit. Was booting fine with pull from 2 days ago...
>>Anyone else seeing this?
>>I suspect pidhash patch because it touched tty_io.c, but I have not tried
>>reverting it as it is getting too late here... So I apologize in advance
>>if I am pointing finger at the innocent ;)
>
>
> Well, I was excited about blowing away 100B from each task but am now
> a bit concerned about the semantic impact of the refcounting part of it.
> It's unclear what pins an ID while a tty has a reference to it without
> the reference counting; Kirill, could you answer this?
stop.
tty doesn't hold reference to ID neither in my patch nor in the original
kernel.
tty only knows session ID and wants to traverse all tasks with such ID.
if task dies it calls detach_pid() and it won't be found in such a loop.
No reference counting is required.
The problem was in loop. Or more exactly my
do_each_task_pid()/while_each_task_pid() macros were incompatible with
continue statement inside. It was really foolish error. Like the most are...
Kirill
next prev parent reply other threads:[~2004-09-03 7:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-03 7:04 INIT hangs with tonight BK pull (2.6.9-rc1+) Dmitry Torokhov
2004-09-03 7:32 ` William Lee Irwin III
2004-09-03 8:09 ` Kirill Korotaev [this message]
2004-09-03 8:06 ` William Lee Irwin III
2004-09-03 8:00 ` Kirill Korotaev
2004-09-04 6:06 ` Dmitry Torokhov
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=413826A6.4000503@sw.ru \
--to=dev@sw.ru \
--cc=dtor_core@ameritech.net \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.org \
--cc=wli@holomorphy.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