From: Mark Brown <broonie@kernel.org>
To: Takashi Iwai <tiwai@suse.de>
Cc: Leo Yan <leo.yan@linaro.org>,
alsa-devel@alsa-project.org, bgoswami@codeaurora.org,
gustavo@embeddedor.com, srinivas.kandagatla@linaro.org,
mchehab+samsung@kernel.org, sr@denx.de,
daniel.thompson@linaro.org, corbet@lwn.net, philburk@google.com,
willy@infradead.org, jmiller@neverware.com,
keescook@chromium.org, arnd@arndb.de, colyli@suse.de,
ckeepax@opensource.wolfsonmicro.com, anna-maria@linutronix.de,
mathieu.poirier@linaro.org, Baolin Wang <baolin.wang@linaro.org>,
sboyd@kernel.org, linux-kernel@vger.kernel.org, vkoul@kernel.org,
joe@perches.com
Subject: Re: [alsa-devel] [RFC PATCH] ALSA: core: Add DMA share buffer support
Date: Fri, 25 Jan 2019 18:25:15 +0000 [thread overview]
Message-ID: <20190125182515.GD6939@sirena.org.uk> (raw)
In-Reply-To: <s5himyczxgl.wl-tiwai@suse.de>
[-- Attachment #1: Type: text/plain, Size: 806 bytes --]
On Fri, Jan 25, 2019 at 02:19:22PM +0100, Takashi Iwai wrote:
> Leo Yan wrote:
> > If we directly use the device node /dev/snd/ as file descriptor, even
> > though we specify flag O_EXCL when open it, but it still is not an
> > anon inode file descriptor. Thus this is not safe enough and will be
> > blocked by SELinux. On the other hand, this patch wants to use
> > dma-buf framework to provide file descriptor for the audio buffer, and
> > this audio buffer can be one of mutiple audio buffers in the system
> > and it can be shared to any audio client program.
> Hrm, it sounds like a workaround just to bypass SELinux check...
> The sound server can open another PCM stream with O_APPEND, and pass
> that fd to the client, too?
So long as we can teach SELinux that they're safe to export, yeah.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2019-01-25 18:25 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
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 [this message]
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=20190125182515.GD6939@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=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