linux-unionfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Amir Goldstein <amir73il@gmail.com>
To: Miklos Szeredi <miklos@szeredi.hu>
Cc: linux-unionfs@vger.kernel.org
Subject: [PATCH 0/2] Overlay inode lock cleanups
Date: Thu, 18 Oct 2018 18:37:12 +0300	[thread overview]
Message-ID: <20181018153714.3834-1-amir73il@gmail.com> (raw)

Miklos,

First patch removes pretty big ugliness.
Second patch is just a matter of taste, so as you wish.

I'll use this opportunity to recap the queue of my proposed patches for
v4.20, so you can see if you missed to consider any of them:

* 5401b99fcbb9 - (overlayfs-devel) ovl: abstract ovl_inode lock with a helper
* 8edcbcef4e55 - ovl: remove the 'locked' argument of ovl_nlink_{start,end}
* bd2ea818ecca - ovl: relax requirement for non null uuid of lower fs
* 19c221c3a6b5 - ovl: disable new features for deprecated upper fs
* 1c785e83823c - ovl: untangle copy up call chain
* b67871490628 - (ovl-fixes) ovl: fix recursive oi->lock in ovl_link()
* e39a0eb89ae4 - vfs: fix FIGETBSZ ioctl on an overlayfs file
* 431d5170b91d - ovl: fix error handling in ovl_verify_set_fh()
* 388b00daecb8 - kernel/acct.c: fix locking order when switching acct files

Thanks,
Amir.

Amir Goldstein (2):
  ovl: remove the 'locked' argument of ovl_nlink_{start,end}
  ovl: abstract ovl_inode lock with a helper

 fs/overlayfs/dir.c       | 21 ++++++++++----------
 fs/overlayfs/overlayfs.h | 14 +++++++++++--
 fs/overlayfs/util.c      | 43 +++++++++++++++++++---------------------
 3 files changed, 43 insertions(+), 35 deletions(-)

-- 
2.17.1

             reply	other threads:[~2018-10-18 15:37 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-18 15:37 Amir Goldstein [this message]
2018-10-18 15:37 ` [PATCH 1/2] ovl: remove the 'locked' argument of ovl_nlink_{start,end} Amir Goldstein
2018-10-18 15:37 ` [PATCH 2/2] ovl: abstract ovl_inode lock with a helper Amir Goldstein
2018-10-26 21:55 ` [PATCH 0/2] Overlay inode lock cleanups Miklos Szeredi
2018-10-29 20:38   ` 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=20181018153714.3834-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 NNTP newsgroup(s).