From: Stefan Richter <stefanr@s5r6.in-berlin.de>
To: Clemens Ladisch <clemens@ladisch.de>
Cc: linux1394-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org, "Theodore Ts'o" <tytso@mit.edu>
Subject: Re: [PATCH] firewire: core: feed /dev/random with devices' GUIDs
Date: Sun, 12 Aug 2012 23:58:56 +0200 [thread overview]
Message-ID: <20120812235856.65e2c7d5@stein> (raw)
In-Reply-To: <5027CFA7.9000100@ladisch.de>
On Aug 12 Clemens Ladisch wrote:
> Send the GUIDs of newly registered controllers and devices
> to the /dev/random driver to help seed its pools.
>
> Signed-off-by: Clemens Ladisch <clemens@ladisch.de>
This looks good to me, almost. Isn't the call in fw_card_add redundant?
The local node's fw_device instance initializer feeds the same GUID,
although a little bit later.
(Added CC: lkml and Theodore because I am not overly familiar with this
matter.)
> ---
> drivers/firewire/core-card.c | 3 +++
> drivers/firewire/core-device.c | 3 +++
> 2 files changed, 6 insertions(+), 0 deletions(-)
>
> based on 3.6-rc1
>
> --- a/drivers/firewire/core-card.c
> +++ b/drivers/firewire/core-card.c
> @@ -29,6 +29,7 @@
> #include <linux/list.h>
> #include <linux/module.h>
> #include <linux/mutex.h>
> +#include <linux/random.h>
> #include <linux/spinlock.h>
> #include <linux/workqueue.h>
>
> @@ -570,6 +571,8 @@ int fw_card_add(struct fw_card *card,
> card->link_speed = link_speed;
> card->guid = guid;
>
> + add_device_randomness(&guid, sizeof(guid));
> +
> mutex_lock(&card_mutex);
>
> generate_config_rom(card, tmp_config_rom);
> --- a/drivers/firewire/core-device.c
> +++ b/drivers/firewire/core-device.c
> @@ -32,6 +32,7 @@
> #include <linux/mod_devicetable.h>
> #include <linux/module.h>
> #include <linux/mutex.h>
> +#include <linux/random.h>
> #include <linux/rwsem.h>
> #include <linux/slab.h>
> #include <linux/spinlock.h>
> @@ -1066,6 +1067,8 @@ static void fw_device_init(struct work_struct *work)
> device->config_rom_retries = 0;
>
> set_broadcast_channel(device, device->generation);
> +
> + add_device_randomness(&device->config_rom[3], 8);
> }
>
> /*
--
Stefan Richter
-=====-===-- =--- -==--
http://arcgraph.de/sr/
next parent reply other threads:[~2012-08-12 21:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5027CFA7.9000100@ladisch.de>
2012-08-12 21:58 ` Stefan Richter [this message]
2012-08-13 7:08 ` [PATCH] firewire: core: feed /dev/random with devices' GUIDs Clemens Ladisch
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=20120812235856.65e2c7d5@stein \
--to=stefanr@s5r6.in-berlin.de \
--cc=clemens@ladisch.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux1394-devel@lists.sourceforge.net \
--cc=tytso@mit.edu \
/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.