diff for duplicates of <1310718056.2586.275.camel@twins> diff --git a/a/1.txt b/N1/1.txt index cc9f7a0..e0172a5 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -1,13 +1,12 @@ On Fri, 2011-07-15 at 16:07 +0800, Shan Hai wrote: ->=20 +> > The following test case could reveal a bug in the futex_lock_pi() ->=20 -> BUG: On FUTEX_LOCK_PI, there is a infinite loop in the futex_lock_pi()= -=20 +> +> BUG: On FUTEX_LOCK_PI, there is a infinite loop in the futex_lock_pi() > on Powerpc e500 core. > Cause: The linux kernel on the e500 core has no write permission on > the COW page, refer the head comment of the following test code. -> =20 +> > ftrace on test case: > [000] 353.990181: futex_lock_pi_atomic <-futex_lock_pi > [000] 353.990185: cmpxchg_futex_value_locked <-futex_lock_pi_atomic @@ -23,10 +22,10 @@ On Fri, 2011-07-15 at 16:07 +0800, Shan Hai wrote: > [snip] > [000] 353.990230: cmpxchg_futex_value_locked <-futex_lock_pi_atomic > [ a loop occures here ] ->=20 +> -But but but but, that get_user_pages(.write=3D1, .force=3D0) should result +But but but but, that get_user_pages(.write=1, .force=0) should result in a COW break, getting our own writable page. What is this e500 thing smoking that this doesn't work? diff --git a/a/content_digest b/N1/content_digest index 64f7511..8db908a 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -3,27 +3,27 @@ "Subject\0Re: [PATCH 0/1] Fixup write permission of TLB on powerpc e500 core\0" "Date\0Fri, 15 Jul 2011 10:20:56 +0200\0" "To\0Shan Hai <haishan.bai@gmail.com>\0" - "Cc\0tony.luck@intel.com" - linux-kernel@vger.kernel.org - cmetcalf@tilera.com - dhowells@redhat.com + "Cc\0benh@kernel.crashing.org" paulus@samba.org tglx@linutronix.de walken@google.com + dhowells@redhat.com + cmetcalf@tilera.com + tony.luck@intel.com + akpm@linux-foundation.org linuxppc-dev@lists.ozlabs.org - " akpm@linux-foundation.org\0" + " linux-kernel@vger.kernel.org\0" "\00:1\0" "b\0" "On Fri, 2011-07-15 at 16:07 +0800, Shan Hai wrote:\n" - ">=20\n" + "> \n" "> The following test case could reveal a bug in the futex_lock_pi()\n" - ">=20\n" - "> BUG: On FUTEX_LOCK_PI, there is a infinite loop in the futex_lock_pi()=\n" - "=20\n" + "> \n" + "> BUG: On FUTEX_LOCK_PI, there is a infinite loop in the futex_lock_pi() \n" "> on Powerpc e500 core.\n" "> Cause: The linux kernel on the e500 core has no write permission on\n" "> the COW page, refer the head comment of the following test code.\n" - "> =20\n" + "> \n" "> ftrace on test case:\n" "> [000] 353.990181: futex_lock_pi_atomic <-futex_lock_pi\n" "> [000] 353.990185: cmpxchg_futex_value_locked <-futex_lock_pi_atomic\n" @@ -39,12 +39,12 @@ "> [snip]\n" "> [000] 353.990230: cmpxchg_futex_value_locked <-futex_lock_pi_atomic\n" "> [ a loop occures here ]\n" - ">=20\n" + "> \n" "\n" "\n" - "But but but but, that get_user_pages(.write=3D1, .force=3D0) should result\n" + "But but but but, that get_user_pages(.write=1, .force=0) should result\n" "in a COW break, getting our own writable page.\n" "\n" What is this e500 thing smoking that this doesn't work? -274459dd46a26e8ecdbd50d6f071d30d16a7f252a0d96ef1a83224307929b1a2 +7350b96b42e17dca41508acaa92923225d61dec35ac80566706610975bc04149
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.