All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Biggers <ebiggers@kernel.org>
To: Lukas Czerner <lczerner@redhat.com>
Cc: hirofumi@mail.parknet.co.jp, jack@suse.cz,
	linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com,
	tytso@mit.edu,
	syzbot <syzbot+6ba92bd00d5093f7e371@syzkaller.appspotmail.com>,
	linux-ext4@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: [syzbot] KASAN: use-after-free Read in move_expired_inodes (2)
Date: Mon, 24 Oct 2022 22:24:29 -0700	[thread overview]
Message-ID: <Y1dzDVZQ49nQdMUv@sol.localdomain> (raw)
In-Reply-To: <000000000000673b6305eac37e1f@google.com>

On Tue, Oct 11, 2022 at 07:57:23AM -0700, syzbot wrote:
> syzbot has bisected this issue to:
> 
> commit cbfecb927f429a6fa613d74b998496bd71e4438a
> Author: Lukas Czerner <lczerner@redhat.com>
> Date:   Thu Aug 25 10:06:57 2022 +0000
> 
>     fs: record I_DIRTY_TIME even if inode already has I_DIRTY_INODE
> 
> bisection log:  https://syzkaller.appspot.com/x/bisect.txt?x=17e93452880000
> start commit:   493ffd6605b2 Merge tag 'ucount-rlimits-cleanups-for-v5.19'..
> git tree:       upstream
> final oops:     https://syzkaller.appspot.com/x/report.txt?x=14193452880000
> console output: https://syzkaller.appspot.com/x/log.txt?x=10193452880000
> kernel config:  https://syzkaller.appspot.com/x/.config?x=d19f5d16783f901
> dashboard link: https://syzkaller.appspot.com/bug?extid=6ba92bd00d5093f7e371
> syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=1724028a880000
> C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=17419234880000
> 
> Reported-by: syzbot+6ba92bd00d5093f7e371@syzkaller.appspotmail.com
> Fixes: cbfecb927f42 ("fs: record I_DIRTY_TIME even if inode already has I_DIRTY_INODE")
> 
> For information about bisection process see: https://goo.gl/tpsmEJ#bisection

Lukas, are you looking into this?

- Eric

      reply	other threads:[~2022-10-25  5:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-11  8:44 [syzbot] KASAN: use-after-free Read in move_expired_inodes (2) syzbot
2022-10-11 14:57 ` syzbot
2022-10-25  5:24   ` Eric Biggers [this message]

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=Y1dzDVZQ49nQdMUv@sol.localdomain \
    --to=ebiggers@kernel.org \
    --cc=hirofumi@mail.parknet.co.jp \
    --cc=jack@suse.cz \
    --cc=lczerner@redhat.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=syzbot+6ba92bd00d5093f7e371@syzkaller.appspotmail.com \
    --cc=syzkaller-bugs@googlegroups.com \
    --cc=tytso@mit.edu \
    /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.