linux-kernel - Re: should we change the name/macros of file-private locks?

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] [day] [month] [year] [list]

Date:	Thu, 17 Apr 2014 19:47:48 -0400
From:	Jeff Layton <jlayton@...hat.com>
To:	mtk.manpages@...il.com
Cc:	"Stefan (metze) Metzmacher" <metze@...ba.org>,
	libc-alpha <libc-alpha@...rceware.org>,
	Michael Kerrisk-manpages <mtk.manpages@...glemail.com>,
	"Carlos O'Donell" <carlos@...hat.com>,
	samba-technical@...ts.samba.org,
	lkml <linux-kernel@...r.kernel.org>,
	Jeremy Allison <jra@...gle.com>,
	"linux-fsdevel@...r.kernel.org" <linux-fsdevel@...r.kernel.org>,
	Ganesha NFS List <nfs-ganesha-devel@...ts.sourceforge.net>
Subject: Re: should we change the name/macros of file-private locks?

On Thu, 17 Apr 2014 22:08:54 +0200
"Michael Kerrisk (man-pages)" <mtk.manpages@...il.com> wrote:

> >> In the docs we could take pains to point out that these are
> >> file-_description_ locks and not file-_descriptor_ locks, and outline
> >> why that is so (which is something I'm trying to make crystal clear in
> >> the docs anyway).
> >>
> >> Does anyone object to that?
> >
> > Well, I'd be silly to object, but maybe we should still allow a day
> > for further comment?
> 
> Jeff,
> 
> One further point. I know the intent is to get this scheme into POSIX.
> Have any conversations happened about this so far on the POSIX/Austin
> lists? If yes, it might be worth also linking those folks into the
> naming discussion..
> 
> Cheers,
> 
> Michael

Yes, good idea. The open bug is here:

    http://austingroupbugs.net/view.php?id=768

I'll write something up there and see if they want to chime in on the
discussion.

-- 
Jeff Layton <jlayton@...hat.com>
--
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/