linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Carl-Daniel Hailfinger <c-d.hailfinger.kernel.2003@gmx.net>
To: Bill Davidsen <davidsen@tmr.com>
Cc: Chris Friesen <cfriesen@nortelnetworks.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [2.5.68] Scalability issues
Date: Wed, 07 May 2003 02:22:11 +0200	[thread overview]
Message-ID: <3EB851B3.6050804@gmx.net> (raw)
In-Reply-To: <Pine.LNX.3.96.1030506142904.9452D-100000@gatekeeper.tmr.com>

Bill Davidsen wrote:
> On Mon, 5 May 2003, Chris Friesen wrote:
> 
> 
>>Felix von Leitner wrote:
>>
>>>Thus spake David S. Miller (davem@redhat.com):
>>
>>>>Either reproduce without the nvidia module loaded, or take
>>>>your report to nvidia.
>>>
>>>Thank you for this stunning display of unprofessionalism and zealotry.
>>>People like you keep free software alive.
>>
>>He may not have put it as politely as you would like, but there really is no way 
>>to debug a problem in a kernel which has been tainted by binary-only drivers. 
>>That driver could have done literally anything to the kernel on loading.
> 
> There's no need to be rude in any case, particularly after the OP reposted
> a not tainted oops which had been through ksymoops and didn't get any help
> anyway. Why be nasty about the format of a question you're not answering
> even after it's been asked again in the preferred format?

Because the OP violated the lkml FAQ section 1.18:
All problems discovered whilst such a module is loaded must be reported
to the vendor of that module, /not/ the Linux kernel hackers and the
linux-kernel mailing list. [...] "oops" reports marked as tainted are of
no use to the kernel developers and will be ignored.

Davem just restated this fact with the same admittedly strong wording.
Felix von Leitner accused him of unprofessionalism and zealotry. That is
what I would call an offence.

> It's a shame that some people seem to think that lots of hard work
> entitles them to be rude and condescending, while really important
> contributors like Alan Cox, Ingo and akpm can be polite and helpful, even
> when they are correcting someone or disagreeing on an approach to a
> problem.

It's even more shocking if a user insults a kernel developer and expects
this developer (or one of his peers) to actually take care of the
problem. wli chose to investigate the report anyway, something not to be
taken for granted.

Hey, if I insulted Al Viro I'd never expect him to help me (respond,
point out mistakes etc.) anymore. Besides that, Al saved me from diving
into floppy.c, for which I'm still thankful.

Chris: Just a heads up - you may get private hate mail from Peter
"Firefly" Lund like I did because you pointed out a mistake of the OP.
So be warned about it.


Carl-Daniel


  parent reply	other threads:[~2003-05-07  0:10 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-04 17:39 [2.5.68] Scalability issues Felix von Leitner
2003-05-04 18:16 ` Michael Buesch
2003-05-04 19:44 ` Felix von Leitner
2003-05-04 20:12   ` David S. Miller
2003-05-05  7:51     ` Felix von Leitner
2003-05-05  9:51       ` Carl-Daniel Hailfinger
2003-05-05 14:05       ` Chris Friesen
2003-05-06 18:44         ` Bill Davidsen
2003-05-06 20:36           ` Timothy Miller
2003-05-07  0:22           ` Carl-Daniel Hailfinger [this message]
2003-05-04 20:34   ` Tomas Szepe
2003-05-06 11:11 ` William Lee Irwin III
2003-05-06 11:46 ` William Lee Irwin III

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=3EB851B3.6050804@gmx.net \
    --to=c-d.hailfinger.kernel.2003@gmx.net \
    --cc=cfriesen@nortelnetworks.com \
    --cc=davidsen@tmr.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;
as well as URLs for NNTP newsgroup(s).