linux-kernel - Re: [PATCH v2] fs.h: ifdef security fields

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]

Message-ID: <20060802191054.GA6825@martell.zuzino.mipt.ru>
Date:	Wed, 2 Aug 2006 23:10:54 +0400
From:	Alexey Dobriyan <adobriyan@...il.com>
To:	Stephen Smalley <sds@...ho.nsa.gov>
Cc:	Andrew Morton <akpm@...l.org>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2] fs.h: ifdef security fields

On Wed, Aug 02, 2006 at 12:53:05PM -0400, Stephen Smalley wrote:
> On Wed, 2006-08-02 at 19:14 +0400, Alexey Dobriyan wrote:
> > > > --- a/include/linux/fs.h
> > > > +++ b/include/linux/fs.h
> > > > @@ -552,7 +552,9 @@ struct inode {
> > > >  	unsigned int		i_flags;
> > > >
> > > >  	atomic_t		i_writecount;
> > > > +#ifdef CONFIG_SECURITY
> > > >  	void			*i_security;
> > > > +#endif
> > > >  	union {
> > > >  		void		*generic_ip;
> > > >  	} u;
> > > > @@ -688,8 +690,9 @@ struct file {
> > > >  	struct file_ra_state	f_ra;
> > > >
> > > >  	unsigned long		f_version;
> > > > +#ifdef CONFIG_SECURITY_SELINUX
> > >
> > > This should just be CONFIG_SECURITY.
> > 
> > After another user appear.
> 
> I see.  Well, if that's the rationale, I thought that seclvl was also
> scheduled for removal in 2.6.18 with the agreement of its maintainer, so
> that would also apply to i_security.

OK, I see seclvl removal patch has been sent and have found couple more
highly greppable fields: "security". :-) There will be bigger patch.

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