diff for duplicates of <1455034131.2925.79.camel@hpe.com> diff --git a/a/1.txt b/N1/1.txt index ae40536..91d8027 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -6,25 +6,25 @@ On Tue, 2016-02-09 at 13:26 +0100, Henning Schild wrote: > > > > > On Tue, 9 Feb 2016 10:10:03 +0100 > > > Ingo Molnar <mingo@kernel.org> wrote: -> > > +> > > A A > > > > * Toshi Kani <toshi.kani@hpe.com> wrote: -> > > > +> > > > A A > > > > > Since 4.1, ioremap() supports large page (pud/pmd) mappings in > > > > > x86_64 and PAE. vmalloc_fault() however assumes that the vmalloc > > > > > range is limited to pte mappings. > > > > > > > > > > pgd_ctor() sets the kernel's pgd entries to user's during > > > > > fork(), which makes user processes share the same page tables -> > > > > for the kernel ranges. When a call to ioremap() is made at +> > > > > for the kernel ranges.A A When a call to ioremap() is made at > > > > > run-time that leads to allocate a new 2nd level table (pud in > > > > > 64-bit and pmd in PAE), user process needs to re-sync with the > > > > > updated kernel pgd entry with vmalloc_fault(). > > > > > -> > > > > Following changes are made to vmalloc_fault(). +> > > > > Following changes are made to vmalloc_fault().A A A A > > > > > > > > So what were the effects of this shortcoming? Were large page > > > > ioremap()s unusable? Was this harmless because no driver used this -> > > > facility? +> > > > facility?A A > > > > > > Drivers do use huge ioremap()s. Now if a pre-existing mm is used to > > > access the device memory a #PF and the call to vmalloc_fault would @@ -37,7 +37,7 @@ On Tue, 2016-02-09 at 13:26 +0100, Henning Schild wrote: #PF -> vmalloc_fault -> oops > > > - funny modification of arbitrary memory possible -> > > - can be abused with uio or regular userland ?? +> > > - can be abused with uio or regular userland ??A A A > > Looking over the code again i am not sure the last two are even > possible, it is just the pointer deref that can cause a #PF. diff --git a/a/content_digest b/N1/content_digest index 03b4fd3..0c17b9e 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -25,25 +25,25 @@ "> > \n" "> > > On Tue, 9 Feb 2016 10:10:03 +0100\n" "> > > Ingo Molnar <mingo@kernel.org> wrote:\n" - "> > > \302\240\302\240\n" + "> > > A A \n" "> > > > * Toshi Kani <toshi.kani@hpe.com> wrote:\n" - "> > > > \302\240\302\240\n" + "> > > > A A \n" "> > > > > Since 4.1, ioremap() supports large page (pud/pmd) mappings in\n" "> > > > > x86_64 and PAE. vmalloc_fault() however assumes that the vmalloc\n" "> > > > > range is limited to pte mappings.\n" "> > > > > \n" "> > > > > pgd_ctor() sets the kernel's pgd entries to user's during\n" "> > > > > fork(), which makes user processes share the same page tables\n" - "> > > > > for the kernel ranges.\302\240\302\240When a call to ioremap() is made at\n" + "> > > > > for the kernel ranges.A A When a call to ioremap() is made at\n" "> > > > > run-time that leads to allocate a new 2nd level table (pud in\n" "> > > > > 64-bit and pmd in PAE), user process needs to re-sync with the\n" "> > > > > updated kernel pgd entry with vmalloc_fault().\n" "> > > > > \n" - "> > > > > Following changes are made to vmalloc_fault().\302\240\302\240\302\240\302\240\n" + "> > > > > Following changes are made to vmalloc_fault().A A A A \n" "> > > > \n" "> > > > So what were the effects of this shortcoming? Were large page\n" "> > > > ioremap()s unusable? Was this harmless because no driver used this\n" - "> > > > facility?\302\240\302\240\n" + "> > > > facility?A A \n" "> > > \n" "> > > Drivers do use huge ioremap()s. Now if a pre-existing mm is used to\n" "> > > access the device memory a #PF and the call to vmalloc_fault would\n" @@ -56,7 +56,7 @@ "#PF -> vmalloc_fault -> oops\n" "\n" "> > > - funny modification of arbitrary memory possible\n" - "> > > - can be abused with uio or regular userland ??\302\240\302\240\302\240\n" + "> > > - can be abused with uio or regular userland ??A A A \n" "> \n" "> Looking over the code again i am not sure the last two are even\n" "> possible, it is just the pointer deref that can cause a #PF.\n" @@ -79,4 +79,4 @@ "see: http://www.linux-mm.org/ .\n" "Don't email: <a href=mailto:\"dont@kvack.org\"> email@kvack.org </a>" -cd833ebeb314e215439758bb889aebb4888928abb5e6968a94636b5739b8383a +e6c0cdbfc77374507015c397feb7ddcca520efb0e248fd1faff5c5bc68ea3c9c
diff --git a/a/1.txt b/N2/1.txt index ae40536..564b4b8 100644 --- a/a/1.txt +++ b/N2/1.txt @@ -53,9 +53,3 @@ Yes, the fix should go to stable as well. Thanks, -Toshi - --- -To unsubscribe, send a message with 'unsubscribe linux-mm' in -the body to majordomo@kvack.org. For more info on Linux MM, -see: http://www.linux-mm.org/ . -Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a> diff --git a/a/content_digest b/N2/content_digest index 03b4fd3..0c1e852 100644 --- a/a/content_digest +++ b/N2/content_digest @@ -12,7 +12,7 @@ mingo@redhat.com hpa@zytor.com bp@alien8.de - linux-nvdimm@lists.01.org + linux-nvdimm@ml01.01.org linux-mm@kvack.org " linux-kernel@vger.kernel.org\0" "\00:1\0" @@ -71,12 +71,6 @@ "Yes, the fix should go to stable as well.\n" "\n" "Thanks,\n" - "-Toshi\n" - "\n" - "--\n" - "To unsubscribe, send a message with 'unsubscribe linux-mm' in\n" - "the body to majordomo@kvack.org. For more info on Linux MM,\n" - "see: http://www.linux-mm.org/ .\n" - "Don't email: <a href=mailto:\"dont@kvack.org\"> email@kvack.org </a>" + -Toshi -cd833ebeb314e215439758bb889aebb4888928abb5e6968a94636b5739b8383a +e8ac0105850e2c50761dd69bd9600b3ca1ce2755293bc35829512fe08bc91c12
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.