From: Gao Xiang <hsiangkao@linux.alibaba.com>
To: syzbot <syzbot+27cc650ef45b379dfe5a@syzkaller.appspotmail.com>,
linux-erofs@lists.ozlabs.org, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [erofs?] BUG: using smp_processor_id() in preemptible code in z_erofs_get_gbuf
Date: Wed, 24 Apr 2024 07:34:14 +0800 [thread overview]
Message-ID: <4ac3f6e8-9801-473e-85e0-405a4283dc2a@linux.alibaba.com> (raw)
In-Reply-To: <00000000000035775f0615b72d01@google.com>
On 2024/4/10 13:19, syzbot wrote:
> Hello,
>
> syzbot tried to test the proposed patch but the build/boot failed:
#syz invalid
Since
https://lore.kernel.org/r/20240408215231.3376659-1-dhavale@google.com
has been folded into the original patch and this issue is only in -next.
Thanks,
Gao Xiang
prev parent reply other threads:[~2024-04-23 23:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-08 18:23 [syzbot] [erofs?] BUG: using smp_processor_id() in preemptible code in z_erofs_get_gbuf syzbot
2024-04-09 1:47 ` Gao Xiang
2024-04-10 5:19 ` syzbot
2024-04-23 23:34 ` Gao Xiang [this message]
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=4ac3f6e8-9801-473e-85e0-405a4283dc2a@linux.alibaba.com \
--to=hsiangkao@linux.alibaba.com \
--cc=linux-erofs@lists.ozlabs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=syzbot+27cc650ef45b379dfe5a@syzkaller.appspotmail.com \
--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;
as well as URLs for NNTP newsgroup(s).