gfs2.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Andreas Gruenbacher <agruenba@redhat.com>
To: Christian Brauner <brauner@kernel.org>
Cc: xingwei lee <xrivendell7@gmail.com>,
	 syzbot+0c64a8706d587f73409e@syzkaller.appspotmail.com,
	gfs2@lists.linux.dev,  linux-fsdevel@vger.kernel.org,
	linux-kernel@vger.kernel.org,  syzkaller-bugs@googlegroups.com,
	viro@zeniv.linux.org.uk
Subject: Re: [syzbot] [gfs2] WARNING in vfs_utimes
Date: Wed, 13 Dec 2023 16:10:18 +0100	[thread overview]
Message-ID: <CAHc6FU7R+mb3Eh11oOfvDVNg-Zsb-zE9CLEhr4yDKJKU5+ABHA@mail.gmail.com> (raw)
In-Reply-To: <20231213-drehen-einquartieren-56bbdda1177e@brauner>

On Wed, Dec 13, 2023 at 11:45 AM Christian Brauner <brauner@kernel.org> wrote:
> On Wed, Dec 13, 2023 at 02:35:58PM +0800, xingwei lee wrote:
> > Hello, I reproduced this bug with repro.c and repro.txt since it
> > relatively large please see
> > https://gist.github.com/xrivendell7/b3b804bbf6d8c9930b2ba22e2dfaa6e6
> >
> > Since this bug in the dashboard
> > https://syzkaller.appspot.com/bug?extid=0c64a8706d587f73409e use
> > kernel commit: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/log/?id=aed8aee11130a954356200afa3f1b8753e8a9482
> > kernel config: https://syzkaller.appspot.com/text?tag=KernelConfig&x=df91a3034fe3f122
> >
> > my repro.c use the seem config and it crash report like below, and
> > it’s almost can make sure it the same as bug reported by syzobt.
>
> Uh, can you reproduce this on mainline?
> I so far fail to even with your repro.

I regularly run afoul of not running "losetup -f" before these
reproducers and so they end up doing nothing; see here:

https://lore.kernel.org/all/CAHc6FU7b-BaBXrMR3UqbZGF3a_y=20TKkCNde1GvqbmN2-h1xw@mail.gmail.com/

Andreas


  parent reply	other threads:[~2023-12-13 15:10 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-13  6:35 [syzbot] [gfs2] WARNING in vfs_utimes xingwei lee
2023-12-13 10:38 ` Christian Brauner
2023-12-13 10:51   ` xingwei lee
2023-12-13 15:10   ` Andreas Gruenbacher [this message]
2024-12-03 14:44     ` WARNING in __folio_mark_dirty (2) Tetsuo Handa
2024-12-03 15:02       ` Jan Kara
2025-01-13  9:35         ` Tetsuo Handa
2025-01-13 11:52           ` Jan Kara
2025-01-13 13:06             ` Tetsuo Handa
2025-01-14 10:06               ` Jan Kara
  -- strict thread matches above, loose matches on Subject: below --
2023-12-11 11:58 [syzbot] [gfs2] WARNING in vfs_utimes 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=CAHc6FU7R+mb3Eh11oOfvDVNg-Zsb-zE9CLEhr4yDKJKU5+ABHA@mail.gmail.com \
    --to=agruenba@redhat.com \
    --cc=brauner@kernel.org \
    --cc=gfs2@lists.linux.dev \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=syzbot+0c64a8706d587f73409e@syzkaller.appspotmail.com \
    --cc=syzkaller-bugs@googlegroups.com \
    --cc=viro@zeniv.linux.org.uk \
    --cc=xrivendell7@gmail.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).