All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+72f94b474d6e50b71ffc@syzkaller.appspotmail.com>
To: kartikey406@gmail.com, linux-kernel@vger.kernel.org,
	 syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [comedi?] BUG: unable to handle kernel paging request in dt2815_attach
Date: Sun, 25 Jan 2026 23:04:03 -0800	[thread overview]
Message-ID: <697711e3.a00a0220.33ccc7.0034.GAE@google.com> (raw)
In-Reply-To: <20260126064243.10298-1-kartikey406@gmail.com>

Hello,

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

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

Tested on:

commit:         63804fed Linux 6.19-rc7
git tree:       upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=157f5e8a580000
kernel config:  https://syzkaller.appspot.com/x/.config?x=e2e5d7c9c1e01cf4
dashboard link: https://syzkaller.appspot.com/bug?extid=72f94b474d6e50b71ffc
compiler:       Debian clang version 21.1.8 (++20251221033036+2078da43e25a-1~exp1~20251221153213.50), Debian LLD 21.1.8
patch:          https://syzkaller.appspot.com/x/patch.diff?x=11ebfe8a580000

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

       reply	other threads:[~2026-01-26  7:04 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20260126064243.10298-1-kartikey406@gmail.com>
2026-01-26  7:04 ` syzbot [this message]
     [not found] <20260126061729.9345-1-kartikey406@gmail.com>
2026-01-26  6:33 ` [syzbot] [comedi?] BUG: unable to handle kernel paging request in dt2815_attach syzbot
     [not found] <20260126054835.7392-1-kartikey406@gmail.com>
2026-01-26  6:04 ` syzbot
     [not found] <20260126051936.5684-1-kartikey406@gmail.com>
2026-01-26  5:36 ` syzbot
2026-01-24  6:45 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=697711e3.a00a0220.33ccc7.0034.GAE@google.com \
    --to=syzbot+72f94b474d6e50b71ffc@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.