From: lauraa@codeaurora.org (Laura Abbott)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC/PATCH 2/3] arm: Add ARCH_WANT_OF_RANDOMNESS
Date: Wed, 12 Feb 2014 16:54:07 -0800 [thread overview]
Message-ID: <52FC17AF.1080508@codeaurora.org> (raw)
In-Reply-To: <20140212164907.0E958C407C9@trevor.secretlab.ca>
On 2/12/2014 8:49 AM, Grant Likely wrote:
> On Tue, 11 Feb 2014 17:33:24 -0800, Laura Abbott <lauraa@codeaurora.org> wrote:
>> The stack canary for ARM is currently the same across reboots
>> due to lack of randomness early enough. Add ARCH_WANT_OF_RANDOMNESS
>> to allow devices to add whatever randomness they need.
>>
>> Signed-off-by: Laura Abbott <lauraa@codeaurora.org>
>
> Do you have a draft patch for a user of this yet?
>
I had a particular patch in mind but I need to re-work it to work with
the upstream tree. I wanted to at least send out the infrastructure to
see how open people were to the idea. After reading the comments, I have
a couple more ideas of users as well. I'll see if I can work that in for v2.
> g.
>
Thanks,
Laura
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
hosted by The Linux Foundation
WARNING: multiple messages have this Message-ID (diff)
From: Laura Abbott <lauraa-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
To: Grant Likely
<grant.likely-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>,
Rob Herring <robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
Arnd Bergmann <arnd-r2nGTMty4D4@public.gmane.org>
Cc: linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
Kumar Gala <galak-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>,
Kees Cook <keescook-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org>
Subject: Re: [RFC/PATCH 2/3] arm: Add ARCH_WANT_OF_RANDOMNESS
Date: Wed, 12 Feb 2014 16:54:07 -0800 [thread overview]
Message-ID: <52FC17AF.1080508@codeaurora.org> (raw)
In-Reply-To: <20140212164907.0E958C407C9-WNowdnHR2B42iJbIjFUEsiwD8/FfD2ys@public.gmane.org>
On 2/12/2014 8:49 AM, Grant Likely wrote:
> On Tue, 11 Feb 2014 17:33:24 -0800, Laura Abbott <lauraa-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org> wrote:
>> The stack canary for ARM is currently the same across reboots
>> due to lack of randomness early enough. Add ARCH_WANT_OF_RANDOMNESS
>> to allow devices to add whatever randomness they need.
>>
>> Signed-off-by: Laura Abbott <lauraa-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
>
> Do you have a draft patch for a user of this yet?
>
I had a particular patch in mind but I need to re-work it to work with
the upstream tree. I wanted to at least send out the infrastructure to
see how open people were to the idea. After reading the comments, I have
a couple more ideas of users as well. I'll see if I can work that in for v2.
> g.
>
Thanks,
Laura
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
hosted by The Linux Foundation
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
WARNING: multiple messages have this Message-ID (diff)
From: Laura Abbott <lauraa@codeaurora.org>
To: Grant Likely <grant.likely@linaro.org>,
Rob Herring <robh+dt@kernel.org>, Arnd Bergmann <arnd@arndb.de>
Cc: linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Kumar Gala <galak@codeaurora.org>,
Kees Cook <keescook@chromium.org>
Subject: Re: [RFC/PATCH 2/3] arm: Add ARCH_WANT_OF_RANDOMNESS
Date: Wed, 12 Feb 2014 16:54:07 -0800 [thread overview]
Message-ID: <52FC17AF.1080508@codeaurora.org> (raw)
In-Reply-To: <20140212164907.0E958C407C9@trevor.secretlab.ca>
On 2/12/2014 8:49 AM, Grant Likely wrote:
> On Tue, 11 Feb 2014 17:33:24 -0800, Laura Abbott <lauraa@codeaurora.org> wrote:
>> The stack canary for ARM is currently the same across reboots
>> due to lack of randomness early enough. Add ARCH_WANT_OF_RANDOMNESS
>> to allow devices to add whatever randomness they need.
>>
>> Signed-off-by: Laura Abbott <lauraa@codeaurora.org>
>
> Do you have a draft patch for a user of this yet?
>
I had a particular patch in mind but I need to re-work it to work with
the upstream tree. I wanted to at least send out the infrastructure to
see how open people were to the idea. After reading the comments, I have
a couple more ideas of users as well. I'll see if I can work that in for v2.
> g.
>
Thanks,
Laura
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
hosted by The Linux Foundation
next prev parent reply other threads:[~2014-02-13 0:54 UTC|newest]
Thread overview: 69+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-12 1:33 [RFC/PATCH 0/3] Add devicetree scanning for randomness Laura Abbott
2014-02-12 1:33 ` Laura Abbott
[not found] ` < 201402121251.06280.arnd@arndb.de>
2014-02-12 1:33 ` [RFC/PATCH 1/3] of: Add early randomness hooks Laura Abbott
2014-02-12 1:33 ` Laura Abbott
2014-02-12 16:47 ` Grant Likely
2014-02-12 16:47 ` Grant Likely
2014-02-12 16:47 ` Grant Likely
2014-02-12 1:33 ` [RFC/PATCH 2/3] arm: Add ARCH_WANT_OF_RANDOMNESS Laura Abbott
2014-02-12 1:33 ` Laura Abbott
2014-02-12 16:49 ` Grant Likely
2014-02-12 16:49 ` Grant Likely
2014-02-12 16:49 ` Grant Likely
2014-02-13 0:54 ` Laura Abbott [this message]
2014-02-13 0:54 ` Laura Abbott
2014-02-13 0:54 ` Laura Abbott
2014-02-12 1:33 ` [RFC/PATCH 3/3] init: Move stack canary initialization after setup_arch Laura Abbott
2014-02-12 1:33 ` Laura Abbott
2014-02-12 11:51 ` [RFC/PATCH 0/3] Add devicetree scanning for randomness Arnd Bergmann
2014-02-12 11:51 ` Arnd Bergmann
2014-02-12 11:51 ` Arnd Bergmann
2014-02-12 17:45 ` Jason Cooper
2014-02-12 17:45 ` Jason Cooper
2014-02-12 17:45 ` Jason Cooper
2014-02-12 18:13 ` Olof Johansson
2014-02-12 18:13 ` Olof Johansson
2014-02-12 18:13 ` Olof Johansson
2014-02-12 18:32 ` Jason Cooper
2014-02-12 18:32 ` Jason Cooper
2014-02-12 18:32 ` Jason Cooper
2014-02-12 18:17 ` Arnd Bergmann
2014-02-12 18:17 ` Arnd Bergmann
2014-02-12 18:17 ` Arnd Bergmann
2014-02-12 18:45 ` Jason Cooper
2014-02-12 18:45 ` Jason Cooper
2014-02-12 18:45 ` Jason Cooper
2014-02-12 19:12 ` Arnd Bergmann
2014-02-12 19:12 ` Arnd Bergmann
2014-02-12 19:43 ` Jason Cooper
2014-02-12 19:43 ` Jason Cooper
2014-02-12 23:55 ` Rob Herring
2014-02-12 23:55 ` Rob Herring
2014-02-12 23:55 ` Rob Herring
2014-02-12 18:20 ` Jason Gunthorpe
2014-02-12 18:20 ` Jason Gunthorpe
2014-02-12 18:20 ` Jason Gunthorpe
2014-02-12 18:51 ` Jason Cooper
2014-02-12 18:51 ` Jason Cooper
2014-02-12 18:51 ` Jason Cooper
2014-02-17 15:54 ` Grant Likely
2014-02-17 15:54 ` Grant Likely
2014-02-17 16:13 ` Arnd Bergmann
2014-02-17 16:13 ` Arnd Bergmann
2014-02-17 16:13 ` Arnd Bergmann
2014-02-17 18:23 ` Jason Cooper
2014-02-17 18:23 ` Jason Cooper
2014-02-17 21:07 ` Geert Uytterhoeven
2014-02-17 21:07 ` Geert Uytterhoeven
2014-02-18 17:56 ` Jason Cooper
2014-02-18 17:56 ` Jason Cooper
2014-02-18 17:56 ` Jason Cooper
2014-02-18 9:39 ` Grant Likely
2014-02-18 9:39 ` Grant Likely
2014-02-18 9:39 ` Grant Likely
2014-02-18 18:19 ` Jason Gunthorpe
2014-02-18 18:19 ` Jason Gunthorpe
2014-02-12 21:35 ` Kees Cook
2014-02-12 21:35 ` Kees Cook
2014-02-13 0:06 ` Laura Abbott
2014-02-13 0:06 ` Laura Abbott
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=52FC17AF.1080508@codeaurora.org \
--to=lauraa@codeaurora.org \
--cc=linux-arm-kernel@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.