From: Vaishali Thakkar <vaishali.thakkar@oracle.com>
To: Takashi Iwai <tiwai@suse.de>, Takashi Sakamoto <o-takashi@sakamocchi.jp>
Cc: clemens@ladisch.de, alsa-devel@alsa-project.org,
ffado-devel@lists.sf.net, stable@vger.kernel.org
Subject: Re: [PATCH v2 1/2] ALSA: fireworks: accessing to user space outside spinlock
Date: Tue, 30 Aug 2016 11:37:04 +0530 [thread overview]
Message-ID: <57C52288.4010502@oracle.com> (raw)
In-Reply-To: <s5ha8fu4yv7.wl-tiwai@suse.de>
On Tuesday 30 August 2016 10:49 AM, Takashi Iwai wrote:
> On Tue, 30 Aug 2016 01:01:34 +0200,
> Takashi Sakamoto wrote:
>>
>> In hwdep interface of fireworks driver, accessing to user space is in a
>> critical section with disabled local interrupt. Depending on architecture,
>> accessing to user space can cause page fault exception. Then local
>> processor stores machine status and handles the synchronous event. A
>> handler corresponding to the event can call task scheduler to wait for
>> preparing pages. In a case of usage of single core processor, the state to
>> disable local interrupt is worse because it don't handle usual interrupts
>> from hardware.
>>
>> This commit fixes this bug, performing the accessing outside spinlock.
>>
>> Reported-by: Vaishali Thakkar <vaishali.thakkar@oracle.com>
>> Cc: stable@vger.kernel.org
>> Fixes: 555e8a8f7f14('ALSA: fireworks: Add command/response functionality into hwdep interface')
>> Signed-off-by: Takashi Sakamoto <o-takashi@sakamocchi.jp>
>> ---
>> sound/firewire/fireworks/fireworks_hwdep.c | 21 ++++++++++++++++-----
>> 1 file changed, 16 insertions(+), 5 deletions(-)
>>
>> diff --git a/sound/firewire/fireworks/fireworks_hwdep.c b/sound/firewire/fireworks/fireworks_hwdep.c
>> index 33df865..8ed4b29 100644
>> --- a/sound/firewire/fireworks/fireworks_hwdep.c
>> +++ b/sound/firewire/fireworks/fireworks_hwdep.c
>> @@ -38,6 +38,7 @@ hwdep_read_resp_buf(struct snd_efw *efw, char __user *buf, long remained,
>> buf += sizeof(type);
>>
>> /* write into buffer as many responses as possible */
>> + spin_lock_irq(&efw->lock);
>> while (efw->resp_queues > 0) {
>> t = (struct snd_efw_transaction *)(efw->pull_ptr);
>> length = be32_to_cpu(t->length) * sizeof(__be32);
>> @@ -52,9 +53,13 @@ hwdep_read_resp_buf(struct snd_efw *efw, char __user *buf, long remained,
>> (unsigned int)(efw->pull_ptr - efw->resp_buf);
>> till_end = min_t(unsigned int, length, till_end);
>>
>> + spin_unlock_irq(&efw->lock);
>> +
>> if (copy_to_user(buf, efw->pull_ptr, till_end))
>> return -EFAULT;
>>
>> + spin_lock_irq(&efw->lock);
>> +
>> efw->pull_ptr += till_end;
>
> Strictly speaking, this is still racy. efw->pull_ptr is accessed
> outside the spinlock, and it can be modified while copy_to_user() is
> being processed.
Should disabling pagefaults while interacting with user space work here?
>
> Takashi
>
>> if (efw->pull_ptr >= efw->resp_buf +
>> snd_efw_resp_buf_size)
>> @@ -69,6 +74,8 @@ hwdep_read_resp_buf(struct snd_efw *efw, char __user *buf, long remained,
>> efw->resp_queues--;
>> }
>>
>> + spin_unlock_irq(&efw->lock);
>> +
>> return count;
>> }
>>
>> @@ -76,14 +83,17 @@ static long
>> hwdep_read_locked(struct snd_efw *efw, char __user *buf, long count,
>> loff_t *offset)
>> {
>> - union snd_firewire_event event;
>> + union snd_firewire_event event = {
>> + .lock_status.type = SNDRV_FIREWIRE_EVENT_LOCK_STATUS,
>> + };
>>
>> - memset(&event, 0, sizeof(event));
>> + spin_lock_irq(&efw->lock);
>>
>> - event.lock_status.type = SNDRV_FIREWIRE_EVENT_LOCK_STATUS;
>> event.lock_status.status = (efw->dev_lock_count > 0);
>> efw->dev_lock_changed = false;
>>
>> + spin_unlock_irq(&efw->lock);
>> +
>> count = min_t(long, count, sizeof(event.lock_status));
>>
>> if (copy_to_user(buf, &event, count))
>> @@ -111,13 +121,14 @@ hwdep_read(struct snd_hwdep *hwdep, char __user *buf, long count,
>> spin_lock_irq(&efw->lock);
>> }
>>
>> + /* Loosely release the lock here, but still safe. */
>> + spin_unlock_irq(&efw->lock);
>> +
>> if (efw->dev_lock_changed)
>> count = hwdep_read_locked(efw, buf, count, offset);
>> else if (efw->resp_queues > 0)
>> count = hwdep_read_resp_buf(efw, buf, count, offset);
>>
>> - spin_unlock_irq(&efw->lock);
>> -
>> return count;
>> }
>>
>> --
>> 2.7.4
>>
--
Vaishali
next prev parent reply other threads:[~2016-08-30 6:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1472511695-29316-1-git-send-email-o-takashi@sakamocchi.jp>
2016-08-29 23:01 ` [PATCH v2 1/2] ALSA: fireworks: accessing to user space outside spinlock Takashi Sakamoto
2016-08-30 5:19 ` Takashi Iwai
2016-08-30 6:07 ` Vaishali Thakkar [this message]
2016-08-30 6:27 ` Takashi Sakamoto
2016-08-30 6:54 ` Takashi Iwai
2016-08-29 23:01 ` [PATCH v2 2/2] ALSA: firewire-tascam: " Takashi Sakamoto
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=57C52288.4010502@oracle.com \
--to=vaishali.thakkar@oracle.com \
--cc=alsa-devel@alsa-project.org \
--cc=clemens@ladisch.de \
--cc=ffado-devel@lists.sf.net \
--cc=o-takashi@sakamocchi.jp \
--cc=stable@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox