public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Samuel Ortiz <samuel@sortiz.org>
To: Peter Zijlstra <a.p.zijlstra@chello.nl>
Cc: Andrey Borzenkov <arvidjaar@mail.ru>,
	Andrew Morton <akpm@osdl.org>,
	irda-users@lists.sourceforge.net, linux-kernel@vger.kernel.org,
	Ingo Molnar <mingo@elte.hu>, arjan <arjan@infradead.org>,
	John Platt <jplatt39@gmail.com>
Subject: Re: [PATCH] lockdep: annotate irda warning
Date: Fri, 24 Nov 2006 22:14:29 +0200	[thread overview]
Message-ID: <20061124201428.GA4261@sortiz.org> (raw)
In-Reply-To: <1164014139.5968.138.camel@twins>

Hi guys,

On Mon, Nov 20, 2006 at 10:15:39AM +0100, Peter Zijlstra wrote:
>
> So, under the assumption the author was right, it just needs a lockdep
> annotation.
> 
> (depends on patches in -mm for spin_lock_irqsave_nested())
> 
> Signed-off-by: Peter Zijlstra <a.p.zijlstra@chello.nl>
> ---
>  net/irda/irlmp.c |    3 ++-
>  1 file changed, 2 insertions(+), 1 deletion(-)
> 
> Index: linux-2.6-mm/net/irda/irlmp.c
> ===================================================================
> --- linux-2.6-mm.orig/net/irda/irlmp.c	2006-11-20 09:54:50.000000000 +0100
> +++ linux-2.6-mm/net/irda/irlmp.c	2006-11-20 10:12:11.000000000 +0100
> @@ -1678,7 +1678,8 @@ static int irlmp_slsap_inuse(__u8 slsap_
>  	 *  every IrLAP connection and check every LSAP associated with each
>  	 *  the connection.
>  	 */
> -	spin_lock_irqsave(&irlmp->links->hb_spinlock, flags);
> +	spin_lock_irqsave_nested(&irlmp->links->hb_spinlock, flags,
> +			SINGLE_DEPTH_NESTING);
>  	lap = (struct lap_cb *) hashbin_get_first(irlmp->links);
>  	while (lap != NULL) {
>  		IRDA_ASSERT(lap->magic == LMP_LAP_MAGIC, goto errlap;);

This patch got pushed into mainline, while the spin_lock_irq_save_nested()
patches are not there yet. It breaks IrDA as irlmp.c doesn't build.
Linus, could you please revert the corresponding commit
(700f9672c9a61c12334651a94d17ec04620e1976) unless you are planning to pull
the spin_lock_irq_save_nested() patches soon from -mm ?
Thanks a lot in advance.

Cheers,
Samuel.

      reply	other threads:[~2006-11-24 20:13 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-18 13:12 2.6.19-rc5: lockdep warnings starting irattach Andrey Borzenkov
2006-11-20  9:04 ` Peter Zijlstra
2006-11-20  9:12   ` Ingo Molnar
2006-11-20  9:15 ` [PATCH] lockdep: annotate irda warning Peter Zijlstra
2006-11-24 20:14   ` Samuel Ortiz [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=20061124201428.GA4261@sortiz.org \
    --to=samuel@sortiz.org \
    --cc=a.p.zijlstra@chello.nl \
    --cc=akpm@osdl.org \
    --cc=arjan@infradead.org \
    --cc=arvidjaar@mail.ru \
    --cc=irda-users@lists.sourceforge.net \
    --cc=jplatt39@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    /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