From: kovalev@altlinux.org
To: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
aivazian.tigran@gmail.com, stable@vger.kernel.org
Cc: lvc-patches@linuxtesting.org, dutyrok@altlinux.org, kovalev@altlinux.org
Subject: [PATCH fs/bfs 0/2] bfs: fix null-ptr-deref and possible warning in bfs_move_block() func
Date: Wed, 10 Jul 2024 22:11:16 +0300 [thread overview]
Message-ID: <20240710191118.40431-1-kovalev@altlinux.org> (raw)
https://syzkaller.appspot.com/bug?extid=d98fd19acd08b36ff422
[PATCH fs/bfs 1/2] bfs: fix null-ptr-deref in bfs_move_block
[PATCH fs/bfs 2/2] bfs: add buffer_uptodate check before mark_buffer_dirty
next reply other threads:[~2024-07-10 19:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-10 19:11 kovalev [this message]
2024-07-10 19:11 ` [PATCH fs/bfs 1/2] bfs: fix null-ptr-deref in bfs_move_block kovalev
2024-07-10 20:09 ` Markus Elfring
2024-07-10 21:57 ` Василий Ковалев
2024-07-11 6:00 ` [fs/bfs " Markus Elfring
2024-07-11 16:40 ` [PATCH fs/bfs " kernel test robot
2024-07-10 19:11 ` [PATCH fs/bfs 2/2] bfs: add buffer_uptodate check before mark_buffer_dirty call kovalev
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=20240710191118.40431-1-kovalev@altlinux.org \
--to=kovalev@altlinux.org \
--cc=aivazian.tigran@gmail.com \
--cc=dutyrok@altlinux.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lvc-patches@linuxtesting.org \
--cc=stable@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox