From: Sascha Hauer <s.hauer@pengutronix.de>
To: BAREBOX <barebox@lists.infradead.org>,
Sascha Hauer <s.hauer@pengutronix.de>
Subject: Re: [PATCH 0/2] fs: reject inodes whose size the superblock cannot address
Date: Fri, 11 Sep 2026 16:04:20 +0200 [thread overview]
Message-ID: <178913546026.2420551.13685534641272061556.b4-ty@pengutronix.de> (raw)
In-Reply-To: <20260908-fs-filesize-fixes-v1-0-8cf3e781a4d0@pengutronix.de>
On Tue, 08 Sep 2026 10:32:08 +0200, Sascha Hauer wrote:
> 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.
>
> [...]
Applied, thanks!
[1/2] fs: track streaming and unknown-size files in dedicated inode fields
https://git.pengutronix.de/cgit/barebox/commit/?id=260a4c6af4e3 (link may not be stable)
[2/2] fs: reject inodes whose size the superblock cannot address
https://git.pengutronix.de/cgit/barebox/commit/?id=b37ad309e6ca (link may not be stable)
Best regards,
--
Sascha Hauer <s.hauer@pengutronix.de>
prev parent reply other threads:[~2026-09-11 14:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-08 8:32 Sascha Hauer
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
2026-09-11 14:04 ` Sascha Hauer [this message]
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=178913546026.2420551.13685534641272061556.b4-ty@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