netdev
[Top] [All Lists]

Re: [PATCH] convert ircomm to seq_file interface

To: Stephen Hemminger <shemminger@xxxxxxxx>
Subject: Re: [PATCH] convert ircomm to seq_file interface
From: Jean Tourrilhes <jt@xxxxxxxxxxxxxxxxxx>
Date: Mon, 18 Aug 2003 13:09:23 -0700
Address: HP Labs, 1U-17, 1501 Page Mill road, Palo Alto, CA 94304, USA.
Cc: "David S. Miller" <davem@xxxxxxxxxx>, irda-users@xxxxxxxxxxxxxxxxxxxxx, netdev@xxxxxxxxxxx
E-mail: jt@hpl.hp.com
In-reply-to: <20030818123142.6369fbff.shemminger@osdl.org>
Organisation: HP Labs Palo Alto
References: <20030818123142.6369fbff.shemminger@osdl.org>
Reply-to: jt@xxxxxxxxxx
Sender: netdev-bounce@xxxxxxxxxxx
User-agent: Mutt/1.3.28i
On Mon, Aug 18, 2003 at 12:31:42PM -0700, Stephen Hemminger wrote:
> Convert ircomm /proc interface to seq_file.
> 
> Note: don't need spin_lock_irq because list is not ever locked
> from inside interrupt context.

        I don't agree with this change.
        If you look in ircomm_lmp.c ; ircomm_lmp_flow_control(), you
will see that the hashbin is accessed from BH context. So, at minimum
it should be a spin_lock_bh().
        Currently, all the IrDA stack uses spin_lock_irqsave(), where
is fact a only spin_lock_bh() is needed. But, this is something that I
kept for 2.7.X, because I would rather make sure previous locking
changes are safe, before going to the next step. So, for consistency
with the rest of the IrDA stack and the code in hashbin, I would keep
the spin_lock_irqsave().
        What do you think ?

        On the other hand, the conversion to seq_file is badly needed,
because the current /proc code was known to be very buggy. Thanks for
doing that.

        Have fun...

        Jean


<Prev in Thread] Current Thread [Next in Thread>