From: Daniel Drake <ddrake@brontes3d.com>
To: Stefan Richter <stefanr@s5r6.in-berlin.de>
Cc: linux1394-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org, ak@suse.de
Subject: Re: Unnecessary BKL contention in video1394
Date: Thu, 19 Oct 2006 09:19:38 -0400 [thread overview]
Message-ID: <1161263978.2845.6.camel@systems03.lan.brontes3d.com> (raw)
In-Reply-To: <45369E69.30007@s5r6.in-berlin.de>
On Wed, 2006-10-18 at 23:36 +0200, Stefan Richter wrote:
> (added Cc: lkml to pull in some clues)
>
> Daniel Drake wrote at linux1394-devel:
> > Hi,
> >
> > I noticed that video1394 calls lock_kernel in it's file_operations. I
> > thought about converting these into a per-instance mutex or something,
> > but in the end I couldn't find a reason why this locking is needed. (The
> > more important I/O system is protected by separate spinlocks)
> >
> > The BKL is only contended when operations such as ioctl() or release()
> > are invoked. My knowledge lacks at this point, but I'm reasonably sure
> > that some upper layer must ensure that these invokations are serialized,
> > as opposed to leaving it up to the driver to handle nasty potential
> > situations e.g. release() being called halfway through a read(). Can
> > anyone clarify?
> I think you are right. Same with dv1394. Although we need to
> double-check whether something needs replacement protection then.
Adding Andi Kleen to CC, who added the BKL around __video1394_ioctl a
long while back (when converting video1394 to compat_ioctl).
I don't feel that any replacement protection is needed, since the
critical sections (where structures are used both in interrupts and in
file_operations) are already protected by spinlocks.
> > ------------------------------------------------------------------------
> >
> > Index: linux/drivers/ieee1394/video1394.c
> > ===================================================================
> > --- linux.orig/drivers/ieee1394/video1394.c
> > +++ linux/drivers/ieee1394/video1394.c
> > @@ -1161,9 +1161,7 @@ static int __video1394_ioctl(struct file
> > static long video1394_ioctl(struct file *file, unsigned int cmd, unsigned long arg)
> > {
> > int err;
> > - lock_kernel();
> > err = __video1394_ioctl(file, cmd, arg);
> > - unlock_kernel();
> > return err;
> > }
> >
> > @@ -1181,13 +1179,11 @@ static int video1394_mmap(struct file *f
> > struct file_ctx *ctx = (struct file_ctx *)file->private_data;
> > int res = -EINVAL;
> >
> > - lock_kernel();
> > if (ctx->current_ctx == NULL) {
> > PRINT(KERN_ERR, ctx->ohci->host->id,
> > "Current iso context not set");
> > } else
> > res = dma_region_mmap(&ctx->current_ctx->dma, file, vma);
> > - unlock_kernel();
> >
> > return res;
> > }
> > @@ -1200,7 +1196,6 @@ static unsigned int video1394_poll(struc
> > struct dma_iso_ctx *d;
> > int i;
> >
> > - lock_kernel();
> > ctx = file->private_data;
> > d = ctx->current_ctx;
> > if (d == NULL) {
> > @@ -1221,7 +1216,6 @@ static unsigned int video1394_poll(struc
> > }
> > spin_unlock_irqrestore(&d->lock, flags);
> > done:
> > - unlock_kernel();
> >
> > return mask;
> > }
> > @@ -1257,7 +1251,6 @@ static int video1394_release(struct inod
> > struct list_head *lh, *next;
> > u64 mask;
> >
> > - lock_kernel();
> > list_for_each_safe(lh, next, &ctx->context_list) {
> > struct dma_iso_ctx *d;
> > d = list_entry(lh, struct dma_iso_ctx, link);
> > @@ -1278,7 +1271,6 @@ static int video1394_release(struct inod
> > kfree(ctx);
> > file->private_data = NULL;
> >
> > - unlock_kernel();
> > return 0;
> > }
> >
> >
>
next prev parent reply other threads:[~2006-10-19 13:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1161203487.28713.8.camel@systems03.lan.brontes3d.com>
2006-10-18 21:36 ` Stefan Richter
2006-10-19 13:19 ` Daniel Drake [this message]
2006-10-19 13:27 ` Andi Kleen
2006-10-19 14:36 ` Stefan Richter
2006-10-19 15:31 ` Daniel Drake
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=1161263978.2845.6.camel@systems03.lan.brontes3d.com \
--to=ddrake@brontes3d.com \
--cc=ak@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux1394-devel@lists.sourceforge.net \
--cc=stefanr@s5r6.in-berlin.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
all inboxes | Powered by JetHome®