From: Sumit Semwal <sumit.semwal@linaro.org>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: "open list:DMA BUFFER SHARING FRAMEWORK"
<linux-media@vger.kernel.org>,
DRI mailing list <dri-devel@lists.freedesktop.org>,
Daniel Vetter <daniel@ffwll.ch>, Chenbo Feng <fengc@google.com>,
LKML <linux-kernel@vger.kernel.org>,
Linaro MM SIG <linaro-mm-sig@lists.linaro.org>,
Charan Teja Reddy <charante@codeaurora.org>,
syzbot+3643a18836bce555bff6@syzkaller.appspotmail.com,
"# 3.4.x" <stable@vger.kernel.org>, Arnd Bergmann <arnd@arndb.de>
Subject: Re: [PATCH v2] dma-buf: Move dma_buf_release() from fops to dentry_ops
Date: Tue, 16 Jun 2020 18:32:31 +0530 [thread overview]
Message-ID: <CAO_48GE8K_nDXs_LDU9caRdP-aK9DWV3vXcD4EuVCxyShCBbmg@mail.gmail.com> (raw)
In-Reply-To: <159231181752.18853.1290700688849491922@build.alporthouse.com>
Hi Chris,
On Tue, 16 Jun 2020 at 18:20, Chris Wilson <chris@chris-wilson.co.uk> wrote:
>
> Quoting Sumit Semwal (2020-06-16 13:42:13)
> > Hello,
> >
> > If there are no objections to this, I will plan to merge it soon.
>
> I was going to suggest running it against our CI, but that's unavailable
> at the moment.
>
> There's a particularly nasty BUG_ON() in dma_buf_release that we hit
> irregularly, that this might help with.
Thanks for your reply; if the CI is going to be available in a couple
of days, we could wait - it'd be definitely good to see a bug being
splattered out!
> -Chris
Best,
Sumit.
next prev parent reply other threads:[~2020-06-16 13:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-11 11:44 [PATCH v2] dma-buf: Move dma_buf_release() from fops to dentry_ops Sumit Semwal
2020-06-16 12:42 ` Sumit Semwal
2020-06-16 12:50 ` Chris Wilson
2020-06-16 13:02 ` Sumit Semwal [this message]
2020-06-16 13:43 ` Charan Teja Kalla
2020-06-22 6:34 ` Sumit Semwal
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=CAO_48GE8K_nDXs_LDU9caRdP-aK9DWV3vXcD4EuVCxyShCBbmg@mail.gmail.com \
--to=sumit.semwal@linaro.org \
--cc=arnd@arndb.de \
--cc=charante@codeaurora.org \
--cc=chris@chris-wilson.co.uk \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=fengc@google.com \
--cc=linaro-mm-sig@lists.linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=syzbot+3643a18836bce555bff6@syzkaller.appspotmail.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).