From: Al Viro <viro@zeniv.linux.org.uk>
To: Palash Oswal <oswalpalash@gmail.com>
Cc: akpm@linux-foundation.org, dave@stgolabs.net,
Kees Cook <keescook@chromium.org>,
linux-kernel@vger.kernel.org, mingo@kernel.org,
peterz@infradead.org, rppt@linux.vnet.ibm.com, sds@tycho.nsa.gov,
syzkaller-bugs@googlegroups.com
Subject: Re: kernel panic: Attempted to kill init!
Date: Tue, 9 Mar 2021 14:25:36 +0000 [thread overview]
Message-ID: <YEeFYMcdPVNrKRJT@zeniv-ca.linux.org.uk> (raw)
In-Reply-To: <CAGyP=7fHhyrTP-u0tqCy5ZHzZN0v_0dAoj6dCHnFuBbqtfnBmQ@mail.gmail.com>
On Tue, Mar 09, 2021 at 11:29:14AM +0530, Palash Oswal wrote:
> I observe the following result(notice the segfault in systemd):
> root@sandbox:~# ./repro
> [ 9.457767] got to 221
> [ 9.457791] got to 183
> [ 9.459144] got to 201
> [ 9.459471] got to 208
> [ 9.459773] got to 210
> [ 9.462602] got to 270
> [ 9.488551] systemd[1]: segfault at 7ffe59fd7fb8 ip
> 000055be8f20b466 sp 00007ffe59fd7fc0 error 6 in
> systemd[55be8f15f000+ed000]
> [ 9.490723] Code: 00 00 00 00 41 57 41 56 41 55 41 54 55 53 89 fd
> 48 81 ec 48 01 00 00 64 48 8b 04 25 28 00 00 00 48 89 84 24 38 01 00
> 00 31 c0 <e8> f5 bf f7 ff 83 f8 01 0f 84 b7 00 00 00 48 8d 9c 240
> [ 9.492637] Kernel panic - not syncing: Attempted to kill init!
> exitcode=0x0000000b
Lovely. So something in that sequence of syscalls manages to trigger
segfault in unrelated process. What happens if you put it to sleep
right after open_by_handle_at() (e.g. by read(2) from fd 0, etc.)?
next prev parent reply other threads:[~2021-03-09 14:31 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-08 16:36 Palash Oswal
2021-03-08 17:18 ` Al Viro
2021-03-09 5:59 ` Palash Oswal
2021-03-09 14:25 ` Al Viro [this message]
2021-03-09 15:06 ` Dmitry Vyukov
2021-03-10 7:33 ` Palash Oswal
2021-03-09 21:30 ` Eric W. Biederman
2021-03-10 9:02 ` Palash Oswal
2021-03-10 9:08 ` Dmitry Vyukov
2021-03-10 9:41 ` Palash Oswal
-- strict thread matches above, loose matches on Subject: below --
2022-12-22 4:35 Hao Sun
2022-12-28 6:35 ` Yonghong Song
2022-12-30 9:54 ` Hao Sun
2022-12-30 16:55 ` Alexei Starovoitov
2023-01-03 12:46 ` Hao Sun
2023-01-03 18:33 ` Alexei Starovoitov
2023-01-05 9:00 ` Hao Sun
2023-01-06 3:01 ` Alexei Starovoitov
2004-12-31 4:40 Srinivas G.
2004-12-31 8:07 ` Arjan van de Ven
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=YEeFYMcdPVNrKRJT@zeniv-ca.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=akpm@linux-foundation.org \
--cc=dave@stgolabs.net \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=oswalpalash@gmail.com \
--cc=peterz@infradead.org \
--cc=rppt@linux.vnet.ibm.com \
--cc=sds@tycho.nsa.gov \
--cc=syzkaller-bugs@googlegroups.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®