public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+f26d7c75c26ec19790e7@syzkaller.appspotmail.com>
To: broonie@kernel.org, david@redhat.com, kartikey406@gmail.com,
	 linux-kernel@vger.kernel.org, osalvador@suse.de,
	 syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [mm?] WARNING in hugetlb_vma_assert_locked
Date: Tue, 07 Oct 2025 00:28:02 -0700	[thread overview]
Message-ID: <68e4c102.050a0220.256323.0019.GAE@google.com> (raw)
In-Reply-To: <20251007060147.340787-1-kartikey406@gmail.com>

Hello,

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

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

Tested on:

commit:         4a715314 Add linux-next specific files for 20251006
git tree:       linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=10653092580000
kernel config:  https://syzkaller.appspot.com/x/.config?x=9a5d0a8497f9e6c4
dashboard link: https://syzkaller.appspot.com/bug?extid=f26d7c75c26ec19790e7
compiler:       Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8
patch:          https://syzkaller.appspot.com/x/patch.diff?x=15c255cd980000

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

       reply	other threads:[~2025-10-07  7:28 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20251007060147.340787-1-kartikey406@gmail.com>
2025-10-07  7:28 ` syzbot [this message]
     [not found] <20251014041430.347253-1-kartikey406@gmail.com>
2025-10-14  5:00 ` [syzbot] [mm?] WARNING in hugetlb_vma_assert_locked syzbot
     [not found] <20251014033532.344635-1-kartikey406@gmail.com>
2025-10-14  3:40 ` syzbot
     [not found] <20251014003959.13323-1-kartikey406@gmail.com>
2025-10-14  3:09 ` syzbot
     [not found] <20251003161140.2960355-1-kartikey406@gmail.com>
2025-10-03 16:52 ` syzbot
     [not found] <20250926003239.8582-1-kartikey406@gmail.com>
2025-09-26  2:27 ` syzbot
     [not found] <20250925231946.5171-1-kartikey406@gmail.com>
2025-09-26  0:50 ` syzbot
     [not found] <20250925134312.148341-1-kartikey406@gmail.com>
2025-09-25 14:10 ` syzbot
     [not found] <20250925104041.33750-1-kartikey406@gmail.com>
2025-09-25 13:19 ` syzbot
2025-09-23  9:03 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=68e4c102.050a0220.256323.0019.GAE@google.com \
    --to=syzbot+f26d7c75c26ec19790e7@syzkaller.appspotmail.com \
    --cc=broonie@kernel.org \
    --cc=david@redhat.com \
    --cc=kartikey406@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=osalvador@suse.de \
    --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