From: Amir Goldstein <amir73il@gmail.com>
To: Miklos Szeredi <miklos@szeredi.hu>
Cc: linux-unionfs@vger.kernel.org
Subject: [PATCH 0/4] Overlayfs aio cleanups
Date: Tue, 12 Sep 2023 20:36:49 +0300 [thread overview]
Message-ID: <20230912173653.3317828-1-amir73il@gmail.com> (raw)
Miklos,
Following are the cleanups and minor fixes I did in preparation for
factoring out of read/write passthrough code.
There are very minor fixes, which do not desreve backporting IMO.
The only meaningful fix (fd leak) was already merged to master.
I will send out the re-factoring patch separately to fsdevel, but
I've split those prep patches for lack of wider audience interest.
Thanks,
Amir.
Amir Goldstein (4):
ovl: protect copying of realinode attributes to ovl inode
ovl: use simpler function to convert iocb to rw flags
ovl: propagate IOCB_APPEND flag on writes to realfile
ovl: move ovl_file_accessed() to aio completion
fs/overlayfs/file.c | 75 +++++++++++++++++++++++++--------------------
fs/overlayfs/util.c | 2 ++
2 files changed, 44 insertions(+), 33 deletions(-)
--
2.34.1
next reply other threads:[~2023-09-12 17:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-12 17:36 Amir Goldstein [this message]
2023-09-12 17:36 ` [PATCH 1/4] ovl: protect copying of realinode attributes to ovl inode Amir Goldstein
2023-09-24 9:28 ` Amir Goldstein
2023-09-26 21:17 ` Amir Goldstein
2023-10-01 14:11 ` Amir Goldstein
2023-09-12 17:36 ` [PATCH 2/4] ovl: use simpler function to convert iocb to rw flags Amir Goldstein
2023-09-12 17:36 ` [PATCH 3/4] ovl: propagate IOCB_APPEND flag on writes to realfile Amir Goldstein
2023-09-12 17:36 ` [PATCH 4/4] ovl: move ovl_file_accessed() to aio completion Amir Goldstein
2023-09-28 5:11 ` 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=20230912173653.3317828-1-amir73il@gmail.com \
--to=amir73il@gmail.com \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).