From: Hillf Danton <hdanton@sina.com>
To: Breno Leitao <leitao@debian.org>
Cc: syzbot <syzbot+f65a2014305525a9f816@syzkaller.appspotmail.com>,
Thomas Gleixner <tglx@linutronix.de>,
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [fs?] BUG: sleeping function called from invalid context in vfree (2)
Date: Mon, 18 Aug 2025 21:19:01 +0800 [thread overview]
Message-ID: <20250818131902.5039-1-hdanton@sina.com> (raw)
In-Reply-To: <4tu4bjs72dqx2pbamu7mc72dg5fxmrbaklbljyppxllr2hccmf@ig75eaoswryd>
On Mon, 18 Aug 2025 05:40:58 -0700 Breno Leitao wrote:
> On Mon, Aug 18, 2025 at 06:07:57PM +0800, Hillf Danton wrote:
> > > Date: Mon, 18 Aug 2025 01:05:33 -0700 [thread overview]
> > > Hello,
> > >
> > > syzbot found the following issue on:
> > >
> > > HEAD commit: 8f5ae30d69d7 Linux 6.17-rc1
> > > git tree: git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci
> > > console output: https://syzkaller.appspot.com/x/log.txt?x=15232442580000
> > > kernel config: https://syzkaller.appspot.com/x/.config?x=8c5ac3d8b8abfcb
> > > dashboard link: https://syzkaller.appspot.com/bug?extid=f65a2014305525a9f816
> > > userspace arch: arm64
> > > syz repro: https://syzkaller.appspot.com/x/repro.syz?x=14cbaba2580000
> > > C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1157faf0580000
> >
> > #syz test upstream master
>
> I was hitting this issue and I've tested it and the BUG is not there any
> more.
>
> Do you know which commit caused this "regression" ?
>
Looks like the tglx dude's work [1]
[1] Subject: [tip: locking/urgent] futex: Move futex cleanup to __mmdrop()
https://lore.kernel.org/lkml/175414093081.1420.8088049602488588887.tip-bot2@tip-bot2/
> > --- x/include/linux/mm_types.h
> > +++ y/include/linux/mm_types.h
> >
> > @@ -689,9 +697,8 @@ void __mmdrop(struct mm_struct *mm)
> > mm_pasid_drop(mm);
> > mm_destroy_cid(mm);
> > percpu_counter_destroy_many(mm->rss_stat, NR_MM_COUNTERS);
> > - futex_hash_free(mm);
> > -
> > - free_mm(mm);
> > + INIT_WORK(&mm->drop_work, mmdrop_workfn);
>
> should INIT_WORK() be called at setup phase other than at any
> __mmdrop()?
>
> Also, is the scheduling overhead a concern here?
>
Feel free to forget/ignore the tecknique details like your concerns
here because the diff is only to cut the added vfree in atomic context
from a square skull.
prev parent reply other threads:[~2025-08-18 13:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-18 8:05 syzbot
2025-08-18 10:07 ` Hillf Danton
2025-08-18 11:42 ` syzbot
2025-08-18 12:40 ` Breno Leitao
2025-08-18 13:19 ` Hillf Danton [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=20250818131902.5039-1-hdanton@sina.com \
--to=hdanton@sina.com \
--cc=leitao@debian.org \
--cc=linux-kernel@vger.kernel.org \
--cc=syzbot+f65a2014305525a9f816@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tglx@linutronix.de \
/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®