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:	Mon, 15 Sep 2008 10:59:42 -0700
From:	Frank Mayhar <fmayhar@...gle.com>
To:	Ingo Molnar <mingo@...e.hu>
Cc:	Roland McGrath <roland@...hat.com>,
	linux-kernel <linux-kernel@...r.kernel.org>,
	Thomas Gleixner <tglx@...utronix.de>,
	Alexey Dobriyan <adobriyan@...il.com>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Oleg Nesterov <oleg@...sign.ru>
Subject: Re: [PATCH 2.6.27-rc5 resubmit] Fix itimer/many thread hang.

On Mon, 2008-09-15 at 08:41 +0200, Ingo Molnar wrote:
> * Roland McGrath <roland@...hat.com> wrote:
> 
> > > please uninline these functions.
> > 
> > They are short and have only one caller.
> 
> then they should be defined in the .c file which uses them.

Well, they are actually used in sched.h, in the inline routines
account_group_user_time() and friends, which are in turn used by
routines in sched.c.  The point here is that the
thread_group_cputime_account_xxx() routines are defined differently
depending upon whether we're building for UP or SMP and the
account_group_xxx() routines use the appropriate version accordingly.

> really, sched.h is large enough already and has lots of unnecessary 
> stuff in it.

Agreed, but Roland and I were trying to make life easier for folks who
have to maintain SMP and UP versions of this stuff, keeping it all in
one place rather than scattering it about.

If you insist, I'll un-inline the routines but this will mean moving all
of this (thread_group_cputime_account_xxx() and account_group_xxx()
routines) to sched.c.  Maybe that makes sense.  It's your call; I'll
hold off on the changes (and resubmitting the patch) while I wait for
you to let me know what you prefer.  Thanks.
-- 
Frank Mayhar <fmayhar@...gle.com>
Google, Inc.

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

Powered by Openwall GNU/*/Linux Powered by OpenVZ