[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CADCM0GLFhoLW33sU0B_7QKFpTfVoUjcb5j_qpRhyY60B+VaCnw@mail.gmail.com>
Date: Sun, 7 Feb 2016 14:30:19 +0530
From: Niranjan Dighe <niranjan.dighe@...il.com>
To: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Cc: Oleg Drokin <oleg.drokin@...el.com>,
Andreas Dilger <andreas.dilger@...el.com>,
Mike Rapoport <mike.rapoport@...il.com>,
Jeremiah Mahler <jmmahler@...il.com>,
James Simmons <jsimmons@...radead.org>,
Haneen Mohammed <hamohammed.sa@...il.com>,
Mike Shuey <shuey@...due.edu>, Arnd Bergmann <arnd@...db.de>,
Al Viro <viro@...iv.linux.org.uk>,
lustre-devel@...ts.lustre.org, devel@...verdev.osuosl.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH] staging: lustre: Fix 'unexpected unlock' warning
generated by sparse
On Thu, Feb 4, 2016 at 3:53 AM, Greg Kroah-Hartman
<gregkh@...uxfoundation.org> wrote:
> On Sun, Jan 03, 2016 at 08:27:04AM +0530, Niranjan Dighe wrote:
>> Added annotation '__must_hold' to function ksocknal_send_keepalive_locked
>> which unlocks the lock ksocknal_data.ksnd_global_lock. As this lock is
>> not acquired in the current function, sparse warns about context imbalance
>>
>> Signed-off-by: Niranjan Dighe <niranjan.dighe@...il.com>
>> ---
>> drivers/staging/lustre/lnet/klnds/socklnd/socklnd_cb.c | 1 +
>> 1 file changed, 1 insertion(+)
>
> Doesn't apply to my tree :(
Sorry about this Greg, I will recreate it on the latest staging-next and resend.
Thanks,
Niranjan Dighe
Powered by blists - more mailing lists