From: Christian Brauner <brauner@kernel.org>
To: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
Cc: Christian Brauner <brauner@kernel.org>,
syzbot <syzbot+e2787430e752a92b8750@syzkaller.appspotmail.com>,
linux-fsdevel@vger.kernel.org, syzkaller-bugs@googlegroups.com,
syzbot <syzbot+4913dca2ea6e4d43f3f1@syzkaller.appspotmail.com>,
Al Viro <viro@zeniv.linux.org.uk>,
damien.lemoal@opensource.wdc.com, jlayton@kernel.org,
willy@infradead.org
Subject: Re: [PATCH] fs: hfsplus: remove WARN_ON() from hfsplus_cat_{read,write}_inode()
Date: Wed, 12 Apr 2023 11:38:55 +0200 [thread overview]
Message-ID: <20230412-driften-aufsagen-cb1c5b9d2ca9@brauner> (raw)
In-Reply-To: <15308173-5252-d6a3-ae3b-e96d46cb6f41@I-love.SAKURA.ne.jp>
On Tue, 11 Apr 2023 19:57:33 +0900, Tetsuo Handa wrote:
> syzbot is hitting WARN_ON() in hfsplus_cat_{read,write}_inode(), for
> crafted filesystem image can contain bogus length. There conditions are
> not kernel bugs that can justify kernel to panic.
>
>
Seems fine as a follow-up fix to Arnd's in
55d1cbbbb29e ("hfs/hfsplus: use WARN_ON for sanity check").
Filesystems is orphaned so taking this through one of our vfs trees,
branch: fs.misc
[1/1] fs: hfsplus: remove WARN_ON() from hfsplus_cat_{read,write}_inode()
commit: 81b21c0f0138ff5a499eafc3eb0578ad2a99622c
prev parent reply other threads:[~2023-04-12 9:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-01 12:49 [syzbot] WARNING in hfsplus_cat_read_inode syzbot
2023-04-11 10:57 ` [PATCH] fs: hfsplus: remove WARN_ON() from hfsplus_cat_{read,write}_inode() Tetsuo Handa
2023-04-11 18:44 ` [PATCH] " Viacheslav Dubeyko
2023-04-12 9:38 ` Christian Brauner [this message]
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=20230412-driften-aufsagen-cb1c5b9d2ca9@brauner \
--to=brauner@kernel.org \
--cc=damien.lemoal@opensource.wdc.com \
--cc=jlayton@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=penguin-kernel@I-love.SAKURA.ne.jp \
--cc=syzbot+4913dca2ea6e4d43f3f1@syzkaller.appspotmail.com \
--cc=syzbot+e2787430e752a92b8750@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=viro@zeniv.linux.org.uk \
--cc=willy@infradead.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.