From: Julian Scheel <julian@jusst.de>
To: Takashi Iwai <tiwai@suse.de>, Jaroslav Kysela <perex@perex.cz>
Cc: alsa-devel@alsa-project.org
Subject: Re: [PATCH] alsactl: Store lockfile in /tmp
Date: Tue, 06 May 2014 20:55:40 +0200 [thread overview]
Message-ID: <5369302C.4040502@jusst.de> (raw)
In-Reply-To: <s5h61ljuevj.wl%tiwai@suse.de>
Am 06/05/14 17:05, schrieb Takashi Iwai:
> At Tue, 06 May 2014 16:53:00 +0200,
> Jaroslav Kysela wrote:
>>
>> Date 6.5.2014 13:57, Julian Scheel wrote:
>>> It can not be generally assumed that the directories in which asound.state
>>> resides are writable. Instead using /tmp as location for lock files seems more
>>> reliable.
>>
>> Apart the missing free for the mallocated string and ommiting the TMPDIR
>> environment variable, I think that the right directory for global locks
>> is /var/lock . The default asound.state directory is now /var/lib/alsa -
>> I don't see the benefit.
>
> Agreed. Above all, using a fixed path with /tmp is really fragile,
> easily leading to a security risk for a service that is run by root
> like this.
I agree that /tmp is not the best choice. It was just what came to my
mind first when thinking of a place where r/w access shall be possible
in any system.
>> What's the reason for this change? Perhaps using an environmental
>> variable to override the lock path may be more appropriate for a custom
>> directory structure.
>
> ... or give an option?
What about using /var/lock as default, allowing to explicitly override
with an option?
I think this would be more correct than the current approach.
-Julian
>>
>> Jaroslav
>>
>>>
>>> Signed-off-by: Julian Scheel <julian@jusst.de>
>>> ---
>>> alsactl/lock.c | 13 ++++++++++---
>>> 1 file changed, 10 insertions(+), 3 deletions(-)
>>>
>>> diff --git a/alsactl/lock.c b/alsactl/lock.c
>>> index 587a109..7ca3a09 100644
>>> --- a/alsactl/lock.c
>>> +++ b/alsactl/lock.c
>>> @@ -36,17 +36,24 @@ static int state_lock_(const char *file, int lock, int timeout)
>>> struct flock lck;
>>> struct stat st;
>>> char lcktxt[12];
>>> + char *filename;
>>> char *nfile;
>>>
>>> if (!do_lock)
>>> return 0;
>>> - nfile = malloc(strlen(file) + 6);
>>> +
>>> + /* only use the actual filename, not the path */
>>> + filename = strrchr(file, '/');
>>> + if (!filename)
>>> + filename = file;
>>> +
>>> + nfile = malloc(strlen(filename) + 10);
>>> if (nfile == NULL) {
>>> error("No enough memory...");
>>> return -ENOMEM;
>>> }
>>> - strcpy(nfile, file);
>>> - strcat(nfile, ".lock");
>>> +
>>> + sprintf(nfile, "/tmp/%s.lock", filename);
>>> lck.l_type = lock ? F_WRLCK : F_UNLCK;
>>> lck.l_whence = SEEK_SET;
>>> lck.l_start = 0;
>>>
>>
>>
>> --
>> Jaroslav Kysela <perex@perex.cz>
>> Linux Kernel Sound Maintainer
>> ALSA Project; Red Hat, Inc.
>> _______________________________________________
>> Alsa-devel mailing list
>> Alsa-devel@alsa-project.org
>> http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
>>
> _______________________________________________
> Alsa-devel mailing list
> Alsa-devel@alsa-project.org
> http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
>
prev parent reply other threads:[~2014-05-06 18:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-06 11:57 [PATCH] alsactl: Store lockfile in /tmp Julian Scheel
2014-05-06 14:53 ` Jaroslav Kysela
2014-05-06 14:55 ` Jaroslav Kysela
2014-05-06 15:00 ` Julian Scheel
2014-05-06 16:44 ` Takashi Iwai
2014-05-06 15:05 ` Takashi Iwai
2014-05-06 18:55 ` Julian Scheel [this message]
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=5369302C.4040502@jusst.de \
--to=julian@jusst.de \
--cc=alsa-devel@alsa-project.org \
--cc=perex@perex.cz \
--cc=tiwai@suse.de \
/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.