linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Luis Chamberlain <mcgrof@kernel.org>
To: syzbot <syzbot+f3c6fda1297c748a7076@syzkaller.appspotmail.com>,
	Jan Kara <jack@suse.cz>, Dave Chinner <david@fromorbit.com>
Cc: brauner@kernel.org, hare@suse.de, joel.granados@kernel.org,
	john.g.garry@oracle.com, kees@kernel.org,
	linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-mm@kvack.org, syzkaller-bugs@googlegroups.com,
	willy@infradead.org
Subject: Re: [syzbot] [mm?] [fs?] BUG: sleeping function called from invalid context in folio_mc_copy
Date: Thu, 27 Mar 2025 14:42:48 -0700	[thread overview]
Message-ID: <Z-XGWGKJJThjtsXM@bombadil.infradead.org> (raw)
In-Reply-To: <67e57c41.050a0220.2f068f.0033.GAE@google.com>

On Thu, Mar 27, 2025 at 09:26:41AM -0700, syzbot wrote:
> Hello,

Thanks, this is a known issue and we're having a hard time reproducing [0].

> C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=152d4de4580000

Thanks! Sadly this has not yet been able to let me reprodouce the issue,
and so we're trying to come up with other ways to test the imminent spin
lock + sleep on buffer_migrate_folio_norefs() path different ways now,
including a new fstests [1] but no luck yet.

We will work on a fix, let's follow up on the original report [0] or the new
tests case suggested thread [1] thanks!

[0] https://lkml.kernel.org/r/202503101536.27099c77-lkp@intel.com                    
[1] https://lkml.kernel.org/r/0250326185101.2237319-1-mcgrof@kernel.org

  Luis

  reply	other threads:[~2025-03-27 21:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-27 16:26 [syzbot] [mm?] [fs?] BUG: sleeping function called from invalid context in folio_mc_copy syzbot
2025-03-27 21:42 ` Luis Chamberlain [this message]
2025-03-30  2:05   ` Rik van Riel
2025-03-30  2:26     ` Luis Chamberlain

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=Z-XGWGKJJThjtsXM@bombadil.infradead.org \
    --to=mcgrof@kernel.org \
    --cc=brauner@kernel.org \
    --cc=david@fromorbit.com \
    --cc=hare@suse.de \
    --cc=jack@suse.cz \
    --cc=joel.granados@kernel.org \
    --cc=john.g.garry@oracle.com \
    --cc=kees@kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=syzbot+f3c6fda1297c748a7076@syzkaller.appspotmail.com \
    --cc=syzkaller-bugs@googlegroups.com \
    --cc=willy@infradead.org \
    /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).