From: syzbot <syzbot+f26d7c75c26ec19790e7@syzkaller.appspotmail.com>
To: kartikey406@gmail.com, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [mm?] WARNING in hugetlb_vma_assert_locked
Date: Mon, 13 Oct 2025 20:40:05 -0700 [thread overview]
Message-ID: <68edc615.050a0220.ac43.0085.GAE@google.com> (raw)
In-Reply-To: <20251014033532.344635-1-kartikey406@gmail.com>
Hello,
syzbot tried to test the proposed patch but the build/boot failed:
failed to apply patch:
checking file fs/hugetlbfs/inode.c
Hunk #1 FAILED at 478.
Hunk #2 FAILED at 496.
2 out of 2 hunks FAILED
checking file mm/hugetlb.c
Tested on:
commit: 52ba7632 Add linux-next specific files for 20251013
git tree: linux-next
kernel config: https://syzkaller.appspot.com/x/.config?x=135377594f35b576
dashboard link: https://syzkaller.appspot.com/bug?extid=f26d7c75c26ec19790e7
compiler:
patch: https://syzkaller.appspot.com/x/patch.diff?x=1681cc58580000
next parent reply other threads:[~2025-10-14 3:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20251014033532.344635-1-kartikey406@gmail.com>
2025-10-14 3:40 ` 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] <20251014003959.13323-1-kartikey406@gmail.com>
2025-10-14 3:09 ` syzbot
[not found] <20251007060147.340787-1-kartikey406@gmail.com>
2025-10-07 7:28 ` 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=68edc615.050a0220.ac43.0085.GAE@google.com \
--to=syzbot+f26d7c75c26ec19790e7@syzkaller.appspotmail.com \
--cc=kartikey406@gmail.com \
--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 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.