From: Adrian Bunk <bunk@fs.tum.de>
To: Albert Cahalan <albert@users.sf.net>
Cc: linux-kernel@vger.kernel.org, procps-list@redhat.com,
kernel@theoesters.com, rml@tech9.net, miquels@cistron-office.nl,
xose@wanadoo.es, tab@tuxfamily.org
Subject: Re: [announce] procps 2.0.13 with NPTL enhancements
Date: Fri, 30 May 2003 08:26:36 +0200 [thread overview]
Message-ID: <20030530062635.GM5643@fs.tum.de> (raw)
In-Reply-To: <1054270854.22088.617.camel@cube>
On Fri, May 30, 2003 at 01:00:54AM -0400, Albert Cahalan wrote:
> Robert Love writes:
> On Thu, 2003-05-29 at 18:08, Adrian Bunk wrote:
>
> >> Well, since I read Albert Cahalan's comment in
> >> Debian bug #172735 [1] I understand the people
> >> maintaining a different branch...
> >
> > Exactly.
> >
> > That bug is fixed in the official tree, fyi.
> > A segfault, as you said, is always a bug.
> > An error message is displayed.
>
> You asked for it...
>
> Nice cheapshot there. So, if I remove some
> critical kernel interfaces from your system,
> nothing should crash? How about I take out
> a few choice system calls or a chunk of libc?
>
> (note: the "bug" is not exploitable)
>
> Face it. For nearly a decade, /proc has been
> a critical kernel interface. This isn't 1991.
> (embedded systems excepted; they don't use procps)
>
> That said, I may do something about the issue
> simply to please users with messed-up systems.
>...
Disabling the proc filesystem is simple by unchecking one item in the
kernel config menu and different from taking out "a chunk of libc" it's
more or less supported.
I don't say #172735 is exploitable. An error message "Error: /proc isn't
mounted" tells you what is wrong, a segmentation fault tells you
_nothing_.
I've seen at several occasions that several man days were lost trying to
find problems in other programs that caused segmentation faults. In the
end things like diff'ing strace files give you important hints after
hours of clueless searching. Error messages instead of segmentation
faults would have prevented several fruitless hours in my live.
After reading the last sentence you might perhaps understand my opinion
about the quality of a software whose maintainer says about a
segmentation fault "Crashing is kind of a good thing even. ... In error
checking, there is a certain balance to achieve." .
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next parent reply other threads:[~2003-05-30 6:13 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1054270854.22088.617.camel@cube>
2003-05-30 6:26 ` Adrian Bunk [this message]
2003-06-01 4:53 ` [announce] procps 2.0.13 with NPTL enhancements Werner Almesberger
2003-05-30 16:56 ` Xose Vazquez Perez
[not found] ` <3ED788B5.2080203@wanadoo.es>
2003-05-31 1:25 ` Albert Cahalan
2003-05-31 2:36 Xose Vazquez Perez
-- strict thread matches above, loose matches on Subject: below --
2003-05-30 18:59 Xose Vazquez Perez
2003-05-30 8:12 Paolo Ciarrocchi
2003-05-30 8:20 ` cosmos
2003-05-30 5:30 Albert Cahalan
2003-05-29 17:25 Xose Vazquez Perez
2003-05-29 18:08 ` Adrian Bunk
2003-05-29 11:16 ` Robert Love
2003-05-29 20:01 ` Vincent Hanquez
2003-05-29 15:40 ` Robert Love
2003-05-28 15:09 Robert Love
2003-05-28 23:19 ` Phil Oester
2003-05-28 16:22 ` Robert Love
2003-05-28 23:59 ` Miquel van Smoorenburg
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=20030530062635.GM5643@fs.tum.de \
--to=bunk@fs.tum.de \
--cc=albert@users.sf.net \
--cc=kernel@theoesters.com \
--cc=linux-kernel@vger.kernel.org \
--cc=miquels@cistron-office.nl \
--cc=procps-list@redhat.com \
--cc=rml@tech9.net \
--cc=tab@tuxfamily.org \
--cc=xose@wanadoo.es \
/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