mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ryusuke Konishi <konishi.ryusuke@gmail.com>
To: Viacheslav Dubeyko <slava@dubeyko.com>
Cc: linux-nilfs <linux-nilfs@vger.kernel.org>,
	LKML <linux-kernel@vger.kernel.org>,
	Jake Labelle <southampton.jake.labelle@gmail.com>
Subject: [PATCH 0/2] nilfs2: robustness fixes from Jake Labelle
Date: Thu,  8 Oct 2026 20:52:46 +0900	[thread overview]
Message-ID: <20261008115312.18482-1-konishi.ryusuke@gmail.com> (raw)

Hi Viacheslav,

Please add the following two commits from Jake Labelle to your queue
for the next cycle.

As this cycle is getting closer to its end, I am sending these ahead with
a minor fix applied.  If Jake responds with further comments or revised
proposals later, we can discuss them as needed.

These patches address two robustness issues:

- Patch 1/2 rejects special inodes during dsync recovery to prevent
  dereferencing uninitialized bmap function pointers.
- Patch 2/2 validates and snaps the directory position after llseek in
  nilfs_readdir() to prevent invalid or out-of-bounds page reads.

For full context and background details, please refer to the original
cover letter here:

https://lore.kernel.org/all/20260930000954.371774-1-southampton.jake.labelle@gmail.com

Thanks,
Ryusuke Konishi

Jake Labelle (2):
  nilfs2: reject non-regular inodes in dsync recovery
  nilfs2: validate directory position after llseek in readdir

 fs/nilfs2/dir.c      | 34 ++++++++++++++++++++++++++++++++++
 fs/nilfs2/recovery.c | 17 +++++++++++++++++
 2 files changed, 51 insertions(+)

-- 
2.53.0


             reply	other threads:[~2026-10-08 11:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-08 11:52 Ryusuke Konishi [this message]
2026-10-08 11:52 ` [PATCH 1/2] nilfs2: reject non-regular inodes in dsync recovery Ryusuke Konishi
2026-10-08 11:52 ` [PATCH 2/2] nilfs2: validate directory position after llseek in readdir Ryusuke Konishi
2026-10-08 16:41 ` [PATCH 0/2] nilfs2: robustness fixes from Jake Labelle Viacheslav Dubeyko

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=20261008115312.18482-1-konishi.ryusuke@gmail.com \
    --to=konishi.ryusuke@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nilfs@vger.kernel.org \
    --cc=slava@dubeyko.com \
    --cc=southampton.jake.labelle@gmail.com \
    /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

all inboxes | Powered by JetHome®