From: Takashi Sakamoto <o-takashi@sakamocchi.jp>
To: Vaishali Thakkar <vaishali.thakkar@oracle.com>,
clemens@ladisch.de, tiwai@suse.de
Cc: alsa-devel@alsa-project.org, ffado-devel@lists.sf.net
Subject: Re: [PATCH 0/2] ALSA: fireworks/firewire-tascam: accessing to user space outside spinlock
Date: Tue, 30 Aug 2016 07:02:56 +0900 [thread overview]
Message-ID: <57C4B110.3070109@sakamocchi.jp> (raw)
In-Reply-To: <57C47194.40201@oracle.com>
[-- Attachment #1.1.1: Type: text/plain, Size: 1475 bytes --]
On Aug 30 2016 02:32, Vaishali Thakkar wrote:
>
>
> On Saturday 27 August 2016 02:20 AM, Takashi Sakamoto wrote:
>> Hi,
>>
>> In ALSA fireworks driver and firewire-tascam driver, current implementation
>> for hwdep interface have issues for page fault handling. For example,
>> when using single core processor, after executing lock_page() in page fault
>> handler and call task scheduler, then the context never run again, because
>> any interrupts are disabled by these drivers and the context can't catch
>> waiting event. This patchset fixes the issues.
>>
>> The issues were reported by Vaishali Thakkar, with a help of coccinelle.
>> Thanks a lot for his care to these minor drivers.
>> http://mailman.alsa-project.org/pipermail/alsa-devel/2016-August/111887.html
>
> Hi,
>
> Just a minor correction here. 'his -> her' :)
I apologize sincerely for my discourtesy...
>> Takashi Sakamoto (2):
>> ALSA: fireworks: accessing to user space outside spinlock
>> ALSA: firewire-tascam: accessing to user space outside spinlock
>>
>> sound/firewire/fireworks/fireworks_hwdep.c | 20 ++++++++++++++-----
>> sound/firewire/tascam/tascam-hwdep.c | 32 ++++++++++--------------------
>> 2 files changed, 25 insertions(+), 27 deletions(-)
This weekend, alsa-project.org is out of service, so I cannot post
revised version. As of this morning, it seems to start services so I'll
post them soon.
Thanks :)
Takashi Sakamoto
[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
prev parent reply other threads:[~2016-08-29 22:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-26 20:50 [PATCH 0/2] ALSA: fireworks/firewire-tascam: accessing to user space outside spinlock Takashi Sakamoto
2016-08-26 20:50 ` [PATCH 1/2] ALSA: fireworks: " Takashi Sakamoto
2016-08-26 20:50 ` Takashi Sakamoto
2016-08-26 21:34 ` [alsa-devel] " kbuild test robot
2016-08-27 1:50 ` Takashi Sakamoto
2016-08-26 20:50 ` [PATCH 2/2] ALSA: firewire-tascam: " Takashi Sakamoto
2016-08-26 20:50 ` Takashi Sakamoto
2016-08-26 21:30 ` [alsa-devel] " kbuild test robot
2016-08-29 17:32 ` [PATCH 0/2] ALSA: fireworks/firewire-tascam: " Vaishali Thakkar
2016-08-29 22:02 ` Takashi Sakamoto [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=57C4B110.3070109@sakamocchi.jp \
--to=o-takashi@sakamocchi.jp \
--cc=alsa-devel@alsa-project.org \
--cc=clemens@ladisch.de \
--cc=ffado-devel@lists.sf.net \
--cc=tiwai@suse.de \
--cc=vaishali.thakkar@oracle.com \
/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.