All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+d8d4c31d40f868eaea30@syzkaller.appspotmail.com>
To: kapoorarnav43@gmail.com, linux-kernel@vger.kernel.org,
	 syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [mm?] INFO: rcu detected stall in purge_vmap_node
Date: Mon, 12 Jan 2026 02:45:02 -0800	[thread overview]
Message-ID: <6964d0ae.050a0220.eaf7.009f.GAE@google.com> (raw)
In-Reply-To: <8b25a7d9-046c-4319-9434-bc30430a0a64n@googlegroups.com>

Hello,

syzbot tried to test the proposed patch but the build/boot failed:

failed to apply patch:
The next patch would create the file mm/kasan/shadow.c,
which already exists!  Applying it anyway.
checking file mm/kasan/shadow.c
patch: **** unexpected end of file in patch



Tested on:

commit:         0f61b186 Linux 6.19-rc5
git tree:       upstream
kernel config:  https://syzkaller.appspot.com/x/.config?x=a11e0f726bfb6765
dashboard link: https://syzkaller.appspot.com/bug?extid=d8d4c31d40f868eaea30
compiler:       
patch:          https://syzkaller.appspot.com/x/patch.diff?x=100aa844580000


       reply	other threads:[~2026-01-12 10:45 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <8b25a7d9-046c-4319-9434-bc30430a0a64n@googlegroups.com>
2026-01-12 10:45 ` syzbot [this message]
2026-01-12 12:08 [PATCH v2] mm/vmalloc: prevent RCU stalls in kasan_release_vmalloc_node Hillf Danton
2026-01-12 13:13 ` [syzbot] [mm?] INFO: rcu detected stall in purge_vmap_node syzbot
2026-01-12 13:38   ` Hillf Danton
2026-01-12 14:50     ` Deepanshu Kartikey
     [not found] <20260112075620.621464-1-kartikey406@gmail.com>
2026-01-12  8:40 ` syzbot
  -- strict thread matches above, loose matches on Subject: below --
2026-01-12  5:33 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=6964d0ae.050a0220.eaf7.009f.GAE@google.com \
    --to=syzbot+d8d4c31d40f868eaea30@syzkaller.appspotmail.com \
    --cc=kapoorarnav43@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.