From: Oliver Endriss <o.endriss@gmx.de>
To: Trent Piepho <xyzzy@speakeasy.org>
Cc: linux-media@vger.kernel.org, linux-dvb@linuxtv.org
Subject: Re: [linux-dvb] [BUG] changeset 9029 (http://linuxtv.org/hg/v4l-dvb/rev/aa3e5cc1d833)
Date: Wed, 18 Feb 2009 17:47:07 +0100 [thread overview]
Message-ID: <200902181747.07804@orion.escape-edv.de> (raw)
In-Reply-To: <Pine.LNX.4.58.0902171911060.24268@shell2.speakeasy.net>
Trent Piepho wrote:
> On Wed, 18 Feb 2009, Oliver Endriss wrote:
> > [1] If you want to lock a process against an interrupt handler,
> > - the process must use spin_lock_irq()
> > - the interrupt can use spin_lock()
> >
> > A routine has to use spin_lock_irqsave if (and only if) process and irq
> > call the routine concurrently. I do not see yet how this might happen.
>
> Some code calls the swfilter functions from process context and some
> drivers call them from interrupt context.
There would be a problem if (and only if) it could happen concurrently
within a given driver. A driver may call the functions either from
process context or from a tasklet/irq.
User space access will occur only if demux_source == DMX_MEMORY_FE.
In this case the driver must not call the routine.
If demux_source == DMX_FRONTEND, the driver may call the routine,
but userspace won't.
Sorry, I need more information to identify the problem.
CU
Oliver
--
----------------------------------------------------------------
VDR Remote Plugin 0.4.0: http://www.escape-edv.de/endriss/vdr/
----------------------------------------------------------------
next prev parent reply other threads:[~2009-02-18 16:48 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-02 1:46 [BUG] changeset 9029 (http://linuxtv.org/hg/v4l-dvb/rev/aa3e5cc1d833) e9hack
2009-02-02 3:38 ` Andy Walls
2009-02-15 12:36 ` Oliver Endriss
2009-02-15 14:07 ` [linux-dvb] " Andy Walls
2009-02-15 20:25 ` Andy Walls
2009-02-16 16:19 ` Trent Piepho
2009-02-16 16:33 ` [linux-dvb] " VDR User
2009-02-16 18:31 ` Mauro Carvalho Chehab
2009-02-16 19:13 ` [linux-dvb] " Steven Toth
2009-02-16 19:15 ` Steven Toth
2009-02-16 23:11 ` Andy Walls
2009-02-17 0:22 ` Trent Piepho
2009-02-17 15:16 ` Steven Toth
2009-02-17 16:47 ` Andreas Oberritter
2009-02-18 2:32 ` Trent Piepho
2009-02-18 15:07 ` Steven Toth
2009-02-18 20:45 ` Trent Piepho
2009-02-17 0:40 ` Oliver Endriss
2009-02-17 4:02 ` Andreas Oberritter
2009-02-18 2:04 ` [linux-dvb] " Oliver Endriss
2009-02-18 3:22 ` Trent Piepho
2009-02-18 16:47 ` Oliver Endriss [this message]
2009-02-18 12:51 ` Andreas Oberritter
2009-02-18 9:15 ` Trent Piepho
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=200902181747.07804@orion.escape-edv.de \
--to=o.endriss@gmx.de \
--cc=linux-dvb@linuxtv.org \
--cc=linux-media@vger.kernel.org \
--cc=xyzzy@speakeasy.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