linux-kernel - [PATCH 0/1] (Was: Linux 3.11-rc4)

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: <20130806154314.GA398@redhat.com>
Date:	Tue, 6 Aug 2013 17:43:14 +0200
From:	Oleg Nesterov <oleg@...hat.com>
To:	Linus Torvalds <torvalds@...ux-foundation.org>,
	Felipe Contreras <felipe.contreras@...il.com>,
	Grazvydas Ignotas <notasas@...il.com>
Cc:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Frederic Weisbecker <fweisbec@...il.com>,
	Ingo Molnar <mingo@...e.hu>,
	Denys Vlasenko <dvlasenk@...hat.com>
Subject: [PATCH 0/1] (Was: Linux 3.11-rc4)

Felipe, thanks a lot. Yes fab840f is wrong, this "bug" is already
used as a feature.

Grazvydas, I cc'ed you because I do not really understand
set_thread_context(). It does a couple of extra PTRACE_POKEUSER's
with the "Linux 2.6.33+ needs ..." comment. It would be nice if you
can check if 3.11 still needs this, in this case we probably need
some more minor fixes in this area.

In fact the first comment doesn't look right, when I look at 2.6.33
it seems that POKEUSER(DR0-DR6) should be fine without POKEUSER(DR7),
but this doesn't really matter and I can be easily wrong. Anyway
this looks like a workaround to hide kernel bugs, I will appreciate
it if you can tell if wine still needs it or not.

Oleg.

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