linux-kernel - Re: Revert needed: udev spewing warnons on common systems in 3.0

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: <alpine.DEB.2.00.1108021439030.12258@chino.kir.corp.google.com>
Date:	Tue, 2 Aug 2011 14:45:38 -0700 (PDT)
From:	David Rientjes <rientjes@...gle.com>
To:	Alan Cox <alan@...rguk.ukuu.org.uk>
cc:	Linus Torvalds <torvalds@...ux-foundation.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Andi Kleen <andi@...stfloor.org>, linux-kernel@...r.kernel.org
Subject: Re: Revert needed: udev spewing warnons on common systems in 3.0

On Tue, 2 Aug 2011, Alan Cox wrote:

> > That's obviously wrong since all of the applications that I've cited 
> > that have been fixed to date have been the result of users actually 
> > noticing the printk_once() and emailing me directly to pass it along to 
> > the appropriate parties.  I've also found other cases where bugzilla 
> > entries were created based on that single line warning by users, who in 
> > turn get distros and maintainers to convert to the new interface.
> 
> And what did the users do - they complained to the distribution.
> 

All of the examples that I've cited that were fixed as a result of the 
printk_once() were through bugzilla for the developers of those 
applications, I didn't talk to any distro when I publically said I would 
handle all reports of this warning that people didn't know how to triage.

> Actually this raises a more interesting question - would it make sense to
> have a moderated notification list for poking all the distributions about
> things like old API expiry >
> 

I think that's the goal of linux-api@...r.kernel.org although it only has 
113 subscribers, so it could probably play the role of a notification list 
as well as a place to report warnings for things such as deprecated 
interfaces.  More communication other than just sometimes stale entries in 
Documentation/ABI and Documentation/feature-removal-schedule.txt would 
certainly be helpful.
--
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/