mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jan Kara <jack@suse.cz>
To: Gianfranco Trad <gianf.trad@gmail.com>
Cc: jan Kara <jack@suse.com>,
	syzbot <syzbot+ddf8715339c89280b6fc@syzkaller.appspotmail.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [syzbot] [udf?] general protection fault in udf_read_folio
Date: Tue, 22 Oct 2024 11:02:22 +0200	[thread overview]
Message-ID: <20241022090222.tndd3zqlgtohjnce@quack3> (raw)
In-Reply-To: <2ae7d2b0-0053-4cff-9352-d180c243ded4@gmail.com>

On Tue 22-10-24 02:19:19, Gianfranco Trad wrote:
> On 22/10/24 02:04, syzbot wrote:
> > Hello,
> > 
> > syzbot has tested the proposed patch and the reproducer did not trigger any issue:
> > 
> > Reported-by: syzbot+ddf8715339c89280b6fc@syzkaller.appspotmail.com
> > Tested-by: syzbot+ddf8715339c89280b6fc@syzkaller.appspotmail.com
> > 
> > Tested on:
> > 
> > commit:         c2ee9f59 KVM: selftests: Fix build on on non-x86 archi..
> > git tree:       upstream
> > console output: https://syzkaller.appspot.com/x/log.txt?x=12684640580000
> > kernel config:  https://syzkaller.appspot.com/x/.config?x=fc6f8ce8c5369043
> > dashboard link: https://syzkaller.appspot.com/bug?extid=ddf8715339c89280b6fc
> > compiler:       Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
> > 
> > Note: no patches were applied.
> > Note: testing is done by a robot and is best-effort only.
> 
> Hi Jan,
> 
> syzbot reported a null-ptr-deref in udf_read_folio a month ago [1].
> 
> This bug was marked as still open on syzbot, so I retested the reproducer
> (no patch applied) to check if the bug was still valid upstream, seems not
> (as reported up).
> Wondering if syzbot will now try to find another reproducer, since after
> this check the reproducer was crossed away on the syzbot web UI, or if the
> bug can be considered closed.
> I hope this might help.

I believe syzbot tries to bisect back to the fix and reports it. Then
either you can ack it (which closes the bug) or the bug will auto-close
after some time if there's no reproducer.

								Honza
-- 
Jan Kara <jack@suse.com>
SUSE Labs, CR

  reply	other threads:[~2024-10-22  9:02 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <40b42775-ca29-4c63-b13c-7b02911379a1@gmail.com>
2024-10-22  0:04 ` syzbot
2024-10-22  0:19   ` Gianfranco Trad
2024-10-22  9:02     ` Jan Kara [this message]
2024-09-21 17:06 syzbot
2024-09-22  4:56 ` Edward Adam Davis
2024-09-22  5:17   ` 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=20241022090222.tndd3zqlgtohjnce@quack3 \
    --to=jack@suse.cz \
    --cc=gianf.trad@gmail.com \
    --cc=jack@suse.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=syzbot+ddf8715339c89280b6fc@syzkaller.appspotmail.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

all inboxes | Powered by JetHome®