linux-kernel - Re: 2.6.29-rc3-git6: Reported regressions from 2.6.28

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: <20090204222256.GA6954@brong.net>
Date:	Thu, 5 Feb 2009 09:22:57 +1100
From:	Bron Gondwana <brong@...tmail.fm>
To:	Ingo Molnar <mingo@...e.hu>
Cc:	Linus Torvalds <torvalds@...ux-foundation.org>,
	Norbert Preining <preining@...ic.at>,
	"Rafael J. Wysocki" <rjw@...k.pl>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Jens Axboe <jens.axboe@...cle.com>,
	Hiroshi Shimamoto <h-shimamoto@...jp.nec.com>
Subject: Re: 2.6.29-rc3-git6: Reported regressions from 2.6.28

On Wed, Feb 04, 2009 at 07:56:06PM +0100, Ingo Molnar wrote:
>    [...] it is a natural reaction: 
>    they only see the small trivial annoyance they intruduce themselves - 
>    which is in a code area and usecase they are prominently familiar with, 
>    so they cannot personally relate to the trouble that users go through if 
>    they hit such issues.

Amen.  Preach it.  I spent quite a while just a week ago arguing that
every semi-loaded machine out there using epoll should not require the
admin to discover that their previously happy software stack was
suddenly hitting an artificially tiny per-user instances count.

Luckily I was able to find multiple blog posts and mailing list archives
with people who had literally spent _days_ tracking down why things had
broken for them when they upgraded to a new -stable kernel.

You really do have to assume that your users don't have time for this
shit.  Anything that really can't DTRT automatically needs to be covered
with plenty of easy to follow instructions on how to fix the problem -
because for someone unfamiliar with that area of the system it really 
does take enormous effort to track down what's changed.

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