From: Pengfei Xu <pengfei.xu@intel.com>
To: <viro@zeniv.linux.org.uk>
Cc: <heng.su@intel.com>, <linux-kernel@vger.kernel.org>,
<davem@davemloft.net>, <jmaloy@redhat.com>, <kuba@kernel.org>
Subject: Update bisect info and new repro code for "[syzbot] WARNING in _copy_from_iter"
Date: Fri, 30 Dec 2022 10:33:02 +0800 [thread overview]
Message-ID: <Y65N3pgLMsxZ99lo@xpf.sh.intel.com> (raw)
Hi Viro,
Related email link:
https://lore.kernel.org/lkml/Y5WlLoCBcHbfKBD5@ZenIV/
syzbot link:
https://syzkaller.appspot.com/bug?id=4694bd1c1c0019f067af5b6e14e8ef02431b6b34
I reproduced on TGL-H with v6.2-rc1 kernel.
All reproduced code bisect info are in link:
https://github.com/xupengfe/syzkaller_logs/tree/main/221228_010310__copy_from_iter
I hope it's helpful.
Thanks!
BR.
next reply other threads:[~2022-12-30 2:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-30 2:33 Pengfei Xu [this message]
2023-01-05 1:48 ` Update bisect info and new repro code for "[syzbot] WARNING in _copy_from_iter" Pengfei Xu
2023-01-05 3:38 ` [Q] is the amount of residual bytes still not guaranteed for to be available for some old SCSI drivers? (was Re: Update bisect info and new repro code for "[syzbot] WARNING in _copy_from_iter") Al Viro
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=Y65N3pgLMsxZ99lo@xpf.sh.intel.com \
--to=pengfei.xu@intel.com \
--cc=davem@davemloft.net \
--cc=heng.su@intel.com \
--cc=jmaloy@redhat.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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