linux-kernel - Re: BUG: unable to handle kernel paging request from pty

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]

Message-ID: <56D00D5D.8020709@suse.cz>
Date:	Fri, 26 Feb 2016 09:31:25 +0100
From:	Jiri Slaby <jslaby@...e.cz>
To:	Jiri Kosina <jikos@...nel.org>,
	Linus Torvalds <torvalds@...ux-foundation.org>
Cc:	Peter Hurley <peter@...leysoftware.com>,
	Greg KH <gregkh@...uxfoundation.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	stable <stable@...r.kernel.org>, lwn@....net,
	Steven Rostedt <rostedt@...dmis.org>
Subject: Re: BUG: unable to handle kernel paging request from pty_write [was:
 Linux 4.4.2]

On 02/25/2016, 11:00 PM, Jiri Kosina wrote:
>> If it was one of the calls _in_ try_to_wake_up() that called to insane 
>> code, I would have expected to see try_to_wake_up on the stack.
> 
> try_to_wake_up() is very likely to be inlined into wake_up_process(), and 
> therefore in such cases will never be on the stack as a return address; 
> it'll always be wake_up_process().

Actually it is not inlined, see core.s at:
http://labs.suse.cz/jslaby/bug-968218/

thanks,
-- 
js
suse labs