linux-kernel - Re: BUG() triggered in do

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

[an error occurred while processing this directive]

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

Message-ID: <CA+55aFyMOBjD+sDwFEwWnufKdJ0E31ggK5M5tTzrt0Zh3Q829g@mail.gmail.com>
Date:	Fri, 10 Jan 2014 17:31:09 +0800
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	Vaibhav Shinde <v.bhav.shinde@...il.com>
Cc:	Tejun Heo <tj@...nel.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Oleg Nesterov <oleg@...hat.com>
Subject: Re: BUG() triggered in do_exit()

Mind posting the actual bug message, and preferably a way to trigger it?

               Linus

On Fri, Jan 10, 2014 at 11:57 AM, Vaibhav Shinde
<v.bhav.shinde@...il.com> wrote:
> Dear All,
>
> I faced this issue on kernel 3.8.13 -
>
> Background -
> An application created SIGSEGV 3 times, whose handling was done properly.
> At generation of SIGSEGV, the do_coredump() failed all 3 times due to
> failure in __get_dumpable () .
>
> The application was again started but this time we didn't get SIGSEGV, the
> BUG () in do_exit was triggered.
> That means schedule () function was failed.
>
> Could you tell the possible reasons for failure in schedule () and
> triggering BUG () in do_exit() ??
--
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/