From: Qian Cai <quic_qiancai@quicinc.com>
To: Jens Axboe <axboe@kernel.dk>
Cc: Marek Szyprowski <m.szyprowski@samsung.com>, <kernel-team@fb.com>,
"Stefan Roesch" <shr@fb.com>, <io-uring@vger.kernel.org>,
<linux-fsdevel@vger.kernel.org>, <viro@zeniv.linux.org.uk>
Subject: Re: [PATCH v3 0/2] io-uring: Make statx api stable
Date: Thu, 24 Feb 2022 20:27:24 -0500 [thread overview]
Message-ID: <YhgwfHtP7ry83oUr@qian> (raw)
In-Reply-To: <a906fc93-1295-f27c-b96a-32571039bf92@kernel.dk>
On Thu, Feb 24, 2022 at 07:09:35AM -0700, Jens Axboe wrote:
> > Freeing unused kernel image (initmem) memory: 1024K
> > Run /sbin/init as init process
> > systemd[1]: System time before build time, advancing clock.
> > systemd[1]: Cannot be run in a chroot() environment.
> > systemd[1]: Freezing execution.
> >
> > Reverting them on top of next-20220223 fixes the boot issue. Btw, those
> > patches are not bisectable. The code at
> > 30512d54fae354a2359a740b75a1451b68aa3807 doesn't compile.
>
> Thanks, I'll drop them from for-next until we figure out what that is.
FYI, this breaks the boot on bare-metal as well.
Loading, please wait...
Starting version 245.4-4ubuntu3.15
Running in chroot, ignoring request.
Running in chroot, ignoring request.
Running in chroot, ignoring request.
Running in chroot, ignoring request.
Running in chroot, ignoring request.
/scripts/init-top/console_setup: line 90: can't create /dev/tty1: No such device or address
/scripts/init-top/console_setup: line 126: can't open /dev/tty1: No such device or address
Begin: Loading essential drivers ... /init: line 155: modprobe: Permission denied
/init: line 155: modprobe: Permission denied
/init: line 155: modprobe: Permission denied
/init: line 155: modprobe: Permission denied
/init: line 155: modprobe: Permission denied
/init: line 155: modprobe: Permission denied
/init: line 155: modprobe: Permission denied
/init: line 155: modprobe: Permission denied
next prev parent reply other threads:[~2022-02-25 1:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-15 18:03 [PATCH v3 0/2] io-uring: Make statx api stable Stefan Roesch
2022-02-15 18:03 ` [PATCH v3 1/2] fs: replace const char* parameter in vfs_statx and do_statx with struct filename Stefan Roesch
2022-02-15 18:03 ` [PATCH v3 2/2] io-uring: Copy path name during prepare stage for statx Stefan Roesch
2022-02-18 16:15 ` [PATCH v3 0/2] io-uring: Make statx api stable Jens Axboe
2022-02-22 18:45 ` Jens Axboe
2022-02-22 18:45 ` Jens Axboe
[not found] ` <CGME20220224124715eucas1p2a7d1b7f2a5131ef1dd5b8280c1d3749b@eucas1p2.samsung.com>
2022-02-24 12:47 ` Marek Szyprowski
2022-02-24 14:09 ` Jens Axboe
2022-02-25 1:27 ` Qian Cai [this message]
2022-02-26 1:22 ` Luis Chamberlain
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=YhgwfHtP7ry83oUr@qian \
--to=quic_qiancai@quicinc.com \
--cc=axboe@kernel.dk \
--cc=io-uring@vger.kernel.org \
--cc=kernel-team@fb.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=shr@fb.com \
--cc=viro@zeniv.linux.org.uk \
/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;
as well as URLs for NNTP newsgroup(s).