From: Pete Zaitcev <zaitcev@redhat.com>
To: Greg KH <greg@kroah.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: my review of the Device Driver Hardening Design Spec
Date: Sat, 21 Sep 2002 08:51:15 -0400 [thread overview]
Message-ID: <200209211251.g8LCpFt23725@devserv.devel.redhat.com> (raw)
In-Reply-To: <mailman.1032587460.6299.linux-kernel2news@redhat.com>
> - actually, what do any of these CONFIG_ options do, and why
> would someone not want the CONFIG_DRIVER_ROBUST to be always
> enabled?
Probably performance blows when it is enabled.
> In summary, I think that a lot of people have spent a lot of time in
> creating this document, and the surrounding code that matches this
> document. I really wish that a tiny bit of that effort had gone into
> contacting the Linux kernel development community, and asking to work
> with them on a project like this. Due to that not happening, and by
> looking at the resultant spec and code, I'm really afraid the majority
> of that time and effort will have been wasted.
Eek. They never mentioned any code before now. In fact they
explicitly said they weren't going to code before the spec
was ready.
-- Pete
next parent reply other threads:[~2002-09-21 12:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.1032587460.6299.linux-kernel2news@redhat.com>
2002-09-21 12:51 ` Pete Zaitcev [this message]
2002-09-21 18:16 ` my review of the Device Driver Hardening Design Spec Greg KH
2002-09-21 21:52 ` Francois Romieu
2002-09-21 22:02 ` Mr. James W. Laferriere
2002-09-21 22:17 ` Francois Romieu
2002-09-21 22:35 ` Mr. James W. Laferriere
2002-09-21 22:37 ` Mr. James W. Laferriere
2002-09-21 22:42 ` Greg KH
2002-09-22 0:57 ` Andre Hedrick
2002-09-21 1:40 [ANNOUNCE] Linux Hardened Device Drivers Project Greg KH
2002-09-21 5:34 ` my review of the Device Driver Hardening Design Spec Greg KH
2002-09-21 15:21 ` Martin J. Bligh
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=200209211251.g8LCpFt23725@devserv.devel.redhat.com \
--to=zaitcev@redhat.com \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.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