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-prev] [thread-next>] [day] [month] [year] [list]
Date:	Sat, 22 Jan 2011 23:14:15 +0100 (CET)
From:	Jesper Juhl <jj@...osbits.net>
To:	John Linn <John.Linn@...inx.com>
cc:	linux-kernel@...r.kernel.org
Subject: Re: console problem?, close(2) hangs /sbin/init

On Sat, 22 Jan 2011, John Linn wrote:

> I have a kernel that runs fine 

What kernel exactely?

>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. 

What other kernel version exactely?

> 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
> 

-- 
Jesper Juhl <jj@...osbits.net>            http://www.chaosbits.net/
Don't top-post http://www.catb.org/~esr/jargon/html/T/top-post.html
Plain text mails only, please.

--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ