linux-kernel - Re: [PATCH] make INIT_FS use the __RW_LOCK

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: <alpine.DEB.1.10.0812102010100.29200@gandalf.stny.rr.com>
Date:	Wed, 10 Dec 2008 20:11:02 -0500 (EST)
From:	Steven Rostedt <rostedt@...dmis.org>
To:	Mike Frysinger <vapier.adi@...il.com>
cc:	Al Viro <viro@...iv.linux.org.uk>,
	LKML <linux-kernel@...r.kernel.org>, linux-arch@...r.kernel.org,
	Andrew Morton <akpm@...ux-foundation.org>,
	Ingo Molnar <mingo@...e.hu>,
	Thomas Gleixner <tglx@...utronix.de>
Subject: Re: [PATCH] make INIT_FS use the __RW_LOCK_UNLOCKED initialization


On Wed, 10 Dec 2008, Mike Frysinger wrote:

> On Wed, Dec 10, 2008 at 18:43, Al Viro wrote:
> > On Wed, Dec 10, 2008 at 06:37:28PM -0500, Steven Rostedt wrote:
> >>
> >> The following patch is in:
> >>
> >>   git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-2.6-trace.git
> >>
> >>     branch: cleanups
> >
> > Would be better to take init_fs to something in fs/ or kernel/ and kill
> > the duplicates, along with INIT_FS macro itself...
> 
> how about the next level: unify init_task.c.  a quick check shows that
> like 90% of the stuff in there is the same for everyone ...
> -mike

I could probably do it for x86 and PPC, but beyond that, each arch 
maintainer will have to do it separately. That's a change that would need 
testing.

These changes are trivial (something I need to get RT working).

-- Steve

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