All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+8a5a459f324d510ea15a@syzkaller.appspotmail.com>
To: jack@suse.com, jack@suse.cz, khoroshilov@ispras.ru,
	linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
	lvc-project@linuxtesting.org, pchelkin@ispras.ru,
	syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [udf?] KASAN: null-ptr-deref Write in udf_write_fi
Date: Mon, 27 Feb 2023 10:42:28 -0800	[thread overview]
Message-ID: <000000000000478fb705f5b2d79c@google.com> (raw)
In-Reply-To: <000000000000dca7e505e9978943@google.com>

syzbot suspects this issue was fixed by commit:

commit e9109a92d2a95889498bed3719cd2318892171a2
Author: Jan Kara <jack@suse.cz>
Date:   Thu Oct 6 14:41:23 2022 +0000

    udf: Convert udf_rename() to new directory iteration code

bisection log:  https://syzkaller.appspot.com/x/bisect.txt?x=1191f00f480000
start commit:   55be6084c8e0 Merge tag 'timers-core-2022-10-05' of git://g..
git tree:       upstream
kernel config:  https://syzkaller.appspot.com/x/.config?x=df75278aabf0681a
dashboard link: https://syzkaller.appspot.com/bug?extid=8a5a459f324d510ea15a
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=100a46c2880000
C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=116a4e72880000

If the result looks correct, please mark the issue as fixed by replying with:

#syz fix: udf: Convert udf_rename() to new directory iteration code

For information about bisection process see: https://goo.gl/tpsmEJ#bisection

  reply	other threads:[~2023-02-27 18:42 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-26 17:05 [syzbot] KASAN: null-ptr-deref Write in udf_write_fi syzbot
2023-02-27 18:42 ` syzbot [this message]
2023-02-28  7:56   ` [syzbot] [udf?] " Dmitry Vyukov

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=000000000000478fb705f5b2d79c@google.com \
    --to=syzbot+8a5a459f324d510ea15a@syzkaller.appspotmail.com \
    --cc=jack@suse.com \
    --cc=jack@suse.cz \
    --cc=khoroshilov@ispras.ru \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lvc-project@linuxtesting.org \
    --cc=pchelkin@ispras.ru \
    --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.