linux-kernel - Re: [syzbot] WARNING in mark_buffer

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <YsL2gTVwHL0wFvmI@casper.infradead.org>
Date:   Mon, 4 Jul 2022 15:17:37 +0100
From:   Matthew Wilcox <willy@...radead.org>
To:     Dmitry Vyukov <dvyukov@...gle.com>
Cc:     syzbot <syzbot+2af3bc9585be7f23f290@...kaller.appspotmail.com>,
        linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org,
        syzkaller-bugs@...glegroups.com, viro@...iv.linux.org.uk
Subject: Re: [syzbot] WARNING in mark_buffer_dirty (4)

On Mon, Jul 04, 2022 at 03:13:13PM +0200, Dmitry Vyukov wrote:
> On Mon, 4 Jul 2022 at 12:56, Matthew Wilcox <willy@...radead.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.