From: David Henningsson <david.henningsson@canonical.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: [PATCH] udev: Allow ALSA input jacks to be accessed by the current
Date: Fri, 17 Jun 2011 06:17:07 +0000 [thread overview]
Message-ID: <4DFAF163.5030908@canonical.com> (raw)
In-Reply-To: <4DFA0F40.7000204@canonical.com>
On 2011-06-16 16:48, Takashi Iwai wrote:
> At Thu, 16 Jun 2011 16:28:08 +0200,
> Kay Sievers wrote:
>>
>> On Thu, Jun 16, 2011 at 16:12, David Henningsson
>> <david.henningsson@canonical.com> wrote:
>>> One missing piece for userspace (PulseAudio etc) to actually be able to use
>>> the jack input devices that ALSA create, is that these devices are
>>> accessible by root only. This patch makes the input device nodes accessible
>>> by the same users that can access the sound card: the current logged in
>>> user, as well as users in the audio group.
>>>
>>> One thing I was thinking about, was that the udev-acl rule actually grants
>>> read-write access to the input device node, where probably only read access
>>> is needed. Is this dangerous?
>>
>> Takashi, wasn't there already something else to use from ALSA than the
>> artificial input devices?
>
> These input devices are just notification from the sound driver at
> jack plugging, so basically it's read-only indeed, and setting the
> file permission RO would make sense.
>
> I can't judge more since I haven't seen the patch.
It was posted to alsa-devel (for comments) two days ago, see:
http://mailman.alsa-project.org/pipermail/alsa-devel/2011-June/040916.html
and
http://mailman.alsa-project.org/pipermail/alsa-devel/2011-June/040917.html
--
David Henningsson, Canonical Ltd.
http://launchpad.net/~diwic
next prev parent reply other threads:[~2011-06-17 6:17 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-16 14:12 [PATCH] udev: Allow ALSA input jacks to be accessed by the current David Henningsson
2011-06-16 14:28 ` [PATCH] udev: Allow ALSA input jacks to be accessed by the Kay Sievers
2011-06-16 14:48 ` [PATCH] udev: Allow ALSA input jacks to be accessed by the current user Takashi Iwai
2011-06-16 14:55 ` [PATCH] udev: Allow ALSA input jacks to be accessed by the Kay Sievers
2011-06-16 15:02 ` [PATCH] udev: Allow ALSA input jacks to be accessed by the current user Takashi Iwai
2011-06-17 6:17 ` David Henningsson [this message]
2011-06-17 6:20 ` Takashi Iwai
2011-06-17 11:27 ` [PATCH] udev: Allow ALSA input jacks to be accessed by the current David Henningsson
2011-06-17 12:31 ` [PATCH] udev: Allow ALSA input jacks to be accessed by the Lennart Poettering
2011-06-17 12:42 ` [PATCH] udev: Allow ALSA input jacks to be accessed by the current user Takashi Iwai
2011-06-17 12:45 ` [PATCH] udev: Allow ALSA input jacks to be accessed by the Lennart Poettering
2011-06-17 12:51 ` [PATCH] udev: Allow ALSA input jacks to be accessed by the current user Takashi Iwai
2011-06-17 13:00 ` [PATCH] udev: Allow ALSA input jacks to be accessed by the Lennart Poettering
2011-06-17 13:05 ` Kay Sievers
2011-06-17 13:10 ` [PATCH] udev: Allow ALSA input jacks to be accessed by the current user Takashi Iwai
2011-06-17 13:15 ` Takashi Iwai
2011-06-17 13:25 ` [PATCH] udev: Allow ALSA input jacks to be accessed by the Kay Sievers
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=4DFAF163.5030908@canonical.com \
--to=david.henningsson@canonical.com \
--cc=linux-hotplug@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 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).