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]
Date:	Tue, 13 Nov 2007 15:17:29 -0800
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	Russell King <rmk+lkml@....linux.org.uk>
Cc:	David Miller <davem@...emloft.net>, alsa-devel@...a-project.org,
	netdev@...r.kernel.org, linux-pcmcia@...ts.infradead.org,
	linux-kernel@...r.kernel.org, protasnb@...il.com,
	linux-ide@...r.kernel.org, bugme-daemon@...zilla.kernel.org,
	linux-input@...ey.karlin.mff.cuni.cz
Subject: Re: [BUG] New Kernel Bugs

On Tue, 13 Nov 2007 23:09:37 +0000 Russell King <rmk+lkml@....linux.org.uk> wrote:

> On Tue, Nov 13, 2007 at 02:32:01PM -0800, Andrew Morton wrote:
> > On Tue, 13 Nov 2007 22:18:01 +0000 Russell King <rmk+lkml@....linux.org.uk> wrote:
> > > On Tue, Nov 13, 2007 at 12:52:22PM -0800, Andrew Morton wrote:
> > > > On Tue, 13 Nov 2007 19:32:19 +0000 Russell King <rmk+lkml@....linux.org.uk> wrote:
> > No, I don't mean that at all and this was very plainly obviously from my very
> > clearly written email.  Let me try again.
> 
> If you screen all bugzilla reports then you'll know that bug #9356 arrived
> at about 1400 GMT yesterday.  It's hardly surprising then that your utterly
> crappy responses to Natalie's message (which, incidentally, wasn't copied
> to me) sent within 24 hours of that report cause *great* annoyance.
> 
> > No, no subsystem developer needs to monitor new bugzilla reports.  This is
> > because *I do it for them*.  I will actively make them aware of new reports
> > which I believe are legitimate and which contain sufficient information for
> > them to be able to take further action.
> 
> On the whole you do an excellent job with feeding the bug reports to
> people, and while I recognise that you're only human, things do
> occasionally go wrong.  For instance, sending clearly marked Samsung
> S3C bugs to me rather than Ben Dooks (who's in MAINTAINERS for those
> platforms.)


Well whatever, sorry.  But this is in the noise floor.  Point is: many bug
reports aren't being attended to.


> > > > > It would be far more productive if the ARM category was deleted from
> > > > > bugzilla and the few people who use bugzilla reported their bugs on the
> > > > > mailing list.  We've a couple of thousand people on the ARM kernel
> > > > > mailing list at the moment - that's 3 orders of magnitude more of eyes
> > > > > than look at bugzilla.
> > > > 
> > > > Is that linux-arm-kernel@...ts.arm.linux.org.uk?
> > > 
> > > Yes.
> > > 
> > > > If so, MANITAINERS claims that it is subscribers-only.  That would cause
> > > > some bug reporters to give up and go away.
> > > 
> > > Find some other mailing list; I'm not hosting *nor* am I willing to run a
> > > non-subscribers only mailing list.  Period.  Not negotiable, so don't even
> > > try to change my mind.
> > 
> > Making a list subscribers-only will cause some bug reports to be lost.
> > 
> > Tradeoffs are involved, against which decisions must be made.  You have
> > made yours.
> 
> So how are they lost when they're held in a moderation queue and are
> either accepted, a useful response given to the original poster, or
> are forwarded to someone who can deal with the issue.
> 
> I don't think "subscribers only" describes my lists - we don't devnull
> stuff just because the poster is not a subscriber.

Oh, OK, as long as there really is a human paying attention to those things
then that's fine.  When one is on the sending end of these things one never
knows how long it will take, not whether it will even happen.

-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ