linux-kernel - Re: NULL dereference OOPS on SysRq-w

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] [day] [month] [year] [list]

Date:	Mon, 28 Apr 2008 15:26:31 +0800
From:	"Dave Young" <hidave.darkstar@...il.com>
To:	dpn@...merica.net
Cc:	"Linux Kernel Mailing List" <linux-kernel@...r.kernel.org>,
	mingo@...e.hu
Subject: Re: NULL dereference OOPS on SysRq-w

On Mon, Apr 28, 2008 at 3:08 PM, Dave Young <hidave.darkstar@...il.com> wrote:
> On Mon, Apr 28, 2008 at 3:01 PM, Dan Noe <dpn@...merica.net> wrote:
>  > Dave Young wrote:
>  >
>  > > [snip]
>  > >
>  > > I have a fix for the NULL pointer reference BUG, tested on my pc.
>  > > ---
>  > >
>  > > "m" will be NULL if seq_printf & seq_puts is called from sched_debug_show
>  > > Use SEQ_* macros to fix it
>  > > Signed-off-by: Dave Young <hidave.darkstar@...il.com>
>  > >
>  >
>  >  There is actually already a patch out for this which simply hasn't made it
>  > upstream yet - Mike Galbraith emailed me with it and it indeed fixes the
>  > problem.  I hadn't realized his email didn't go to lkml.. otherwise I would
>  > have echoed that here to avoid wasting people's time.  My apologies.
>
>  Ok, thanks.
>
>  While debuging this issue I found another BUG about sysrq,
>
>  echo w >/proc/sys/kernel/sysrq
>  My system hangs, there's no response from then on.

Strange, the bug can not be reproduced now. Now I only get the
expected result "Invalid argument".
--
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/