From: "Georg Müller" <georgmueller@gmx.net>
To: Miklos Szeredi <miklos@szeredi.hu>, linux-unionfs@vger.kernel.org
Subject: overlayfs: supporting O_TMPFILE
Date: Thu, 28 Oct 2021 22:41:45 +0200 [thread overview]
Message-ID: <951c68ed-3f0e-8d9b-6c10-690df778ecc2@gmx.net> (raw)
Hi,
I was trying to implement .tmpfile for overlayfs inode_operations to support O_TMPFILE.
Docker with aufs supports it, but this is deprecated and removed from current docker. I now have a work-around in my code (create tmpfile+unlink), but
I thought it might be a good idea to have tmpfile support in overlayfs.
I was trying to do it on my own, but I have some headaches to what is necessary to achieve the goal.
From my understanding, I have to find the dentry for the upper dir (or workdir) and call vfs_tmpdir() for this, but I am running from oops to oops.
Is there some hint what I have to do to achieve the goal?
Best regards,
Georg
next reply other threads:[~2021-10-28 20:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-28 20:41 Georg Müller [this message]
2021-10-28 22:37 ` overlayfs: supporting O_TMPFILE Amir Goldstein
2021-10-29 12:54 ` Miklos Szeredi
2021-10-29 13:47 ` Georg Müller
2021-10-29 15:16 ` Georg Müller
2022-04-19 14:01 ` Georg Müller
2022-04-20 8:21 ` Amir Goldstein
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=951c68ed-3f0e-8d9b-6c10-690df778ecc2@gmx.net \
--to=georgmueller@gmx.net \
--cc=linux-unionfs@vger.kernel.org \
--cc=miklos@szeredi.hu \
/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