linux-kernel - RE: kernel space to user space /bin/sh startup

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:	Wed, 11 Apr 2007 08:57:27 -0700
From:	"Tom Strader" <tom.strader@...inx.com>
To:	"Jan Engelhardt" <jengelh@...ux01.gwdg.de>
Cc:	<linux-kernel@...r.kernel.org>
Subject: RE: kernel space to user space /bin/sh startup

Nope.  Terminal is set correctly, the kernel is outputting messages, the
command line arguments sent to the kernel have 115200 set.  What would
happen if the getty was not started correctly?  Would the echoes in rcS
still appear?  I feel like it may be related to the getty and userspace
prints due to the fact the kernel is still printing and responding to
commands.
Tom

-----Original Message-----
From: Jan Engelhardt [mailto:jengelh@...ux01.gwdg.de] 
Sent: Wednesday, April 11, 2007 8:48 AM
To: Tom Strader
Cc: linux-kernel@...r.kernel.org
Subject: Re: kernel space to user space /bin/sh startup


On Apr 10 2007 11:22, Tom Strader wrote:

>console::sysinit:/etc/init.d/rcS
>console::respawn:/sbin/getty -L 115200 /dev/ttyS0 vt100

>Now I can type on the console and characters are echoed back, pressing
>ctrl-c echoes: "uart_flush_buffer(0) called" so the code is still
>running, but I am not sure where I am or why I see no login prompt or
>shell command line.
>I never see the "mounting filesystems..." echoed to the screen, but the
>code does not stall and no errors are reported by the kernel.  Any help
>during the transition from init/main.c in kernel space to user space
>would be appreciated, so I could debug this further.
>I have looked around and have not seen a solution for my problem, most
>likely due to the fact that I am not entirely sure what the problem is.

Perhaps your terminal program is set to 9600 bps?



Jan
-- 


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