linux-kernel - Re: [PATCH] Please get this committed, _NOW

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: <20091108161625.GA10497@rhlx01.hs-esslingen.de>
Date:	Sun, 8 Nov 2009 17:16:25 +0100
From:	Andreas Mohr <andi@...as.de>
To:	Arnd Bergmann <arnd@...db.de>
Cc:	Américo Wang <xiyou.wangcong@...il.com>,
	Andreas Mohr <andi@...as.de>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	"Michael A. Griffith" <grif@....org>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] Please get this committed, _NOW_ (preferrably 5 years
	ago), thanks.

Hi,

On Sun, Nov 08, 2009 at 04:30:32PM +0100, Arnd Bergmann wrote:
> On Sunday 08 November 2009, Américo Wang wrote:
> > Yeah, I mentioned it to mean it is not suitable to explain
> > user-space problems in a kernel source file. Putting it into a kernel
> > doc should be fine.
> 
> I think it would be best to put it on a wiki page, e.g. on kernelnewbies.org
> and point to that. That means you will be able to add information to it
> independent of the kernel version.

I don't know, personally I think that's way too disconnected.
A Wiki entry might be down, might get renamed, might get converted to an
entirely different Wiki etc. Or might sit on a certain (admittedly large ;)
network that I don't have access to under certain circumstances.
In general these issues should be treated right where they're being created,
and that's the kernel.
And I don't see how "independent of the kernel version" is relevant
here. If I have such an issue, then I look into that file on a tree I
have here (which usually is a current version), and if that doesn't
help, then one could look into the exact version that (tries to) boots.

And IMHO what we should perhaps think of is inventing a reference number
scheme for people to easily look up kernel issues.
This could then be something like "LKE#1234: No init found." (L_inux
K_ernel E_rror).
OTOH this would bloat kernel messages, thus maybe there's a way to
handle it more intelligently.

Thanks,

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