linux-kernel - Re: [patch] scsi: revert "[SCSI] Get rid of scsi

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: <18306.33932.262313.661070@stoffel.org>
Date:	Mon, 7 Jan 2008 14:59:08 -0500
From:	"John Stoffel" <john@...ffel.org>
To:	Stefan Richter <stefanr@...6.in-berlin.de>
Cc:	John Stoffel <john@...ffel.org>, Willy Tarreau <w@....eu>,
	Adrian Bunk <bunk@...nel.org>,
	James Bottomley <James.Bottomley@...senPartnership.com>,
	Matthew Wilcox <matthew@....cx>, Ingo Molnar <mingo@...e.hu>,
	Peter Osterlund <petero2@...ia.com>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	linux-kernel@...r.kernel.org,
	Andrew Morton <akpm@...ux-foundation.org>,
	Al Viro <viro@....linux.org.uk>
Subject: Re: [patch] scsi: revert "[SCSI] Get rid of scsi_cmnd->done"

>>>>> "Stefan" == Stefan Richter <stefanr@...6.in-berlin.de> writes:

Stefan> John Stoffel wrote:
>> The question to me really revolves around how do you automate the
>> process in a transparent manner so that people don't have to change
>> much how they interact with lkml.  

Stefan> I think the more important questions are:
Stefan>   - Are there people who know how to get reports to developers?
Stefan>     (We can't train all potential reporters to get reports right.)

Sure, but telling them "email to helpme@...r.kernel.org" isn't tough.  

Stefan>   - Are there enough developers to work towards bug fixes?

Nope, never enough.

Stefan> The technical means to capture reports, let alone the
Stefan> bugtracking tools, are of secondary importance.

The technical means are secondary, it's the human factors of how bug
reports are captured which is of prime concern.  It's obvious people
aren't happy with bugzilla.  Most, but not all, are happy with LKML,
but a dumb mailing list isn't ideal for tracking bug reports.  

As a SysAdmin, I love being able to tell me user 'just email help' to
open a ticket.  As a SysAdmin, I can then interact with the tickets
which are created and managed using 'RT' (http://www.fsck.org/rt) from
inside my email client without having to think about it too much.  

Again, transparency to the end-user AND tothe developers is key.  If
neither finds if easy to use, it won't be.  So we need to come up with
a work flow which works with us (read you, I just read and contribute
bug reports myself... :-) and for us.  But which never gets in the way
if at all possible.

John

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