From: Thadeu Lima de Souza Cascardo <cascardo@igalia.com>
To: linux-ext4@vger.kernel.org
Cc: Theodore Ts'o <tytso@mit.edu>,
linux-kernel@vger.kernel.org, Tao Ma <boyu.mt@taobao.com>,
Andreas Dilger <adilger.kernel@dilger.ca>,
kernel-dev@igalia.com,
Thadeu Lima de Souza Cascardo <cascardo@igalia.com>
Subject: [PATCH 0/4] ext4: avoid OOB when system.data xattr changes underneath the filesystem
Date: Wed, 21 Aug 2024 12:23:20 -0300 [thread overview]
Message-ID: <20240821152324.3621860-1-cascardo@igalia.com> (raw)
This patchset changes some of the error paths involving dir entries lookups
and recheck that xattrs are valid after an inode is potentially reread from
disk.
Thadeu Lima de Souza Cascardo (4):
ext4: ext4_search_dir should return a proper error
ext4: return error on ext4_find_inline_entry
ext4: explicitly exit when ext4_find_inline_entry returns an error
ext4: avoid OOB when system.data xattr changes underneath the
filesystem
fs/ext4/inline.c | 35 +++++++++++++++++++++++++----------
fs/ext4/namei.c | 14 ++++++++------
2 files changed, 33 insertions(+), 16 deletions(-)
--
2.34.1
next reply other threads:[~2024-08-21 15:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-21 15:23 Thadeu Lima de Souza Cascardo [this message]
2024-08-21 15:23 ` [PATCH 1/4] ext4: ext4_search_dir should return a proper error Thadeu Lima de Souza Cascardo
2024-08-21 15:23 ` [PATCH 2/4] ext4: return error on ext4_find_inline_entry Thadeu Lima de Souza Cascardo
2024-08-21 15:23 ` [PATCH 3/4] ext4: explicitly exit when ext4_find_inline_entry returns an error Thadeu Lima de Souza Cascardo
2024-08-21 15:23 ` [PATCH 4/4] ext4: avoid OOB when system.data xattr changes underneath the filesystem Thadeu Lima de Souza Cascardo
2024-09-05 14:53 ` [PATCH 0/4] " Theodore Ts'o
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=20240821152324.3621860-1-cascardo@igalia.com \
--to=cascardo@igalia.com \
--cc=adilger.kernel@dilger.ca \
--cc=boyu.mt@taobao.com \
--cc=kernel-dev@igalia.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tytso@mit.edu \
/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®