[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <161410140523.3588113.12183751046979550289.b4-ty@chromium.org>
Date: Tue, 23 Feb 2021 09:30:11 -0800
From: Kees Cook <keescook@...omium.org>
To: Anton Vorontsov <anton@...msg.org>,
Tetsuo Handa <penguin-kernel@...ove.SAKURA.ne.jp>,
Colin Cross <ccross@...roid.com>,
Tony Luck <tony.luck@...el.com>
Cc: Kees Cook <keescook@...omium.org>, linux-kernel@...r.kernel.org,
syzbot <syzbot+d0cf0ad6513e9a1da5df@...kaller.appspotmail.com>
Subject: Re: [PATCH] pstore: fix warning in pstore_kill_sb()
On Sun, 14 Feb 2021 12:13:07 +0900, Tetsuo Handa wrote:
> syzbot is hitting WARN_ON(pstore_sb != sb) at pstore_kill_sb() [1], for the
> assumption that pstore_sb != NULL is wrong because pstore_fill_super() will
> not assign pstore_sb = sb when new_inode() for d_make_root() returned NULL
> (due to memory allocation fault injection).
>
> Since mount_single() calls pstore_kill_sb() when pstore_fill_super()
> failed, pstore_kill_sb() needs to be aware of such failure path.
>
> [...]
Applied to for-next/pstore, thanks!
[1/1] pstore: Fix warning in pstore_kill_sb()
https://git.kernel.org/kees/c/9c7d83ae6ba6
--
Kees Cook
Powered by blists - more mailing lists