From: Amir Goldstein <amir73il@gmail.com>
To: Miklos Szeredi <miklos@szeredi.hu>
Cc: Jan Kara <jack@suse.cz>, linux-unionfs@vger.kernel.org
Subject: [PATCH v2 0/3] overlayfs lock ordering changes
Date: Mon, 14 Aug 2023 17:05:15 +0300 [thread overview]
Message-ID: <20230814140518.763674-1-amir73il@gmail.com> (raw)
Hi Miklos,
These patches are needed for my start-write-safe series [1].
I think that at least patch 3 fixes a real bug.
Thanks,
Amir.
Changes since v1:
- Breakup the large ovl_want_write() transaction in copy up
- Add fix to possible deadlock with encode lower ovl fh
[1] https://github.com/amir73il/linux/commits/start-write-safe
Amir Goldstein (3):
ovl: reorder ovl_want_write() after ovl_inode_lock()
ovl: do not open/llseek lower file with upper sb_writers held
ovl: do not encode lower fh with upper sb_writers held
fs/overlayfs/copy_up.c | 195 ++++++++++++++++++++++++++-------------
fs/overlayfs/dir.c | 71 +++++++-------
fs/overlayfs/export.c | 7 +-
fs/overlayfs/inode.c | 56 ++++++-----
fs/overlayfs/namei.c | 37 ++++++--
fs/overlayfs/overlayfs.h | 26 ++++--
fs/overlayfs/super.c | 20 ++--
fs/overlayfs/util.c | 16 ++++
8 files changed, 268 insertions(+), 160 deletions(-)
--
2.34.1
next reply other threads:[~2023-08-14 14:06 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-14 14:05 Amir Goldstein [this message]
2023-08-14 14:05 ` [PATCH v2 1/3] ovl: reorder ovl_want_write() after ovl_inode_lock() Amir Goldstein
2023-08-15 10:50 ` Miklos Szeredi
2023-08-15 15:12 ` Amir Goldstein
2023-08-14 14:05 ` [PATCH v2 2/3] ovl: do not open/llseek lower file with upper sb_writers held Amir Goldstein
2023-08-15 15:12 ` Miklos Szeredi
2023-08-15 15:59 ` Amir Goldstein
2023-08-15 19:07 ` Miklos Szeredi
2023-08-15 19:51 ` Amir Goldstein
2023-08-15 20:36 ` Miklos Szeredi
2023-08-16 10:28 ` Christian Brauner
2023-08-16 15:02 ` Amir Goldstein
2023-09-08 12:29 ` Amir Goldstein
2023-08-16 10:34 ` Christian Brauner
2023-08-14 14:05 ` [PATCH v2 3/3] ovl: do not encode lower fh " 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=20230814140518.763674-1-amir73il@gmail.com \
--to=amir73il@gmail.com \
--cc=jack@suse.cz \
--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).