linux-kernel - Re: Device Driver Etiquette

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <75b66ecd0706011138v25e0d352p2fe5c4b5b8933046@mail.gmail.com>
Date:	Fri, 1 Jun 2007 14:38:30 -0400
From:	"Lee Revell" <rlrevell@...-job.com>
To:	"Matthew Fredrickson" <creslin@...ium.com>
Cc:	linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: Device Driver Etiquette

On 6/1/07, Matthew Fredrickson <creslin@...ium.com> wrote:
> is it acceptable (although
> not nice) to simply fix it this way, by disabling irqs while it loads
> the firmware?
>

I would say to just disable IRQs while loading firmware.  Almost every
server I maintain has some vendor driver which generates a "many lost
ticks!" message on load.  As long as it's only done at module load
time it should be fine.

Of course the best solution is to just get the driver into mainline.

Lee
-
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/