linux-kernel - Re: [PATCH 3/9] jump label: Fix module _

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:	Sat, 16 Oct 2010 08:23:04 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Steven Rostedt <rostedt@...dmis.org>
Cc:	linux-kernel@...r.kernel.org,
	Andrew Morton <akpm@...ux-foundation.org>,
	Frederic Weisbecker <fweisbec@...il.com>,
	Jason Baron <jbaron@...hat.com>,
	Peter Zijlstra <peterz@...radead.org>
Subject: Re: [PATCH 3/9] jump label: Fix module __init section race


* Steven Rostedt <rostedt@...dmis.org> wrote:

> On Fri, 2010-10-15 at 16:09 -0400, Steven Rostedt wrote:
> 
> > --- a/kernel/jump_label.c
> > +++ b/kernel/jump_label.c
> > @@ -168,7 +168,8 @@ void jump_label_update(unsigned long key, enum jump_label_type type)
> >  			count = e_module->nr_entries;
> >  			iter = e_module->table;
> >  			while (count--) {
> > -				if (kernel_text_address(iter->code))
> > +				if (iter->key &&
> > +						kernel_text_address(iter->code))
> 
> Peter, I know you hated this, but the alternative is either:
> 
> 				if (iter->key &&
> 				    kernel_text_address(iter->code))
> 
> or break 80 chars. All three seem bad (although I don't mind breaking 
> 80 chars for this). But I'll leave it for now.

No, the proper alternative is to move the body of the iteration into a 
jump_label_update_entry() inline function ...

Nobody is forcing you to start yet another iteration 4 indentations 
deep. We have functions for a reason.

Thanks,

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