mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Sascha Hauer <s.hauer@pengutronix.de>
To: BAREBOX <barebox@lists.infradead.org>
Subject: [PATCH 0/2] fs: reject inodes whose size the superblock cannot address
Date: Tue, 08 Sep 2026 10:32:08 +0200	[thread overview]
Message-ID: <20260908-fs-filesize-fixes-v1-0-8cf3e781a4d0@pengutronix.de> (raw)

This is a continuation of the patch previously sent as a single patch.

Additionally I added a patch cleaning up the FILE_SIZE_STREAM disambiguity.
The problem is that we overloaded the inode size with a flag indicating
that the inode belongs to a stream with undefined file size. The new
patch solves this by adding extra flags to struct inode.

Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
---
Sascha Hauer (2):
      fs: track streaming and unknown-size files in dedicated inode fields
      fs: reject inodes whose size the superblock cannot address

 fs/devfs.c         |  7 ++++++-
 fs/fs.c            | 37 +++++++++++++++++++++++++++++++++----
 fs/tftp.c          |  2 +-
 include/linux/fs.h |  2 ++
 4 files changed, 42 insertions(+), 6 deletions(-)
---
base-commit: 42e510a258d7c276c35f06c103e685c80d376eab
change-id: 20260908-fs-filesize-fixes-2f932f665027

Best regards,
-- 
Sascha Hauer <s.hauer@pengutronix.de>




             reply	other threads:[~2026-09-08  8:33 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-08  8:32 Sascha Hauer [this message]
2026-09-08  8:32 ` [PATCH 1/2] fs: track streaming and unknown-size files in dedicated inode fields Sascha Hauer
2026-09-08  8:50   ` Ahmad Fatoum
2026-09-08  8:32 ` [PATCH 2/2] fs: reject inodes whose size the superblock cannot address Sascha Hauer
2026-09-08  8:55   ` Ahmad Fatoum

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=20260908-fs-filesize-fixes-v1-0-8cf3e781a4d0@pengutronix.de \
    --to=s.hauer@pengutronix.de \
    --cc=barebox@lists.infradead.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