[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <477DC564.4050008@cosmosbay.com>
Date: Fri, 04 Jan 2008 06:34:28 +0100
From: Eric Dumazet <dada1@...mosbay.com>
To: David Miller <davem@...emloft.net>
CC: netdev@...r.kernel.org
Subject: Re: [ICMP]: Avoid sparse warnings in net/ipv4/icmp.c
David Miller a écrit :
> From: Eric Dumazet <dada1@...mosbay.com>
> Date: Fri, 04 Jan 2008 06:24:20 +0100
>
>> CHECK net/ipv4/icmp.c
>> net/ipv4/icmp.c:249:13: warning: context imbalance in 'icmp_xmit_unlock' -
>> unexpected unlock
>> net/ipv4/icmp.c:376:13: warning: context imbalance in 'icmp_reply' - different
>> lock contexts for basic block
>> net/ipv4/icmp.c:430:6: warning: context imbalance in 'icmp_send' - different
>> lock contexts for basic block
>>
>> Solution is to declare icmp_xmit_unlock() as __inline__ (similar with
>> icmp_xmit_lock())
>
> Please use "inline" instead of "__inline__". If other stuff
> uses __inline__ in that file, feel free to fix it up too.
>
You are right, here is the updated version
Thank you
[ICMP]: Avoid sparse warnings in net/ipv4/icmp.c
CHECK net/ipv4/icmp.c
net/ipv4/icmp.c:249:13: warning: context imbalance in 'icmp_xmit_unlock' -
unexpected unlock
net/ipv4/icmp.c:376:13: warning: context imbalance in 'icmp_reply' - different
lock contexts for basic block
net/ipv4/icmp.c:430:6: warning: context imbalance in 'icmp_send' - different
lock contexts for basic block
Solution is to declare both icmp_xmit_lock() and icmp_xmit_unlock() as inline
Signed-off-by: Eric Dumazet <dada1@...mosbay.com>
net/ipv4/icmp.c | 4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
View attachment "icmp.patch" of type "text/plain" (635 bytes)
Powered by blists - more mailing lists