Received-SPF: pass (google.com: domain of linux-kernel+bounces-135324-linux.lists.archive=gmail.com@vger.kernel.org designates 147.75.80.249 as permitted sender) client-ip=147.75.80.249;
Precedence: bulk
MIME-Version: 1.0
From: Masahiro Yamada <masahiroy@kernel.org>
Date: Mon, 8 Apr 2024 21:33:18 +0900
Message-ID: <CAK7LNAR576NEto9ewk+OhGBfh6+xicB3KL-41gUkc5g_68UvJw@mail.gmail.com>
Subject: Question about context imbalance warning in sparse
To: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Content-Type: text/plain; charset="UTF-8"

Hi Luc,


Sparse does not seem to consider the first parameter
of __context__().

Sparse does not warn anything about this code.


void foo(void)
{
        __context__(a, 1);
        __context__(b, -1);
}


In Linux, I think sparse should warn
the following code
(lock and unlock different locks)


void foo(void)
{
        write_lock(&my_lock1);
        write_unlock(&my_lock2);
}


-- 
Best Regards
Masahiro Yamada