public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Frederic Weisbecker <fweisbec@gmail.com>
To: John Kacur <jkacur@redhat.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
	linux-kernel@vger.kernel.org,
	Thomas Gleixner <tglx@linutronix.de>,
	Jonathan Corbet <corbet@lwn.net>,
	Peter Zijlstra <a.p.zijlstra@chello.nl>,
	Christoph Hellwig <hch@infradead.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Vincent^M^J Sanders <vince@simtec.co.uk>,
	Ingo Molnar <mingo@elte.hu>
Subject: Re: [PATCH] sound_core.c: Remove BKL from soundcore_open
Date: Sun, 11 Oct 2009 13:33:21 +0200	[thread overview]
Message-ID: <20091011113317.GA4901@nowhere> (raw)
In-Reply-To: <alpine.LFD.2.00.0910110223510.4921@localhost.localdomain>

On Sun, Oct 11, 2009 at 02:25:53AM +0200, John Kacur wrote:
> 
> 
> On Sun, 11 Oct 2009, Alan Cox wrote:
> 
> > On Sun, 11 Oct 2009 01:24:14 +0200 (CEST)
> > John Kacur <jkacur@redhat.com> wrote:
> > 
> > > >From 030af455d4f54482130c8eccb47fe90aaba8808c Mon Sep 17 00:00:00 2001
> > > From: John Kacur <jkacur@redhat.com>
> > > Date: Sat, 10 Oct 2009 23:39:56 +0200
> > > Subject: [PATCH] This code is already protected by spin_lock, and doesn't require the bkl
> > 
> > Sorry but I don't think that is true becaue of:
> > 
> >            spin_unlock(&sound_loader_lock);
> >                 if(file->f_op->open)
> >                         err = file->f_op->open(inode,file);
> > 
> > 
> > So the underlying driver open method expects lock_kernel status and you
> > don't propogate it down. You really need to track down each thing that
> > can be called into here and fix it, or maybe just punt for the moment and
> > push it down to
> > 
> > 	{
> > 		lock_kernel()
> > 		err = file-f_op->open ...
> > 		unlock_kernel()
> > 	}
> > 
> > so its obvious to the next person who takes up the war on the BKL what is
> > to be tackled.
> > 
> 
> Yikes, I missed that. Still I'm loath to just push it down like that. I 
> wonder if I can use a mutex there. What about the following patch?
> 
> From 8b0b91523ee2fcf60ccd82dba44b8da8bad34ce4 Mon Sep 17 00:00:00 2001
> From: John Kacur <jkacur@redhat.com>
> Date: Sun, 11 Oct 2009 02:14:44 +0200
> Subject: [PATCH] Remove the bkl in soundcore_open
> 
> Remove the bkl in soundcore_open since it is mostly covered by the sound_loader_lock spin_lock
> 
> Protect the underlying driver open method with a mutex.
> 
> Signed-off-by: John Kacur <jkacur@redhat.com>
> ---
>  sound/sound_core.c |    8 ++++----
>  1 files changed, 4 insertions(+), 4 deletions(-)
> 
> diff --git a/sound/sound_core.c b/sound/sound_core.c
> index 49c9981..6afb6f1 100644
> --- a/sound/sound_core.c
> +++ b/sound/sound_core.c
> @@ -14,6 +14,8 @@
>  #include <linux/major.h>
>  #include <sound/core.h>
>  
> +static DEFINE_MUTEX(osc_mutex);
> +
>  #ifdef CONFIG_SOUND_OSS_CORE
>  static int __init init_oss_soundcore(void);
>  static void cleanup_oss_soundcore(void);
> @@ -576,8 +578,6 @@ static int soundcore_open(struct inode *inode, struct file *file)
>  	struct sound_unit *s;
>  	const struct file_operations *new_fops = NULL;
>  
> -	lock_kernel ();
> -
>  	chain=unit&0x0F;
>  	if(chain==4 || chain==5)	/* dsp/audio/dsp16 */
>  	{
> @@ -631,17 +631,17 @@ static int soundcore_open(struct inode *inode, struct file *file)
>  		file->f_op = new_fops;
>  		spin_unlock(&sound_loader_lock);
>  		if(file->f_op->open)
> +			mutex_lock(&osc_mutex);
>  			err = file->f_op->open(inode,file);
> +			mutex_unlock(&osc_mutex);


Yeah that's tempting, but I fear that also means this mutex will
never be removed....


  reply	other threads:[~2009-10-11 11:34 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-10 23:24 [PATCH] sound_core.c: Remove BKL from soundcore_open John Kacur
2009-10-10 23:42 ` Alan Cox
2009-10-11  0:25   ` John Kacur
2009-10-11 11:33     ` Frederic Weisbecker [this message]
2009-10-11 12:41       ` John Kacur
2009-10-11 14:12         ` Oliver Neukum
2009-10-11 20:40           ` Frederic Weisbecker
2009-10-11 21:25         ` John Kacur
2009-10-12  6:05         ` Takashi Iwai
2009-10-12  8:37           ` John Kacur
2009-10-12 10:17             ` Takashi Iwai
2009-10-12 10:42               ` John Kacur
2009-10-11 15:20     ` Jonathan Corbet
2009-10-11 17:15       ` Jonathan Corbet
2009-10-11 17:37         ` Arjan van de Ven
2009-10-11 19:17           ` Alan Cox
2009-10-11 19:26             ` Arjan van de Ven
2009-10-11 20:51               ` Alan Cox

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=20091011113317.GA4901@nowhere \
    --to=fweisbec@gmail.com \
    --cc=a.p.zijlstra@chello.nl \
    --cc=akpm@linux-foundation.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=corbet@lwn.net \
    --cc=hch@infradead.org \
    --cc=jkacur@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=tglx@linutronix.de \
    --cc=vince@simtec.co.uk \
    /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