From: "Darrick J. Wong" <djwong@kernel.org>
To: Luca Di Maio <luca.dimaio1@gmail.com>
Cc: linux-xfs@vger.kernel.org, dimitri.ledkov@chainguard.dev,
smoser@chainguard.dev, hch@infradead.org
Subject: Re: [PATCH v11 1/1] proto: add ability to populate a filesystem from a directory
Date: Wed, 30 Jul 2025 08:04:09 -0700 [thread overview]
Message-ID: <20250730150409.GG2672070@frogsfrogsfrogs> (raw)
In-Reply-To: <bowzj7lobz6tv73swiauishctrryozcwqmqyeqck65o2qjyt5v@vufmu67nwlkc>
On Wed, Jul 30, 2025 at 04:40:39PM +0200, Luca Di Maio wrote:
> Thanks Darrick for the review!
> Sorry again for this indentation mess, I'm going to basically align all
> function arguments and all the top-function declarations
> I was a bit confused because elsewhere in the code is not like that so
> it's a bit difficult to infere
>
> Offtopic: maybe we could also introduce an editorconfig setup? so that
> all various editors will be correctly set to see the tabs/spaces as
> needed (https://editorconfig.org/)
Hrmm, that /would/ be useful.
> Back on topic:
>
> On Tue, Jul 29, 2025 at 02:43:22PM -0700, Darrick J. Wong wrote:
<snipping>
> > > + if (!S_ISSOCK(file_stat.st_mode) &&
> > > + !S_ISLNK(file_stat.st_mode) &&
> > > + !S_ISFIFO(file_stat.st_mode)) {
> > > + close(fd);
> > > + fd = openat(pathfd, entry->d_name,
> > > + O_NOFOLLOW | O_RDONLY | O_NOATIME);
> >
> > Just out of curiosity, does O_NOATIME not work in the previous openat?
[narrator: it doesn't]
> Actually on my test setup (mainly using docker/podman to test), opening
> with and without O_NOATIME when using O_PATH, does not change accesstime
> checking with `stat`, but also it works if I add it.
> As a precautionary measure (not sure if podman/docker is messing with
> noatime) I'll add it, as it seems to work correctly.
On second thought I think you might leave the double opens because
O_NOATIME is only allowed if the current user owns source file, or has
CAP_FOWNER. If you're running mkfs as an unprivileged user trying to
capture a rootfs (with uid 0 files) then O_NOATIME won't be allowed.
Maybe something along the lines of:
/*
* Try to open the source file noatime to avoid a flood of
* writes to the source fs, but we can fall back to plain
* readonly mode if we don't have enough permission.
*/
fd = openat(pathfd, entry->d_name, O_NOFOLLOW | O_RDONLY | O_NOATIME);
if (fd < 0)
fd = openat(pathfd, entry->d_name, O_NOFOLLOW | O_RDONLY);
if (fd < 0)
/* whine and exit */
Just to see if you can open the source file without touching atime?
--D
> > > + * this will make flistxattr() and fgetxattr() fail wil EBADF,
> >
> > "fail with EBADF"...
> >
>
> Ack.
>
> > > + /*
> > > + * Copy over attributes.
> > > + */
> > > + writeattrs(ip, path_buf, fd);
> >
> > Nothing closes fd here; does it leak?
> >
> > --D
> >
>
> Ack.
>
> L.
next prev parent reply other threads:[~2025-07-30 15:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-28 15:29 [PATCH v11 0/1] mkfs: add ability to populate filesystem from directory Luca Di Maio
2025-07-28 15:29 ` [PATCH v11 1/1] proto: add ability to populate a filesystem from a directory Luca Di Maio
2025-07-29 21:43 ` Darrick J. Wong
2025-07-30 14:40 ` Luca Di Maio
2025-07-30 15:04 ` Darrick J. Wong [this message]
2025-07-30 15:20 ` Luca Di Maio
2025-07-30 15:26 ` Darrick J. Wong
2025-07-30 15:42 ` Luca Di Maio
2025-08-08 11:55 ` Andrey Albershteyn
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=20250730150409.GG2672070@frogsfrogsfrogs \
--to=djwong@kernel.org \
--cc=dimitri.ledkov@chainguard.dev \
--cc=hch@infradead.org \
--cc=linux-xfs@vger.kernel.org \
--cc=luca.dimaio1@gmail.com \
--cc=smoser@chainguard.dev \
/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