From: syzbot <syzbot+76f33569875eb708e575@syzkaller.appspotmail.com>
To: dhowells@redhat.com, linux-afs@lists.infradead.org,
linux-kernel@vger.kernel.org, marc.dionne@auristor.com,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [afs?] WARNING: lock held when returning to user space in afs_proc_addr_prefs_write
Date: Mon, 06 Jan 2025 09:05:02 -0800 [thread overview]
Message-ID: <677c0d3e.050a0220.3b3668.0013.GAE@google.com> (raw)
In-Reply-To: <377468.1736181885@warthog.procyon.org.uk>
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: 13563da6 Merge tag 'vfio-v6.13-rc7' of https://github...
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=154cb6f8580000
kernel config: https://syzkaller.appspot.com/x/.config?x=ad08f7f48e13abcd
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=164dc4b0580000
Note: testing is done by a robot and is best-effort only.
next prev parent reply other threads:[~2025-01-06 17:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-25 21:54 [syzbot] [afs?] WARNING: lock held when returning to user space in afs_proc_addr_prefs_write syzbot
2024-12-26 1:05 ` [syzbot] " syzbot
2024-12-26 1:26 ` [PATCH] afs: Merge preference rule failure condition Lizhi Xu
2025-01-06 13:48 ` David Howells
2025-01-06 14:06 ` [syzbot] [afs?] WARNING: lock held when returning to user space in afs_proc_addr_prefs_write David Howells
2025-01-06 14:27 ` syzbot
2025-01-06 16:44 ` David Howells
2025-01-06 17:05 ` syzbot [this message]
[not found] <20241226010508.2320551-1-lizhi.xu@windriver.com>
2024-12-26 1:25 ` 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=677c0d3e.050a0220.3b3668.0013.GAE@google.com \
--to=syzbot+76f33569875eb708e575@syzkaller.appspotmail.com \
--cc=dhowells@redhat.com \
--cc=linux-afs@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marc.dionne@auristor.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