linux-kernel - Re: [RFC v3 33/45] nfsd: Keep list of acls to dispose of in compoundargs

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAHpGcMJ1-EXQx8dxm=G4aXUkbTFDaMLFuxb33bY+tPt4_6TWBg@mail.gmail.com>
Date:	Thu, 28 May 2015 22:28:13 +0200
From:	Andreas Grünbacher <andreas.gruenbacher@...il.com>
To:	"J. Bruce Fields" <bfields@...ldses.org>
Cc:	linux-kernel@...r.kernel.org, linux-fsdevel@...r.kernel.org,
	linux-nfs@...r.kernel.org
Subject: Re: [RFC v3 33/45] nfsd: Keep list of acls to dispose of in compoundargs

2015-05-28 21:52 GMT+02:00 J. Bruce Fields <bfields@...ldses.org>:
> On Fri, Apr 24, 2015 at 01:04:30PM +0200, Andreas Gruenbacher wrote:
>> We will decode acls in requests into richacls; those need to be richacl_put()
>> at the end of the request instead of kfree()d; this allows the vfs to cache
>> them whenever possible.
>>
>> NOTE: If we allow only a single acl per request, we can get rid of the list
>> here.
>
> Technically I guess we're supposed to allow it, and maybe someday
> someone will come up with a reason....  So I'm not inclined to drop the
> list.

Okay, I'll update the comment accordingly.

Thanks,
Andreas
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/