From: Uladzislau Rezki <urezki@gmail.com>
To: Juefei Pu <juefei.pu@email.ucr.edu>
Cc: Xingyu Li <xli399@ucr.edu>, Uladzislau Rezki <urezki@gmail.com>,
paulmck@kernel.org, frederic@kernel.org,
neeraj.upadhyay@kernel.org, joel@joelfernandes.org,
josh@joshtriplett.org, boqun.feng@gmail.com, rostedt@goodmis.org,
mathieu.desnoyers@efficios.com, jiangshanlai@gmail.com,
qiang.zhang1211@gmail.com, rcu@vger.kernel.org,
linux-kernel@vger.kernel.org, Yu Hao <yhao016@ucr.edu>
Subject: Re: BUG: WARNING in kvfree_rcu_bulk
Date: Mon, 16 Sep 2024 15:54:45 +0200 [thread overview]
Message-ID: <Zug4pQjdWtR0ToMn@pc636> (raw)
In-Reply-To: <CANikGpd-rkQh8EpygeLxcHrO1r+72G2bHA_MQ2CFExDK_KDe_Q@mail.gmail.com>
> After several tests, I found that the same PoC can cause multiple
> different crashes for some unknown reason. Thus, I suspect that the
> bug is capable of performing unintended memory writing without being
> caught by KASAN.
> I tested the PoC on the latest kernel, Linux 6.11 rc7 and it can still
> cause crashes.
> For reproducibility, I've created a GitHub repo at
> https://github.com/TomAPU/Linux611BugReport, which contains the
> software versions we used, the QEMU arguments we used to boot up the
> kernel, the kernel config we used, the pre-compiled kernel image,
> Dockerfile that can be used to compile the kernel.
> I hope this repo will be helpful for analyzing the bug.
>
Could you please help to bisect this bug then?
Thanks!
--
Uladzislau Rezki
prev parent reply other threads:[~2024-09-16 13:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-28 21:30 BUG: WARNING in kvfree_rcu_bulk Xingyu Li
2024-08-29 8:17 ` Uladzislau Rezki
2024-08-29 23:29 ` Xingyu Li
2024-09-04 17:52 ` Uladzislau Rezki
2024-09-05 2:23 ` Xingyu Li
2024-09-12 16:08 ` Uladzislau Rezki
2024-09-16 0:02 ` Xingyu Li
2024-09-16 5:12 ` Juefei Pu
2024-09-16 13:54 ` Uladzislau Rezki [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=Zug4pQjdWtR0ToMn@pc636 \
--to=urezki@gmail.com \
--cc=boqun.feng@gmail.com \
--cc=frederic@kernel.org \
--cc=jiangshanlai@gmail.com \
--cc=joel@joelfernandes.org \
--cc=josh@joshtriplett.org \
--cc=juefei.pu@email.ucr.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=neeraj.upadhyay@kernel.org \
--cc=paulmck@kernel.org \
--cc=qiang.zhang1211@gmail.com \
--cc=rcu@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=xli399@ucr.edu \
--cc=yhao016@ucr.edu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.