linux-kernel - Re: shm updates broke UML

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: <20110801171042.GA25954@albatros>
Date:	Mon, 1 Aug 2011 21:10:42 +0400
From:	Vasiliy Kulikov <segoon@...nwall.com>
To:	Marc Zyngier <maz@...terjones.org>
Cc:	Richard Weinberger <richard@....at>, serge.hallyn@...onical.com,
	torvalds@...ux-foundation.org, akpm@...ux-foundation.org,
	linux-kernel@...r.kernel.org,
	user-mode-linux-devel@...ts.sourceforge.net, toralf.foerster@....de
Subject: Re: shm updates broke UML

On Mon, Aug 01, 2011 at 18:01 +0200, Marc Zyngier wrote:
> It also breaks ARM (at least 11MPCore and Cortex A9).
> The same workaround gets the kernel booting again.

Can you please apply this patch and show the output? 
I suppose all numbers will be nonNULL and the last is NULL.

diff --git a/ipc/shm.c b/ipc/shm.c
index bf46636..8e48ad8 100644
--- a/ipc/shm.c
+++ b/ipc/shm.c
@@ -304,6 +304,12 @@ void exit_shm(struct task_struct *task)
 {
 	struct ipc_namespace *ns = task->nsproxy->ipc_ns;
 
+	pr_err("ns = %p, ids = %p",
+		ns, ns ? &shm_ids(ns) : (void*)(-2));
+	pr_err("wait_list = %p\n", ns ? &shm_ids(ns) ?
+		 &shm_ids(ns).rw_mutex.wait_list : (void*)(-1) : (void*)(-2));
+	pr_err("next = %p\n", shm_ids(ns).rw_mutex.wait_list.next);
+
 	/* Destroy all already created segments, but not mapped yet */
 	down_write(&shm_ids(ns).rw_mutex);
 	if (&shm_ids(ns).in_use)
--
--
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/