linux-kernel - Re: git pull request for tip/tracing/urgent

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:	Wed, 11 Feb 2009 10:53:25 +0100
From:	Ingo Molnar <mingo@...e.hu>
To:	Tejun Heo <tj@...nel.org>
Cc:	Frederic Weisbecker <fweisbec@...il.com>,
	Steven Rostedt <rostedt@...dmis.org>,
	LKML <linux-kernel@...r.kernel.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	"H. Peter Anvin" <hpa@...or.com>
Subject: Re: git pull request for tip/tracing/urgent


* Tejun Heo <tj@...nel.org> wrote:

> Hello,
> 
> Ingo Molnar wrote:
> > This bit:
> > 
> >   	".section .fixup, \"ax\"\n"
> >  	"4: movl $1, %[faulted]\n"
> >  	"   jmp 3b\n"
> >  	".previous\n"
> > 
> > Can be thought of as an 'embedded' or 'nested' section - the '.previous'
> > directive jumps back to whatever section we were in before. This can be
> > nested multiple times too:
> > 
> >    .section A
> >    [...]
> >      .section B
> >      [...]
> >         .section C
> >         [...]
> >         .previous
> >      [...]
> >      .previous
> >    [...]
> >    .previous
> 
> That will result in...
> 
>  A->B->C->B->C->B
> 
> .pushsection and .popsection should be used for nesting, right?
> 
> Thanks.

hm ... doh, yes. I think we even had a bug in this area.

Why is it implemented like this? These semantics seem to make no sense.

	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/