From: Juefei Pu <juefei.pu@email.ucr.edu>
To: Xingyu Li <xli399@ucr.edu>
Cc: Roman Gushchin <roman.gushchin@linux.dev>,
hannes@cmpxchg.org, mhocko@kernel.org, shakeel.butt@linux.dev,
muchun.song@linux.dev, cgroups@vger.kernel.org,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
Yu Hao <yhao016@ucr.edu>
Subject: Re: BUG: general protection fault in get_mem_cgroup_from_objcg
Date: Wed, 4 Sep 2024 12:18:46 -0700 [thread overview]
Message-ID: <CANikGpcg3_hVS+-h5egaLNkHGvG50qVAZ21syT7Ogc6iK1SzKA@mail.gmail.com> (raw)
In-Reply-To: <CALAgD-6Vg9k=wd1zaJ+k-EaWLnzosAn2f=iz7FvhVpdS6eq-dA@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.
For reproducibility, I've created a GitHub repo at
https://github.com/TomAPU/Linux610BugReort, 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.
Yours,
Juefei
On Thu, Aug 29, 2024 at 4:28 PM Xingyu Li <xli399@ucr.edu> wrote:
>
> Juefei: Can you give some input on this?
>
> On Thu, Aug 29, 2024 at 4:24 PM Roman Gushchin <roman.gushchin@linux.dev> wrote:
> >
> > On Wed, Aug 28, 2024 at 10:20:04PM -0700, Xingyu Li wrote:
> > > Hi,
> > >
> > > Here is the kernel config file:
> > > https://gist.github.com/TomAPU/64f5db0fe976a3e94a6dd2b621887cdd
> > >
> > > how long does it take to reproduce?
> > > Juefei will follow on this, and I just CC'ed him.
> >
> > I ran the reproducer for several hours in a vm without much success.
> > So in order to make any progress I'd really need a help from your side.
> > If you can reproduce it consistently, can you, please, try to bisect it?
> >
> > Thanks!
>
>
>
> --
> Yours sincerely,
> Xingyu
prev parent reply other threads:[~2024-09-04 19:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-28 23:09 Xingyu Li
2024-08-29 2:43 ` Roman Gushchin
2024-08-29 5:20 ` Xingyu Li
2024-08-29 23:24 ` Roman Gushchin
2024-08-29 23:27 ` Xingyu Li
2024-09-04 19:18 ` Juefei Pu [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=CANikGpcg3_hVS+-h5egaLNkHGvG50qVAZ21syT7Ogc6iK1SzKA@mail.gmail.com \
--to=juefei.pu@email.ucr.edu \
--cc=cgroups@vger.kernel.org \
--cc=hannes@cmpxchg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@kernel.org \
--cc=muchun.song@linux.dev \
--cc=roman.gushchin@linux.dev \
--cc=shakeel.butt@linux.dev \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox