All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+c8564fc0a96e3ecbe4d4@syzkaller.appspotmail.com>
To: eadavis@sina.com, linux-kernel@vger.kernel.org,
	 syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [dm?] WARNING: zero-size vmalloc in cache_ctr
Date: Mon, 02 Nov 2026 00:33:02 -0800	[thread overview]
Message-ID: <6ae84abe.e91b1aea.38328a.0007.GAE@google.com> (raw)
In-Reply-To: <20261102080049.417712-1-eadavis@sina.com>

Hello,

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

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

Tested on:

commit:         7a19f0cc Merge branch 'for-next/core' into for-kernelci
git tree:       git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci
console output: https://syzkaller.appspot.com/x/log.txt?x=166b1cb1580000
kernel config:  https://syzkaller.appspot.com/x/.config?x=6602d83d2f34eb80
dashboard link: https://syzkaller.appspot.com/bug?extid=c8564fc0a96e3ecbe4d4
compiler:       Debian clang version 22.1.8 (1~deb13u4), Debian LLD 22.1.8
userspace arch: arm64
patch:          https://syzkaller.appspot.com/x/patch.diff?x=16ea4f95580000

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

  reply	other threads:[~2026-11-02  8:33 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-31 17:03 [syzbot] [dm?] WARNING: zero-size vmalloc in cache_ctr syzbot
2026-11-02  7:15 ` Edward Adam Davis
2026-11-02  7:57   ` syzbot
2026-11-02  8:00 ` Edward Adam Davis
2026-11-02  8:33   ` syzbot [this message]
2026-11-02  8:07 ` Edward Adam Davis

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=6ae84abe.e91b1aea.38328a.0007.GAE@google.com \
    --to=syzbot+c8564fc0a96e3ecbe4d4@syzkaller.appspotmail.com \
    --cc=eadavis@sina.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.