From: James Simmons <jsimmons@infradead.org>
To: "Andreas Grünbacher" <andreas.gruenbacher@gmail.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
devel@driverdev.osuosl.org,
Andreas Dilger <andreas.dilger@intel.com>,
Oleg Drokin <oleg.drokin@intel.com>,
Andreas Gruenbacher <agruenba@redhat.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Lustre Development List <lustre-devel@lists.lustre.org>
Subject: Re: [PATCH] staging: lustre: llite: drop acl from cache
Date: Tue, 24 May 2016 21:38:19 +0100 (BST) [thread overview]
Message-ID: <alpine.LFD.2.20.1605242135500.4622@casper.infradead.org> (raw)
In-Reply-To: <CAHpGcMJtzz4MYcRKkG-ybKgDArchQ_CFOtFjpJ8axe8Ls2G7rw@mail.gmail.com>
> 2016-05-24 2:35 GMT+02:00 James Simmons <jsimmons@infradead.org>:
> > Commit b8a7a3a6 change get_acl() for posix xattr to always cache
> > the ACL which increases the reference count. That reference count
> > can be reduced by have ll_get_acl() call forget_cached_acl() which
> > it wasn't. When an inode gets deleted by Lustre the POSIX ACL
> > reference count is tested to ensure its 1 and if not produces an error.
>
> Lustre shouldn't assume that the VFS immediately drops the reference
> it is passed. Please remove that check as well.
The piece of code in question from ll_delete_inode() is
#ifdef CONFIG_FS_POSIX_ACL
else if (lli->lli_posix_acl) {
LASSERT(atomic_read(&lli->lli_posix_acl->a_refcount) ==
1);
LASSERT(!lli->lli_remote_perms);
posix_acl_release(lli->lli_posix_acl);
lli->lli_posix_acl = NULL;
}
#endif
So we want to prevent a leak should I do a
while (atomic_read(&lli->lli_posix_acl->a_refcount))
posix_acl_release(lli->lli_posix_acl);
lli->lli_posix_acl = NULL;
Or does the VFS do this cleanup for us?
> > Since forget_cached_acl() was not called Lustre started to complain.
> > This patch changes ll_get_acl() to call forget_cached_acl().
> >
> > Signed-off-by: James Simmons <jsimmons@infradead.org>
>
> Reviewed-by: Andreas Gruenbacher <agruenba@redhat.com>
>
> > ---
> > drivers/staging/lustre/lustre/llite/file.c | 1 +
> > 1 files changed, 1 insertions(+), 0 deletions(-)
> >
> > diff --git a/drivers/staging/lustre/lustre/llite/file.c b/drivers/staging/lustre/lustre/llite/file.c
> > index f47f2ac..0191945 100644
> > --- a/drivers/staging/lustre/lustre/llite/file.c
> > +++ b/drivers/staging/lustre/lustre/llite/file.c
> > @@ -3124,6 +3124,7 @@ struct posix_acl *ll_get_acl(struct inode *inode, int type)
> > spin_lock(&lli->lli_lock);
> > /* VFS' acl_permission_check->check_acl will release the refcount */
> > acl = posix_acl_dup(lli->lli_posix_acl);
> > + forget_cached_acl(inode, type);
> > spin_unlock(&lli->lli_lock);
> >
> > return acl;
> > --
> > 1.7.1
> >
>
next prev parent reply other threads:[~2016-05-24 20:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-24 0:35 James Simmons
2016-05-24 2:08 ` Andreas Grünbacher
2016-05-24 20:38 ` James Simmons [this message]
2016-05-24 22:08 ` Andreas Gruenbacher
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=alpine.LFD.2.20.1605242135500.4622@casper.infradead.org \
--to=jsimmons@infradead.org \
--cc=agruenba@redhat.com \
--cc=andreas.dilger@intel.com \
--cc=andreas.gruenbacher@gmail.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lustre-devel@lists.lustre.org \
--cc=oleg.drokin@intel.com \
/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
all inboxes | Powered by JetHome®