Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: syzbot <syzbot+02a127be2df04bdc5df0@syzkaller.appspotmail.com>
To: clm@fb.com, dsterba@suse.com, josef@toxicpanda.com,
	 linux-btrfs@vger.kernel.org, linux-kernel@vger.kernel.org,
	 quwenruo.btrfs@gmx.com, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [btrfs?] BUG: sleeping function called from invalid context in getname_kernel
Date: Wed, 09 Oct 2024 17:54:03 -0700	[thread overview]
Message-ID: <670725ab.050a0220.1139e6.0015.GAE@google.com> (raw)
In-Reply-To: <5278c962-8f78-499d-9723-38a3d6520e19@gmx.com>

Hello,

syzbot has tested the proposed patch and the reproducer did not trigger any issue:

Reported-by: syzbot+02a127be2df04bdc5df0@syzkaller.appspotmail.com
Tested-by: syzbot+02a127be2df04bdc5df0@syzkaller.appspotmail.com

Tested on:

commit:         964c2da7 btrfs: make buffered write to copy one page a..
git tree:       https://github.com/adam900710/linux.git subpage_read
console output: https://syzkaller.appspot.com/x/log.txt?x=115d8f07980000
kernel config:  https://syzkaller.appspot.com/x/.config?x=3ec5955a0d4f6ede
dashboard link: https://syzkaller.appspot.com/bug?extid=02a127be2df04bdc5df0
compiler:       Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40

Note: no patches were applied.
Note: testing is done by a robot and is best-effort only.

  reply	other threads:[~2024-10-10  0:54 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-09 13:48 [syzbot] [btrfs?] BUG: sleeping function called from invalid context in getname_kernel syzbot
2024-10-09 23:21 ` Qu Wenruo
2024-10-10  0:54   ` syzbot [this message]
2024-10-10 13:02 ` syzbot

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=670725ab.050a0220.1139e6.0015.GAE@google.com \
    --to=syzbot+02a127be2df04bdc5df0@syzkaller.appspotmail.com \
    --cc=clm@fb.com \
    --cc=dsterba@suse.com \
    --cc=josef@toxicpanda.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=quwenruo.btrfs@gmx.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