netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: Bryan O'Donoghue <bryan.odonoghue@linaro.org>
Cc: loic.poulain@linaro.org, kvalo@kernel.org, davem@davemloft.net,
	edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
	wcn36xx@lists.infradead.org, linux-wireless@vger.kernel.org,
	netdev@vger.kernel.org
Subject: Re: [PATCH v2] wcn36xx: Add RX frame SNR as a source of system entropy
Date: Thu, 15 Sep 2022 00:57:50 +0100	[thread overview]
Message-ID: <YyJqfsXLESDWDBvR@zx2c4.com> (raw)
In-Reply-To: <20220914212841.1407497-2-bryan.odonoghue@linaro.org>

On Wed, Sep 14, 2022 at 10:28:41PM +0100, Bryan O'Donoghue wrote:
> The signal-to-noise-ratio SNR is returned by the wcn36xx firmware for each
> received frame. SNR represents all of the unwanted interference signal
> after filtering out the fundamental frequency and harmonics of the
> frequency.
> 
> Noise can come from various electromagnetic sources, from temperature
> affecting the performance hardware components or quantization effects
> converting from analog to digital domains.
> 
> The SNR value returned by the WiFi firmware then is a good source of
> entropy.
> 
> Other WiFi drivers offer up the noise component of the FFT as an entropy
> source for the random pool e.g.
> 
> commit 2aa56cca3571 ("ath9k: Mix the received FFT bins to the random pool")
> 
> I attended Jason's talk on sources of randomness at Plumbers and it
> occurred to me that SNR is a reasonable candidate to add.

Neat!

> Cc: Jason A. Donenfeld <Jason@zx2c4.com>
> Signed-off-by: Bryan O'Donoghue <bryan.odonoghue@linaro.org>
> ---
>  drivers/net/wireless/ath/wcn36xx/txrx.c | 3 +++
>  1 file changed, 3 insertions(+)
> 
> diff --git a/drivers/net/wireless/ath/wcn36xx/txrx.c b/drivers/net/wireless/ath/wcn36xx/txrx.c
> index 8da3955995b6e..b73229776af8b 100644
> --- a/drivers/net/wireless/ath/wcn36xx/txrx.c
> +++ b/drivers/net/wireless/ath/wcn36xx/txrx.c
> @@ -16,6 +16,7 @@
>  
>  #define pr_fmt(fmt) KBUILD_MODNAME ": " fmt
>  
> +#include <linux/random.h>
>  #include "txrx.h"
>  
>  static inline int get_rssi0(struct wcn36xx_rx_bd *bd)
> @@ -297,6 +298,8 @@ static void wcn36xx_update_survey(struct wcn36xx *wcn, int rssi, int snr,
>  	wcn->chan_survey[idx].rssi = rssi;
>  	wcn->chan_survey[idx].snr = snr;
>  	spin_unlock(&wcn->survey_lock);
> +
> +	add_device_randomness(&snr, sizeof(s8));

Won't this break on big endian? Just have an assignment handle it:

    u8 snr_sample = snr & 0xff;
    add_device_randomness(&snr_sample, sizeof(snr_sample);

That & 0xff is redundant, but it doesn't hurt to be explicit.

Jason

  reply	other threads:[~2022-09-14 23:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-14 21:28 [PATCH v2 0/1] wcn36xx: Use SNR as a source of system entropy Bryan O'Donoghue
2022-09-14 21:28 ` [PATCH v2] wcn36xx: Add RX frame " Bryan O'Donoghue
2022-09-14 23:57   ` Jason A. Donenfeld [this message]
2022-09-15  0:14     ` Bryan O'Donoghue
2022-09-15  1:22       ` Jason A. Donenfeld

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=YyJqfsXLESDWDBvR@zx2c4.com \
    --to=jason@zx2c4.com \
    --cc=bryan.odonoghue@linaro.org \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=kuba@kernel.org \
    --cc=kvalo@kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=loic.poulain@linaro.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=wcn36xx@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).