linux-kernel - console problem?, close(2) hangs /sbin/init

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Date:	Sat, 22 Jan 2011 14:45:09 -0700
From:	John Linn <John.Linn@...inx.com>
To:	<linux-kernel@...r.kernel.org>
Subject: console problem?, close(2) hangs /sbin/init

I have a kernel that runs fine with a busybox root file system using
inittab.  When I move to a non-busybox init (sysvinit), I see init
hanging when doing a close of standard error very early when it starts.
I have debugged it with GDB but not found the source of the hang as it's
in the kernel it appears.

To debug this, I use init=/bin/sh on the kernel command line, then exec
init to start it. The same root file system works on another board with
a different kernel.  I have also noticed that building init with
INITDEBUG on so that it forks for debugging makes it work fine. This
seems to indicate the device nodes are all fine to me.

It seems related to PID 1 and the console device.

Adding debug to the kernel in sys_close() shows it hanging in
filp_close() and I'm still digging more (maybe locking issue). The
console is a serial device with a newer driver which I suspected to be
the issue, but can't see anything wrong.

Any hints or similar problems seen would be much appreciated.
Thanks,
John

This email and any attachments are intended for the sole use of the named recipient(s) and contain(s) confidential information that may be proprietary, privileged or copyrighted under applicable law. If you are not the intended recipient, do not read, copy, or forward this email message or any attachments. Delete this email message and any attachments immediately.

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/