linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: syzbot <syzbot+b4c65e7d749285a82467@syzkaller.appspotmail.com>
To: brauner@kernel.org, hdanton@sina.com,
	linux-fsdevel@vger.kernel.org,  linux-kernel@vger.kernel.org,
	syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [kernel?] general protection fault in put_ipc_ns
Date: Mon, 17 Nov 2025 19:03:04 -0800	[thread overview]
Message-ID: <691be1e8.a70a0220.f6df1.004c.GAE@google.com> (raw)
In-Reply-To: <20251118002044.9391-1-hdanton@sina.com>

Hello,

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

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

Tested on:

commit:         cc7d6c65 nstree: fix kernel-doc comments for internal ..
git tree:       https://github.com/brauner/linux.git namespace-6.19
console output: https://syzkaller.appspot.com/x/log.txt?x=10d8e212580000
kernel config:  https://syzkaller.appspot.com/x/.config?x=1e17ff55912ea78d
dashboard link: https://syzkaller.appspot.com/bug?extid=b4c65e7d749285a82467
compiler:       Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8

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

      reply	other threads:[~2025-11-18  3:03 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <691b044b.a70a0220.3124cb.009d.GAE@google.com>
2025-11-18  0:20 ` [syzbot] [kernel?] general protection fault in put_ipc_ns Hillf Danton
2025-11-18  3:03   ` syzbot [this message]

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=691be1e8.a70a0220.f6df1.004c.GAE@google.com \
    --to=syzbot+b4c65e7d749285a82467@syzkaller.appspotmail.com \
    --cc=brauner@kernel.org \
    --cc=hdanton@sina.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --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;
as well as URLs for NNTP newsgroup(s).