linux-kernel - Re: [PATCH 5/5][NFS] Cleanup explicit check for mandatory 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:	Tue, 18 Sep 2007 09:27:15 -0400
From:	Trond Myklebust <trond.myklebust@....uio.no>
To:	Pavel Emelyanov <xemul@...nvz.org>
Cc:	Andrew Morton <akpm@...l.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	devel@...nvz.org
Subject: Re: [PATCH 5/5][NFS] Cleanup explicit check for mandatory locks

On Tue, 2007-09-18 at 10:20 +0400, Pavel Emelyanov wrote:
> Trond Myklebust wrote:
> > On Mon, 2007-09-17 at 11:57 +0400, Pavel Emelyanov wrote:
> >> The __mandatory_lock(inode) macro makes the same check, but
> >> makes the code more readable.
> > 
> > Could we please avoid using underscores in macros. Also, why are we
> > breaking the usual convention of capitalising macro names?
> 
> Sorry, I've forgot to change all the log - this is not a macro, 
> but a static inline function. The underscores are here, because 
> the mandatory_lock() one already exists and additionally checks 
> for "if (IS_MANDLOCK(inode))"

OK. I withdraw my objection then.

Cheers
  Trond

-
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/