public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Manon Goo <manon@manon.de>
To: "White, Charles" <Charles.White@COMPAQ.com>, Arrays <Arrays@COMPAQ.com>
Cc: linux-kernel@vger.kernel.org,
	"Markus Schröder" <schroeder.markus@allianz.de>
Subject: RE: Hooks for random device entropy generation missing in cpqarray.c
Date: Wed, 20 Mar 2002 17:06:54 +0100	[thread overview]
Message-ID: <5013428.1016644014@eva.dhcp.gimlab.org> (raw)
In-Reply-To: <A2C35BB97A9A384CA2816D24522A53BB01E88B79@cceexc18.americas.cpqcorp.net>

[-- Attachment #1: Type: text/plain, Size: 1749 bytes --]

I have a quick and drity patch for 1 contorlller:

I patched as floows:



--- ./drivers/block/cpqarray.c.old      Wed Mar 20 14:53:16 2002
+++ drivers/block/cpqarray.c    Wed Mar 20 15:31:32 2002
@@ -1009,6 +1009,7 @@

 startio:
        start_io(h);
+       add_blkdev_randomness(MAJOR_NR);
 }

 /*


other Driver (handling more the 1 drive) find out the
Major driver number ...


./drivers/scsi/scsi_lib.c:      add_blkdev_randomness(MAJOR(req->rq_dev));
./drivers/ide/ide.c:            add_blkdev_randomness(MAJOR(rq->rq_dev));
./drivers/block/DAC960.c:         add_blkdev_randomness(DAC960_MAJOR + 
Controller->ControllerNumber);

How would I do this for the cpqarray ?

--On Mittwoch, 20. März 2002 8:25 Uhr -0600 "White, Charles" 
<Charles.White@COMPAQ.com> wrote:

> Yes.. I was reported that it some how got dropped from our 2.4 version of
> the driver..  DON'T add add_interrupt_randomness, just add "|
> SA_SAMPLE_RANDOM" to the call to request_irq.
>
> Patch to follow.
>
>
> -----Original Message-----
> From: Manon Goo [mailto:manon@manon.de]
> Sent: Wednesday, March 20, 2002 7:34 AM
> To: Arrays
> Cc: linux-kernel@vger.kernel.org; tytso@MIT.EDU; Markus Schröder
> Subject: Hooks for random device entropy generation missing in
> cpqarray.c
>
>
> Hi,
>
> All hooks for the random ganeration (add_blkdev_randomness() ) are
> ignored  in the cpqarray / ida  driver.
> 	Is a patch available ?
> 	or an other updated driver ?
> 	any hints where to put add_blkdev_randomness() in your driver ?
>
> 	is add_interrupt_randomness() called on an i386 SMP IO-APCI system ?
>
>
> Thanks
> Manon
>
> PS: Folks on linux-kernel please CC to manon@manon.de I am not on the list
>
>


[-- Attachment #2: Type: application/pgp-signature, Size: 229 bytes --]

  reply	other threads:[~2002-03-20 16:07 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-20 14:25 Hooks for random device entropy generation missing in cpqarray.c White, Charles
2002-03-20 16:06 ` Manon Goo [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-03-20 21:07 Stephen Cameron
2002-03-20 21:24 ` Manon Goo
     [not found] <A2C35BB97A9A384CA2816D24522A53BB01E88B79@cceexc18.americas.cpqc <5013428.1016644014@eva.dhcp.gimlab.org>
2002-03-20 16:16 ` Dave Jones
2002-03-20 16:29   ` Manon Goo
2002-03-20 13:33 Manon Goo
2002-03-20 14:38 ` Zwane Mwaikambo
2002-03-20 15:39   ` Alan Cox
2002-03-20 15:39   ` Manon Goo
2002-03-20 15:42     ` Zwane Mwaikambo

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=5013428.1016644014@eva.dhcp.gimlab.org \
    --to=manon@manon.de \
    --cc=Arrays@COMPAQ.com \
    --cc=Charles.White@COMPAQ.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=schroeder.markus@allianz.de \
    /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