linux-kernel - Re: [RFC 1/8] locking: Move mutex into kernel/locking/

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: <20131105212029.GT28601@twins.programming.kicks-ass.net>
Date:	Tue, 5 Nov 2013 22:20:29 +0100
From:	Peter Zijlstra <peterz@...radead.org>
To:	Michel Lespinasse <walken@...gle.com>
Cc:	torvalds@...ux-foundation.org, akpm@...ux-foundation.org,
	paulmck@...ux.vnet.ibm.com, oleg@...hat.com, dhowells@...hat.com,
	willy@...ux.intel.com, tglx@...utronix.de, rostedt@...dmis.org,
	airlied@...il.com, maarten.lankhorst@...onical.com,
	linux-kernel@...r.kernel.org, Ingo Molnar <mingo@...nel.org>
Subject: Re: [RFC 1/8] locking: Move mutex into kernel/locking/

On Tue, Nov 05, 2013 at 12:26:38PM -0800, Michel Lespinasse wrote:
> On Tue, Nov 5, 2013 at 4:10 AM, Peter Zijlstra <peterz@...radead.org> wrote:
> > Index: linux-2.6/kernel/Makefile
> > ===================================================================
> > --- linux-2.6.orig/kernel/Makefile
> > +++ linux-2.6/kernel/Makefile
> > @@ -7,7 +7,7 @@ obj-y     = fork.o exec_domain.o panic.o
> >             sysctl.o sysctl_binary.o capability.o ptrace.o timer.o user.o \
> >             signal.o sys.o kmod.o workqueue.o pid.o task_work.o \
> >             extable.o params.o posix-timers.o \
> > -           kthread.o sys_ni.o posix-cpu-timers.o mutex.o \
> > +           kthread.o sys_ni.o posix-cpu-timers.o \
> >             hrtimer.o rwsem.o nsproxy.o semaphore.o \
> >             notifier.o ksysfs.o cred.o reboot.o \
> >             async.o range.o groups.o lglock.o smpboot.o
> 
> This is probably a stupid question, but I haven't been able to find
> one kernel version that this applies cleanly over ???

Oh my bad, it appears I made it against a working tree, not an actual
published tree. That said, I don't think the rejects should be super
hard to fix.

If people don't object to the idea I'll respin against something
published and testable.


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