public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+76f33569875eb708e575@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, lizhi.xu@windriver.com,
	 syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [afs?] WARNING: lock held when returning to user space in afs_proc_addr_prefs_write
Date: Wed, 25 Dec 2024 17:25:03 -0800	[thread overview]
Message-ID: <676cb06f.050a0220.2f3838.03d5.GAE@google.com> (raw)
In-Reply-To: <20241226010508.2320551-1-lizhi.xu@windriver.com>

Hello,

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

Reported-by: syzbot+76f33569875eb708e575@syzkaller.appspotmail.com
Tested-by: syzbot+76f33569875eb708e575@syzkaller.appspotmail.com

Tested on:

commit:         9b2ffa61 Merge tag 'mtd/fixes-for-6.13-rc5' of git://g..
git tree:       upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=137b8018580000
kernel config:  https://syzkaller.appspot.com/x/.config?x=c078001e66e4a17e
dashboard link: https://syzkaller.appspot.com/bug?extid=76f33569875eb708e575
compiler:       gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40
patch:          https://syzkaller.appspot.com/x/patch.diff?x=10731adf980000

Note: testing is done by a robot and is best-effort only.

       reply	other threads:[~2024-12-26  1:25 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20241226010508.2320551-1-lizhi.xu@windriver.com>
2024-12-26  1:25 ` syzbot [this message]
2024-12-25 21:54 [syzbot] [afs?] WARNING: lock held when returning to user space in afs_proc_addr_prefs_write syzbot
2025-01-06 14:06 ` David Howells
2025-01-06 14:27   ` syzbot
2025-01-06 16:44 ` David Howells
2025-01-06 17:05   ` 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=676cb06f.050a0220.2f3838.03d5.GAE@google.com \
    --to=syzbot+76f33569875eb708e575@syzkaller.appspotmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lizhi.xu@windriver.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