From: Al Viro <viro@zeniv.linux.org.uk>
To: Farhad Alemi <farhad.alemi@berkeley.edu>
Cc: Kees Cook <kees@kernel.org>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [BUG] ufs: UBSAN shift-out-of-bounds in ufs_fill_super() at fs/ufs/super.c:1181
Date: Tue, 26 May 2026 23:49:56 +0100 [thread overview]
Message-ID: <20260526224956.GF2636677@ZenIV> (raw)
In-Reply-To: <CA+0ovCg9e3_2jyM7x67A2rp8E=BR2gLX1FBZHyXdctFAhcG+qg@mail.gmail.com>
On Tue, May 26, 2026 at 02:47:30PM -0700, Farhad Alemi wrote:
> Hello Al and the linux-fsdevel team,
>
> I am reporting a UFS crash found by syzkaller. fs/ufs has no named
> M: entry in MAINTAINERS, so I'm routing by commit-history affinity.
Same comment as for your previous report, really. I'll resurrect
an old patch adding sanity checks to ufs_fill_super() (rejecting the
same things BSD does), will Cc you when it's posted. Might be a week
or so, though - plenty of shit on my platter at the moment.
next prev parent reply other threads:[~2026-05-26 22:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-26 21:47 [BUG] ufs: UBSAN shift-out-of-bounds in ufs_fill_super() at fs/ufs/super.c:1181 Farhad Alemi
2026-05-26 22:49 ` Al Viro [this message]
2026-05-26 23:02 ` Farhad Alemi
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=20260526224956.GF2636677@ZenIV \
--to=viro@zeniv.linux.org.uk \
--cc=farhad.alemi@berkeley.edu \
--cc=kees@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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.