linux-kernel - Re: [PATCH] x86_64: use kstack_end() in dumpstack

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: <20150223182905.2997548f@kohral>
Date:	Mon, 23 Feb 2015 18:29:05 +0100
From:	Adrien Schildknecht <adrien+dev@...ischi.me>
To:	Steven Rostedt <rostedt@...dmis.org>
Cc:	tglx@...utronix.de, mingo@...hat.com, hpa@...or.com,
	x86@...nel.org, srostedt@...hat.com, luto@...capital.net,
	bp@...en8.de, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] x86_64: use kstack_end() in dumpstack_64.c

> > This patch depends on patch "x86: fix output of
> > show_stack_log_lvl()"
> 
> I'm curious to what the dependency is? What would break if we apply
> this without that patch?

Maybe I misunderstood "dependency".
I mean that this patch won't apply properly since a line of the context
was changed by the previous patch.
"if ((i % STACKSLOTS_PER_LINE) == 0) {"

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