From: Al Viro <viro@zeniv.linux.org.uk>
To: kernel test robot <oliver.sang@intel.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
linux-fsdevel@vger.kernel.org, lkp@lists.01.org, lkp@intel.com
Subject: Re: [iov_iter] 2418c34937: Initiating_system_reboot
Date: Wed, 28 Apr 2021 03:18:18 +0000 [thread overview]
Message-ID: <YIjT+lZNn46VgscR@zeniv-ca.linux.org.uk> (raw)
In-Reply-To: <20210428023747.GA13086@xsang-OptiPlex-9020>
On Wed, Apr 28, 2021 at 10:37:47AM +0800, kernel test robot wrote:
>
>
> Greeting,
>
> FYI, we noticed the following commit (built with gcc-9):
>
> commit: 2418c34937c42a30ef4bccd923ad664a89e1fbd4 ("iov_iter: optimize iov_iter_advance() for iovec and kvec")
> https://git.kernel.org/cgit/linux/kernel/git/viro/vfs.git untested.iov_iter
>
>
> in testcase: boot
>
> on test machine: qemu-system-x86_64 -enable-kvm -cpu SandyBridge -smp 2 -m 16G
>
> caused below changes (please refer to attached dmesg/kmsg for entire log/backtrace):
>
>
> +--------------------------+------------+------------+
> | | c5f070c68e | 2418c34937 |
> +--------------------------+------------+------------+
> | boot_failures | 0 | 11 |
> | Initiating_system_reboot | 0 | 11 |
> +--------------------------+------------+------------+
>
>
> If you fix the issue, kindly add following tag
> Reported-by: kernel test robot <oliver.sang@intel.com>
Could you run it with soft_panic=1 in command line? Alternatively, some
information about how to reproduce that without running hell knows what
as root on host would be very welcome; I can't imagine a single reason
for needing root to run qemu, to be honest...
next prev parent reply other threads:[~2021-04-28 3:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-28 2:37 kernel test robot
2021-04-28 3:18 ` Al Viro [this message]
2021-04-30 15:54 ` Oliver Sang
2021-04-30 15:40 ` Al Viro
2021-04-28 4:32 ` Al Viro
2021-04-30 15:45 ` Oliver Sang
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=YIjT+lZNn46VgscR@zeniv-ca.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=lkp@lists.01.org \
--cc=oliver.sang@intel.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®