diff for duplicates of <20181206161950.GB3544@redhat.com> diff --git a/a/1.txt b/N1/1.txt index d1269b8..99caa71 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -2,19 +2,19 @@ On Thu, Dec 06, 2018 at 04:08:12PM +0000, Koenig, Christian wrote: > Am 06.12.18 um 16:21 schrieb Jerome Glisse: > > On Thu, Dec 06, 2018 at 08:09:28AM +0000, Koenig, Christian wrote: > >> Am 06.12.18 um 02:41 schrieb jglisse@redhat.com: -> >>> From: Jérôme Glisse <jglisse@redhat.com> +> >>> From: J�r�me Glisse <jglisse@redhat.com> > >>> > >>> The debugfs take reference on fence without dropping them. Also the > >>> rcu section are not well balance. Fix all that ... > >>> -> >>> Signed-off-by: Jérôme Glisse <jglisse@redhat.com> -> >>> Cc: Christian König <christian.koenig@amd.com> +> >>> Signed-off-by: J�r�me Glisse <jglisse@redhat.com> +> >>> Cc: Christian K�nig <christian.koenig@amd.com> > >>> Cc: Daniel Vetter <daniel.vetter@ffwll.ch> > >>> Cc: Sumit Semwal <sumit.semwal@linaro.org> > >>> Cc: linux-media@vger.kernel.org > >>> Cc: dri-devel@lists.freedesktop.org > >>> Cc: linaro-mm-sig@lists.linaro.org -> >>> Cc: Stéphane Marchesin <marcheu@chromium.org> +> >>> Cc: St�phane Marchesin <marcheu@chromium.org> > >>> Cc: stable@vger.kernel.org > >> Well NAK, you are now taking the RCU lock twice and dropping the RCU and > >> still accessing fobj has a huge potential for accessing freed up memory. @@ -50,4 +50,4 @@ Thank you for reviewing and pointing out the code i was oblivious too :) Cheers, -Jérôme +J�r�me diff --git a/a/content_digest b/N1/content_digest index 4d67569..ab33eaa 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -21,19 +21,19 @@ "> Am 06.12.18 um 16:21 schrieb Jerome Glisse:\n" "> > On Thu, Dec 06, 2018 at 08:09:28AM +0000, Koenig, Christian wrote:\n" "> >> Am 06.12.18 um 02:41 schrieb jglisse@redhat.com:\n" - "> >>> From: J\303\251r\303\264me Glisse <jglisse@redhat.com>\n" + "> >>> From: J\303\257\302\277\302\275r\303\257\302\277\302\275me Glisse <jglisse@redhat.com>\n" "> >>>\n" "> >>> The debugfs take reference on fence without dropping them. Also the\n" "> >>> rcu section are not well balance. Fix all that ...\n" "> >>>\n" - "> >>> Signed-off-by: J\303\251r\303\264me Glisse <jglisse@redhat.com>\n" - "> >>> Cc: Christian K\303\266nig <christian.koenig@amd.com>\n" + "> >>> Signed-off-by: J\303\257\302\277\302\275r\303\257\302\277\302\275me Glisse <jglisse@redhat.com>\n" + "> >>> Cc: Christian K\303\257\302\277\302\275nig <christian.koenig@amd.com>\n" "> >>> Cc: Daniel Vetter <daniel.vetter@ffwll.ch>\n" "> >>> Cc: Sumit Semwal <sumit.semwal@linaro.org>\n" "> >>> Cc: linux-media@vger.kernel.org\n" "> >>> Cc: dri-devel@lists.freedesktop.org\n" "> >>> Cc: linaro-mm-sig@lists.linaro.org\n" - "> >>> Cc: St\303\251phane Marchesin <marcheu@chromium.org>\n" + "> >>> Cc: St\303\257\302\277\302\275phane Marchesin <marcheu@chromium.org>\n" "> >>> Cc: stable@vger.kernel.org\n" "> >> Well NAK, you are now taking the RCU lock twice and dropping the RCU and\n" "> >> still accessing fobj has a huge potential for accessing freed up memory.\n" @@ -69,6 +69,6 @@ "oblivious too :)\n" "\n" "Cheers,\n" - "J\303\251r\303\264me" + "J\303\257\302\277\302\275r\303\257\302\277\302\275me" -a9091b21ea8e7b349110b0c6cfc13a1c35b45db55b00796445c6ac89d2738481 +74293deff69091ca8e5c14209848e58384057bc6e914ba01c0ebbdbaf9891fda
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.