From: Jerome Glisse <jglisse@redhat.com>
To: "Koenig, Christian" <Christian.Koenig@amd.com>
Cc: "Daniel Vetter" <daniel.vetter@ffwll.ch>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
"linaro-mm-sig@lists.linaro.org" <linaro-mm-sig@lists.linaro.org>,
"stable@vger.kernel.org" <stable@vger.kernel.org>,
"Stéphane Marchesin" <marcheu@chromium.org>,
"linux-media@vger.kernel.org" <linux-media@vger.kernel.org>
Subject: Re: [PATCH] dma-buf: fix debugfs versus rcu and fence dumping
Date: Thu, 6 Dec 2018 10:21:17 -0500 [thread overview]
Message-ID: <20181206152116.GA3544@redhat.com> (raw)
In-Reply-To: <b520e7b6-a8f6-da49-fc7d-460823eabf47@amd.com>
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>
> >
> > 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>
> > 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: 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.
>
> The only correct thing I can see here is to grab a reference to the
> fence before printing any info on it,
> Christian.
Hu ? That is exactly what i am doing, take reference under rcu,
rcu_unlock print the fence info, drop the fence reference, rcu
lock rinse and repeat ...
Note that the fobj in _existing_ code is access outside the rcu
end that there is an rcu imbalance in that code ie a lonlely
rcu_unlock after the for loop.
So that the existing code is broken.
>
> > ---
> > drivers/dma-buf/dma-buf.c | 11 +++++++++--
> > 1 file changed, 9 insertions(+), 2 deletions(-)
> >
> > diff --git a/drivers/dma-buf/dma-buf.c b/drivers/dma-buf/dma-buf.c
> > index 13884474d158..f6f4de42ac49 100644
> > --- a/drivers/dma-buf/dma-buf.c
> > +++ b/drivers/dma-buf/dma-buf.c
> > @@ -1051,24 +1051,31 @@ static int dma_buf_debug_show(struct seq_file *s, void *unused)
> > fobj = rcu_dereference(robj->fence);
> > shared_count = fobj ? fobj->shared_count : 0;
> > fence = rcu_dereference(robj->fence_excl);
> > + fence = dma_fence_get_rcu(fence);
> > if (!read_seqcount_retry(&robj->seq, seq))
> > break;
> > rcu_read_unlock();
> > }
> > -
> > - if (fence)
> > + if (fence) {
> > seq_printf(s, "\tExclusive fence: %s %s %ssignalled\n",
> > fence->ops->get_driver_name(fence),
> > fence->ops->get_timeline_name(fence),
> > dma_fence_is_signaled(fence) ? "" : "un");
> > + dma_fence_put(fence);
> > + }
> > +
> > + rcu_read_lock();
> > for (i = 0; i < shared_count; i++) {
> > fence = rcu_dereference(fobj->shared[i]);
> > if (!dma_fence_get_rcu(fence))
> > continue;
> > + rcu_read_unlock();
> > seq_printf(s, "\tShared fence: %s %s %ssignalled\n",
> > fence->ops->get_driver_name(fence),
> > fence->ops->get_timeline_name(fence),
> > dma_fence_is_signaled(fence) ? "" : "un");
> > + dma_fence_put(fence);
> > + rcu_read_lock();
> > }
> > rcu_read_unlock();
> >
>
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
WARNING: multiple messages have this Message-ID (diff)
From: Jerome Glisse <jglisse@redhat.com>
To: "Koenig, Christian" <Christian.Koenig@amd.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Daniel Vetter" <daniel.vetter@ffwll.ch>,
"Sumit Semwal" <sumit.semwal@linaro.org>,
"linux-media@vger.kernel.org" <linux-media@vger.kernel.org>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
"linaro-mm-sig@lists.linaro.org" <linaro-mm-sig@lists.linaro.org>,
"Stéphane Marchesin" <marcheu@chromium.org>,
"stable@vger.kernel.org" <stable@vger.kernel.org>
Subject: Re: [PATCH] dma-buf: fix debugfs versus rcu and fence dumping
Date: Thu, 6 Dec 2018 10:21:17 -0500 [thread overview]
Message-ID: <20181206152116.GA3544@redhat.com> (raw)
In-Reply-To: <b520e7b6-a8f6-da49-fc7d-460823eabf47@amd.com>
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>
> >
> > 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>
> > 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: 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.
>
> The only correct thing I can see here is to grab a reference to the
> fence before printing any info on it,
> Christian.
Hu ? That is exactly what i am doing, take reference under rcu,
rcu_unlock print the fence info, drop the fence reference, rcu
lock rinse and repeat ...
Note that the fobj in _existing_ code is access outside the rcu
end that there is an rcu imbalance in that code ie a lonlely
rcu_unlock after the for loop.
So that the existing code is broken.
>
> > ---
> > drivers/dma-buf/dma-buf.c | 11 +++++++++--
> > 1 file changed, 9 insertions(+), 2 deletions(-)
> >
> > diff --git a/drivers/dma-buf/dma-buf.c b/drivers/dma-buf/dma-buf.c
> > index 13884474d158..f6f4de42ac49 100644
> > --- a/drivers/dma-buf/dma-buf.c
> > +++ b/drivers/dma-buf/dma-buf.c
> > @@ -1051,24 +1051,31 @@ static int dma_buf_debug_show(struct seq_file *s, void *unused)
> > fobj = rcu_dereference(robj->fence);
> > shared_count = fobj ? fobj->shared_count : 0;
> > fence = rcu_dereference(robj->fence_excl);
> > + fence = dma_fence_get_rcu(fence);
> > if (!read_seqcount_retry(&robj->seq, seq))
> > break;
> > rcu_read_unlock();
> > }
> > -
> > - if (fence)
> > + if (fence) {
> > seq_printf(s, "\tExclusive fence: %s %s %ssignalled\n",
> > fence->ops->get_driver_name(fence),
> > fence->ops->get_timeline_name(fence),
> > dma_fence_is_signaled(fence) ? "" : "un");
> > + dma_fence_put(fence);
> > + }
> > +
> > + rcu_read_lock();
> > for (i = 0; i < shared_count; i++) {
> > fence = rcu_dereference(fobj->shared[i]);
> > if (!dma_fence_get_rcu(fence))
> > continue;
> > + rcu_read_unlock();
> > seq_printf(s, "\tShared fence: %s %s %ssignalled\n",
> > fence->ops->get_driver_name(fence),
> > fence->ops->get_timeline_name(fence),
> > dma_fence_is_signaled(fence) ? "" : "un");
> > + dma_fence_put(fence);
> > + rcu_read_lock();
> > }
> > rcu_read_unlock();
> >
>
WARNING: multiple messages have this Message-ID (diff)
From: Jerome Glisse <jglisse@redhat.com>
To: "Koenig, Christian" <Christian.Koenig@amd.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Daniel Vetter" <daniel.vetter@ffwll.ch>,
"Sumit Semwal" <sumit.semwal@linaro.org>,
"linux-media@vger.kernel.org" <linux-media@vger.kernel.org>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
"linaro-mm-sig@lists.linaro.org" <linaro-mm-sig@lists.linaro.org>,
"Stéphane Marchesin" <marcheu@chromium.org>,
"stable@vger.kernel.org" <stable@vger.kernel.org>
Subject: Re: [PATCH] dma-buf: fix debugfs versus rcu and fence dumping
Date: Thu, 6 Dec 2018 10:21:17 -0500 [thread overview]
Message-ID: <20181206152116.GA3544@redhat.com> (raw)
In-Reply-To: <b520e7b6-a8f6-da49-fc7d-460823eabf47@amd.com>
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>
> >
> > 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>
> > 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: 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.
>
> The only correct thing I can see here is to grab a reference to the
> fence before printing any info on it,
> Christian.
Hu ? That is exactly what i am doing, take reference under rcu,
rcu_unlock print the fence info, drop the fence reference, rcu
lock rinse and repeat ...
Note that the fobj in _existing_ code is access outside the rcu
end that there is an rcu imbalance in that code ie a lonlely
rcu_unlock after the for loop.
So that the existing code is broken.
>
> > ---
> > drivers/dma-buf/dma-buf.c | 11 +++++++++--
> > 1 file changed, 9 insertions(+), 2 deletions(-)
> >
> > diff --git a/drivers/dma-buf/dma-buf.c b/drivers/dma-buf/dma-buf.c
> > index 13884474d158..f6f4de42ac49 100644
> > --- a/drivers/dma-buf/dma-buf.c
> > +++ b/drivers/dma-buf/dma-buf.c
> > @@ -1051,24 +1051,31 @@ static int dma_buf_debug_show(struct seq_file *s, void *unused)
> > fobj = rcu_dereference(robj->fence);
> > shared_count = fobj ? fobj->shared_count : 0;
> > fence = rcu_dereference(robj->fence_excl);
> > + fence = dma_fence_get_rcu(fence);
> > if (!read_seqcount_retry(&robj->seq, seq))
> > break;
> > rcu_read_unlock();
> > }
> > -
> > - if (fence)
> > + if (fence) {
> > seq_printf(s, "\tExclusive fence: %s %s %ssignalled\n",
> > fence->ops->get_driver_name(fence),
> > fence->ops->get_timeline_name(fence),
> > dma_fence_is_signaled(fence) ? "" : "un");
> > + dma_fence_put(fence);
> > + }
> > +
> > + rcu_read_lock();
> > for (i = 0; i < shared_count; i++) {
> > fence = rcu_dereference(fobj->shared[i]);
> > if (!dma_fence_get_rcu(fence))
> > continue;
> > + rcu_read_unlock();
> > seq_printf(s, "\tShared fence: %s %s %ssignalled\n",
> > fence->ops->get_driver_name(fence),
> > fence->ops->get_timeline_name(fence),
> > dma_fence_is_signaled(fence) ? "" : "un");
> > + dma_fence_put(fence);
> > + rcu_read_lock();
> > }
> > rcu_read_unlock();
> >
>
next prev parent reply other threads:[~2018-12-06 15:21 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-06 1:41 [PATCH] dma-buf: fix debugfs versus rcu and fence dumping jglisse
2018-12-06 8:09 ` Koenig, Christian
2018-12-06 15:21 ` Jerome Glisse [this message]
2018-12-06 15:21 ` Jerome Glisse
2018-12-06 15:21 ` Jerome Glisse
2018-12-06 16:08 ` Koenig, Christian
2018-12-06 16:08 ` Koenig, Christian
2018-12-06 16:19 ` Jerome Glisse
2018-12-06 16:19 ` Jerome Glisse
2018-12-07 13:30 ` Sasha Levin
2018-12-16 19:23 ` kbuild test robot
2018-12-16 19:23 ` kbuild test robot
2018-12-16 19:23 ` kbuild test robot
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20181206152116.GA3544@redhat.com \
--to=jglisse@redhat.com \
--cc=Christian.Koenig@amd.com \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=linaro-mm-sig@lists.linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=marcheu@chromium.org \
--cc=stable@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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.