public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Takashi Iwai <tiwai@suse.de>
Cc: Jaroslav Kysela <perex@perex.cz>,
	alsa-devel@alsa-project.org, arnd@arndb.de,
	keescook@chromium.org, bgoswami@codeaurora.org, sr@denx.de,
	gustavo@embeddedor.com, philburk@google.com, willy@infradead.org,
	mchehab+samsung@kernel.org, sboyd@kernel.org, vkoul@kernel.org,
	Baolin Wang <baolin.wang@linaro.org>,
	daniel.thompson@linaro.org, leo.yan@linaro.org,
	mathieu.poirier@linaro.org, srinivas.kandagatla@linaro.org,
	anna-maria@linutronix.de, corbet@lwn.net, jmiller@neverware.com,
	ckeepax@opensource.wolfsonmicro.com, joe@perches.com,
	o-takashi@sakamocchi.jp, colyli@suse.de,
	linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH] ALSA: core: Add DMA share buffer support
Date: Mon, 21 Jan 2019 12:40:53 +0000	[thread overview]
Message-ID: <20190121124053.GA12679@sirena.org.uk> (raw)
In-Reply-To: <s5hzhrxzrez.wl-tiwai@suse.de>

[-- Attachment #1: Type: text/plain, Size: 1093 bytes --]

On Fri, Jan 18, 2019 at 08:39:32PM +0100, Takashi Iwai wrote:
> Mark Brown wrote:

> > > multiple tasks). I would probably go in this way and add more extended
> > > permission control for the PCM device, so permissions can be restricted
> > > for the passed descriptor to the producer or the consumer task. In this

> > One concern I have with doing some ALSA-specific custom permissions
> > thing is integration with frameworks like SELinux (they'd presumably
> > need to learn about the ALSA specific stuff to manage it).  It also

> Well, I wonder what makes it more difficult by the approach Jaroslav
> suggested.  With O_APPEND, you can just call mmap() normally, and
> that's all. What's the merit of dma-buf approach wrt the security?

It was the bit about adding more extended permission control that I was
worried about there, not the initial O_APPEND bit.  Indeed the O_APPEND
bit sounds like it might also work from the base buffer sharing point of
view, I have to confess I'd not heard of that feature before (it didn't
come up in the discussion when Eric raised this in Prague).

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2019-01-21 12:41 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-18  4:55 [RFC PATCH] ALSA: core: Add DMA share buffer support Baolin Wang
2019-01-18  9:35 ` Jaroslav Kysela
2019-01-18 19:08   ` Mark Brown
2019-01-18 19:39     ` Takashi Iwai
2019-01-21 12:40       ` Mark Brown [this message]
2019-01-21 14:15         ` Jaroslav Kysela
2019-01-22 20:25           ` Mark Brown
2019-01-23 11:58             ` Takashi Iwai
2019-01-23 12:46               ` Leo Yan
2019-01-24 13:43                 ` Jaroslav Kysela
2019-01-24 17:33                   ` Mark Brown
2019-01-25  9:25                   ` Baolin Wang
2019-01-25 10:10                     ` Takashi Iwai
2019-01-25 10:20                       ` Takashi Iwai
2019-01-25 11:24                         ` Baolin Wang
2019-01-25 13:04                           ` Takashi Iwai
2019-01-28  5:48                             ` Baolin Wang
2019-01-25 11:11                       ` Baolin Wang
2019-01-25 13:03                         ` Takashi Iwai
2019-01-28  5:47                           ` Baolin Wang
2019-01-25 13:19                 ` [alsa-devel] " Takashi Iwai
2019-01-25 18:25                   ` Mark Brown
2019-01-28 13:31                     ` Jaroslav Kysela
2019-01-28 14:14                       ` Takashi Iwai

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=20190121124053.GA12679@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=alsa-devel@alsa-project.org \
    --cc=anna-maria@linutronix.de \
    --cc=arnd@arndb.de \
    --cc=baolin.wang@linaro.org \
    --cc=bgoswami@codeaurora.org \
    --cc=ckeepax@opensource.wolfsonmicro.com \
    --cc=colyli@suse.de \
    --cc=corbet@lwn.net \
    --cc=daniel.thompson@linaro.org \
    --cc=gustavo@embeddedor.com \
    --cc=jmiller@neverware.com \
    --cc=joe@perches.com \
    --cc=keescook@chromium.org \
    --cc=leo.yan@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mathieu.poirier@linaro.org \
    --cc=mchehab+samsung@kernel.org \
    --cc=o-takashi@sakamocchi.jp \
    --cc=perex@perex.cz \
    --cc=philburk@google.com \
    --cc=sboyd@kernel.org \
    --cc=sr@denx.de \
    --cc=srinivas.kandagatla@linaro.org \
    --cc=tiwai@suse.de \
    --cc=vkoul@kernel.org \
    --cc=willy@infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox