From: Matthew Wilcox <willy@infradead.org>
To: Dmitry Vyukov <dvyukov@google.com>
Cc: syzbot <syzbot+2af3bc9585be7f23f290@syzkaller.appspotmail.com>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com, viro@zeniv.linux.org.uk
Subject: Re: [syzbot] WARNING in mark_buffer_dirty (4)
Date: Mon, 4 Jul 2022 15:17:37 +0100 [thread overview]
Message-ID: <YsL2gTVwHL0wFvmI@casper.infradead.org> (raw)
In-Reply-To: <CACT4Y+ZvK0Oxf=Hw7mznmFU=x_zCwC4Ev_Zxo2N0p79DNNi-jw@mail.gmail.com>
On Mon, Jul 04, 2022 at 03:13:13PM +0200, Dmitry Vyukov wrote:
> On Mon, 4 Jul 2022 at 12:56, Matthew Wilcox <willy@infradead.org> wrote:
> > It's clearly none of those commits. This is a bug in minix, afaict.
> > Judging by the earlier errors, I'd say that it tried to read something,
> > failed, then marked it dirty, at which point we hit an assertion that
> > you shouldn't mark a !uptodate buffer as dirty. Given that this is
> > minix, I have no interest in pursuing this bug further. Why is syzbot
> > even testing with minix?
>
> Shouldn't it? Why? It does not seem to depend on BROKEN.
There is no entry for minix in MAINTAINERS. Nobody cares about it.
next prev parent reply other threads:[~2022-07-04 14:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-04 10:22 [syzbot] WARNING in mark_buffer_dirty (4) syzbot
2022-07-04 10:56 ` Matthew Wilcox
2022-07-04 13:13 ` Dmitry Vyukov
2022-07-04 14:17 ` Matthew Wilcox [this message]
2022-07-05 7:59 ` Dmitry Vyukov
2022-08-21 12:10 ` [PATCH] fs: fix " Hawkins Jiawei
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=YsL2gTVwHL0wFvmI@casper.infradead.org \
--to=willy@infradead.org \
--cc=dvyukov@google.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=syzbot+2af3bc9585be7f23f290@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=viro@zeniv.linux.org.uk \
/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 NNTP newsgroup(s).