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: <CACT4Y+bUtBuhD7_BAN+NavEfhBNOavqF0CJkrZ+Gc4pYeLiy+g@mail.gmail.com>
Date:   Tue, 5 Jul 2022 09:59:24 +0200
From:   Dmitry Vyukov <dvyukov@...gle.com>
To:     Matthew Wilcox <willy@...radead.org>
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,
        syzkaller <syzkaller@...glegroups.com>
Subject: Re: [syzbot] WARNING in mark_buffer_dirty (4)

On Mon, 4 Jul 2022 at 16:17, Matthew Wilcox <willy@...radead.org> wrote:
>
> 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.

Humm... but it is also enabled in real distros (debian, ubuntu, my
current one) and 32 kernel defconfigs...
Subject to auto-mounting when anything is inserted into usb, right?

In this situation it's good to test it at least to know the state.
Otherwise few kernel devs may know it's broken and unmaintained, but
the rest of the world assumes it's all good and solid and happily
enables it :)