| 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: Fri, 14 Jun 2013 15:47:09 -0700 From: Anton Vorontsov <anton@...msg.org> To: Rob Herring <robherring2@...il.com> Cc: Tony Luck <tony.luck@...il.com>, Kees Cook <keescook@...omium.org>, Colin Cross <ccross@...roid.com>, "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org> Subject: Re: [GIT PULL] pstore/ram for 3.11 On Fri, Jun 14, 2013 at 05:32:16PM -0500, Rob Herring wrote: > https://lkml.org/lkml/2013/4/9/831 > > The main discussion was around the write-combining change which I > dropped. You can pick patches 2 and 3 off the mail list if you prefer. I > would assume they only require an ack from one of the 4 of you which > pulling the tree implicitly does. I've just re-reviewed the discussion. I see Colin was talking about ftrace causing infinite loops due to recursion. Once I stumbled onto this too (but the issue itself was due to missing 'notrace' mark), and Stephen told that recursion protection is kind of mandatory: http://lists.linaro.org/pipermail/linaro-kernel/2012-August/002084.html I belive that the protection is actually there nowadays, and that is why Rob does not see the problem with his patch. So, I guess the patches are good, at least they fix real issues for Rob. :) Acked-by: Anton Vorontsov <anton@...msg.org> (Or I can pick this via linux-pstore.git tree, I'll let Tony decide.) Thanks! Anton -- 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