From: Trond Myklebust <trondmy@hammerspace.com>
To: "agruenba@redhat.com" <agruenba@redhat.com>
Cc: "okir@suse.de" <okir@suse.de>,
"tanxin.ctf@gmail.com" <tanxin.ctf@gmail.com>,
"xiyuyang19@fudan.edu.cn" <xiyuyang19@fudan.edu.cn>,
"akpm@osdl.org" <akpm@osdl.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>,
"anna.schumaker@netapp.com" <anna.schumaker@netapp.com>,
"kjlu@umn.edu" <kjlu@umn.edu>,
"yuanxzhang@fudan.edu.cn" <yuanxzhang@fudan.edu.cn>
Subject: Re: [PATCH] nfs: Fix potential posix_acl refcnt leak in nfs3_set_acl
Date: Mon, 20 Apr 2020 13:13:43 +0000 [thread overview]
Message-ID: <c19f1a6ac3664dca12706400dc425538ccf8f101.camel@hammerspace.com> (raw)
In-Reply-To: <CAHc6FU411Eoo_E=aQiR=Vk2Tx6XCZEuiz25NykWY+dd5wKrszg@mail.gmail.com>
On Mon, 2020-04-20 at 15:04 +0200, Andreas Gruenbacher wrote:
> On Mon, Apr 20, 2020 at 2:59 PM Trond Myklebust <
> trondmy@hammerspace.com> wrote:
> > Well, that should Oops when either IS_ERR(acl) or IS_ERR(dfacl)
> > triggers, shouldn't it?
>
> Yes, checks missings. But you get the idea.
>
Fair enough 🙂
Can I expect an official patch from either you or the original
submitters?
--
Trond Myklebust
Linux NFS client maintainer, Hammerspace
trond.myklebust@hammerspace.com
next prev parent reply other threads:[~2020-04-20 13:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-20 5:43 Xiyu Yang
2020-04-20 12:14 ` Trond Myklebust
2020-04-20 12:51 ` Andreas Gruenbacher
2020-04-20 12:59 ` Trond Myklebust
2020-04-20 13:04 ` Andreas Gruenbacher
2020-04-20 13:13 ` Trond Myklebust [this message]
2020-04-20 13:51 Andreas Gruenbacher
2020-04-20 14:13 ` Trond Myklebust
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=c19f1a6ac3664dca12706400dc425538ccf8f101.camel@hammerspace.com \
--to=trondmy@hammerspace.com \
--cc=agruenba@redhat.com \
--cc=akpm@osdl.org \
--cc=anna.schumaker@netapp.com \
--cc=kjlu@umn.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=okir@suse.de \
--cc=tanxin.ctf@gmail.com \
--cc=xiyuyang19@fudan.edu.cn \
--cc=yuanxzhang@fudan.edu.cn \
/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®