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: <200802181235.31503.rjw@sisk.pl>
Date:	Mon, 18 Feb 2008 12:35:30 +0100
From:	"Rafael J. Wysocki" <rjw@...k.pl>
To:	Jiri Slaby <jirislaby@...il.com>
Cc:	Ingo Molnar <mingo@...e.hu>, Alexey Dobriyan <adobriyan@...il.com>,
	LKML <linux-kernel@...r.kernel.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Adrian Bunk <bunk@...nel.org>,
	Alan Cox <alan@...rguk.ukuu.org.uk>,
	Tilman Schmidt <tilman@...p.cc>, Greg KH <gregkh@...e.de>
Subject: Re: 2.6.25-rc2: Reported regressions from 2.6.24

On Monday, 18 of February 2008, Jiri Slaby wrote:
> On 02/18/2008 10:49 AM, Ingo Molnar wrote:
> > * Alexey Dobriyan <adobriyan@...il.com> wrote:
> > 
> >> Why on earth do we have CONFIG_SYSFS_DEPRECATED at all if the only 
> >> sane choice for someone who tests new kernels is to always turn it on?
> > 
> > seconded ...
> > 
> > it's insane how inconvenient certain storage systems are to use, and 
> > people get turned away with NOATBUG. ITISABUG every time user-space 
> > breaks or the user has to do _anything_ to get the box working as it 
> > should.
> 
> No, user needn't to do anything. Just turn that default y option really to y 
> (yes, you are right, the help text of this option is misleading...). It's like 
> you turn off old acpi events option and scream that you acpi daemon doesn't work 
> for instance. There are many instances of this behaviour in the kernel. And yes, 
> many people don't need that option tuyrned on -- I think we need not-y testers 
> too, but it might be my personal feeling.

Well, my definition of a regression from 2.6.24 is that it happens when someone
takes a .config that worked with 2.6.24, configures the kernel with that,
leaving the defaults for the options he is _asked_ _for_, and the resulting
kernel doesn't work as expected.

Thanks,
Rafael
--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ