| 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
| ||
|
Date: Tue, 26 Sep 2006 20:55:41 -0600 From: ebiederm@...ssion.com (Eric W. Biederman) To: Bill Huey (hui) <billh@...ppy.monkey.org> Cc: Ingo Molnar <mingo@...e.hu>, linux-kernel@...r.kernel.org, Thomas Gleixner <tglx@...utronix.de>, John Stultz <johnstul@...ibm.com>, "Paul E. McKenney" <paulmck@...ibm.com>, Dipankar Sarma <dipankar@...ibm.com>, Arjan van de Ven <arjan@...radead.org> Subject: Re: [PATCH] move put_task_struct() reaping into a thread [Re: 2.6.18-rt1] Bill Huey (hui) <billh@...ppy.monkey.org> writes: > On Wed, Sep 20, 2006 at 04:19:07PM +0200, Ingo Molnar wrote: >> I'm pleased to announce the 2.6.18-rt1 tree, which can be downloaded >> from the usual place: > ... >> as usual, bugreports, fixes and suggestions are welcome, > > Speaking of which... > > This patch moves put_task_struct() reaping into a thread instead of an > RCU callback function as discussed with Esben publically and Ingo privately: Stupid question. Why does the rt tree make all calls to put_task_struct an rcu action? We only need the rcu callback from kernel/exit.c Nothing else needs those semantics. I agree that put_task_struct is the most common point so this is unlikely to remove your issues with rcu callbacks but it just seems completely backwards to increase the number of rcu callbacks in the rt tree. Eric - 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/
Powered by blists - more mailing lists