All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+8cbdf9aa6c281a4e6bbe@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, pavankumaryalagada@gmail.com,
	 syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [nfs?] [net?] WARNING in svc_destroy
Date: Sun, 08 Nov 2026 11:43:03 -0800	[thread overview]
Message-ID: <6af0d0c7.5a668245.1aceb6.0011.GAE@google.com> (raw)
In-Reply-To: <avDCXm3QW1x2577L@user>

Hello,

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

Reported-by: syzbot+8cbdf9aa6c281a4e6bbe@syzkaller.appspotmail.com
Tested-by: syzbot+8cbdf9aa6c281a4e6bbe@syzkaller.appspotmail.com

Tested on:

commit:         d164c7d7 Merge tag 'devicetree-fixes-for-7.4-1' of git..
git tree:       git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
console output: https://syzkaller.appspot.com/x/log.txt?x=14bc4ebe580000
kernel config:  https://syzkaller.appspot.com/x/.config?x=1cf189394a856f11
dashboard link: https://syzkaller.appspot.com/bug?extid=8cbdf9aa6c281a4e6bbe
compiler:       gcc (Debian 14.2.0-19) 14.2.0, GNU ld (GNU Binutils for Debian) 2.44
patch:          https://syzkaller.appspot.com/x/patch.diff?x=116d1409580000

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

       reply	other threads:[~2026-11-08 19:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <avDCXm3QW1x2577L@user>
2026-11-08 19:43 ` syzbot [this message]
     [not found] <20261108140816.1083-1-drifabdelmalekmohamedsaid@gmail.com>
2026-11-08 15:00 ` [syzbot] [nfs?] [net?] WARNING in svc_destroy syzbot
     [not found] <20261108140754.1057-1-drifabdelmalekmohamedsaid@gmail.com>
2026-11-08 14:39 ` syzbot
2026-11-06 18:09 [syzbot] [net?] [nfs?] " syzbot
2026-11-08  5:52 ` [syzbot] [nfs?] [net?] " 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=6af0d0c7.5a668245.1aceb6.0011.GAE@google.com \
    --to=syzbot+8cbdf9aa6c281a4e6bbe@syzkaller.appspotmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavankumaryalagada@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.