linux-kernel - Re: OOM changes in Linux 3.7 lead to udev warnings and total breakage of KDE 3.5.10/TDE

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: <CA+55aFz2Kgn0mVV4ozH0g1QGKw1VE6NpgCz9taxxfbCUz2a8VA@mail.gmail.com>
Date:	Mon, 12 Nov 2012 17:10:07 -0800
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	David Rientjes <rientjes@...gle.com>
Cc:	"Artem S. Tashkinov" <t.artem@...os.com>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Davidlohr Bueso <dave@....org>,
	Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: OOM changes in Linux 3.7 lead to udev warnings and total breakage
 of KDE 3.5.10/TDE

On Mon, Nov 12, 2012 at 1:41 PM, David Rientjes <rientjes@...gle.com> wrote:
>
> This is
> http://mail.kde.org/pipermail/unassigned-bugs/2010-December/016850.html
> from almost two years ago.  The tunable had been on the feature removal
> schedule for two years and would have emitted a warning if you had run on
> any kernel during that time.  KDE 4.6.1 and later from two years ago work
> fine.

Doesn't matter. If something breaks real users, it needs to get
reverted (or worked around).

The feature-removal.txt file was a joke, and was used as an excuse for
exactly the above kind of bad behavior. It got removed for good
reasons.

The work-around might be as simple as creating an oom_adj file that
simply doesn't do anything.

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