From: Roman Smirnov <r.smirnov@omp.ru>
To: "stable@vger.kernel.org" <stable@vger.kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Ryusuke Konishi <konishi.ryusuke@gmail.com>,
"linux-nilfs@vger.kernel.org" <linux-nilfs@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Alexey Khoroshilov <khoroshilov@ispras.ru>,
"lvc-project@linuxtesting.org" <lvc-project@linuxtesting.org>,
"Sergey Shtylyov" <s.shtylyov@omp.ru>,
Karina Yankevich <k.yankevich@omp.ru>,
"Andrey Rusalin" <a.rusalin@omp.ru>,
Sergey Yudin <s.yudin@omp.ru>,
"Valentin Perevozchikov" <v.perevozchikov@omp.ru>
Subject: Re: [PATCH 5.10/5.15/6.1 0/1] nilfs2: fix WARNING in nilfs_dat_prepare_end()
Date: Tue, 20 Feb 2024 08:44:02 +0000 [thread overview]
Message-ID: <5abcb44deb604258aff4cd02c3ca90a3@omp.ru> (raw)
In-Reply-To: <20240208144224.438146-1-r.smirnov@omp.ru>
On Thu, 8 Feb 2024 17:42:41 +0300, Roman Smirnov wrote:
> Syzkaller reports WARNING in nilfs_dat_prepare_end() in 5.10, 5.15 and 6.1
> stable releases. The problem has been fixed in upstream:
> https://syzkaller.appspot.com/bug?extid=5d5d25f90f195a3cfcb4
>
> The problem can also be fixed in versions 5.10, 5.15 and 6.1 by the
> following patch.
>
> Found by Linux Verification Center (linuxtesting.org) with Syzkaller.
>
> Link: https://syzkaller.appspot.com/bug?extid=325e6b0a1e7cf9035cc0
> Link: https://syzkaller.appspot.com/bug?extid=bebf30d67ea2569f0fd3
>
> Ryusuke Konishi (1):
> nilfs2: replace WARN_ONs for invalid DAT metadata block requests
>
> fs/nilfs2/dat.c | 27 +++++++++++++++++----------
> 1 file changed, 17 insertions(+), 10 deletions(-)
Sorry to bother you, do you have any comments on the patch?
next prev parent reply other threads:[~2024-02-20 8:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-08 14:42 [PATCH 5.10/5.15/6.1 0/1] nilfs2: fix WARNING in nilfs_dat_prepare_end() Roman Smirnov
2024-02-08 14:42 ` [PATCH 5.10/5.15/6.1 1/1] nilfs2: replace WARN_ONs for invalid DAT metadata block requests Roman Smirnov
2024-02-20 8:44 ` Roman Smirnov [this message]
2024-02-20 14:09 ` [PATCH 5.10/5.15/6.1 0/1] nilfs2: fix WARNING in nilfs_dat_prepare_end() Ryusuke Konishi
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=5abcb44deb604258aff4cd02c3ca90a3@omp.ru \
--to=r.smirnov@omp.ru \
--cc=a.rusalin@omp.ru \
--cc=gregkh@linuxfoundation.org \
--cc=k.yankevich@omp.ru \
--cc=khoroshilov@ispras.ru \
--cc=konishi.ryusuke@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nilfs@vger.kernel.org \
--cc=lvc-project@linuxtesting.org \
--cc=s.shtylyov@omp.ru \
--cc=s.yudin@omp.ru \
--cc=stable@vger.kernel.org \
--cc=v.perevozchikov@omp.ru \
/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.