linux-kernel - Re: [PATCH] fs/coda: remove static inline forward declarations

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]

Date:	Wed, 13 Feb 2008 08:43:53 -0500
From:	"linux-os (Dick Johnson)" <linux-os@...logic.com>
To:	Ilpo Järvinen <ilpo.jarvinen@...sinki.fi>
Cc:	<jaharkes@...cmu.edu>, "Andrew Morton" <akpm@...ux-foundation.org>,
	"LKML" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] fs/coda: remove static inline forward declarations

On Wed, 13 Feb 2008, [iso-8859-1] Ilpo Järvinen wrote:

> They're defined later on in the same file with bodies and
> nothingin between needs them.
>
> Signed-off-by: Ilpo Järvinen <ilpo.jarvinen@...sinki.fi>
> ---
> include/linux/coda_linux.h |    3 ---
> 1 files changed, 0 insertions(+), 3 deletions(-)
>
> diff --git a/include/linux/coda_linux.h b/include/linux/coda_linux.h
> index 1c47a34..31b7531 100644
> --- a/include/linux/coda_linux.h
> +++ b/include/linux/coda_linux.h
> @@ -43,9 +43,6 @@ int coda_getattr(struct vfsmount *, struct dentry *, struct kstat *);
> int coda_setattr(struct dentry *, struct iattr *);
>
> /* this file:  heloers */
> -static __inline__ struct CodaFid *coda_i2f(struct inode *);
> -static __inline__ char *coda_i2s(struct inode *);
> -static __inline__ void coda_flag_inode(struct inode *, int flag);
> char *coda_f2s(struct CodaFid *f);
> int coda_isroot(struct inode *i);
> int coda_iscontrol(const char *name, size_t length);
> -- 
> 1.5.2.2
>

I was taught formally that all procedures must be declared
before they are encountered in a file. This constitutes what
is generally known as "good standards of engineering practice."
It also guarantees a compiler diagnostic if the declaration and
the function doesn't match.

You should not remove things just because you don't think they
are necessary. They do no harm and removing them can cause
code checking tools to issue diagnostic messages.

Cheers,
Dick Johnson
Penguin : Linux version 2.6.22.1 on an i686 machine (5588.28 BogoMips).
My book : http://www.AbominableFirebug.com/
_

****************************************************************
The information transmitted in this message is confidential and may be privileged.  Any review, retransmission, dissemination, or other use of this information by persons or entities other than the intended recipient is prohibited.  If you are not the intended recipient, please notify Analogic Corporation immediately - by replying to this message or by sending an email to DeliveryErrors@...logic.com - and destroy all copies of this information, including any attachments, without reading or disclosing them.

Thank you.
--
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/