Lock-annotate some kernel functions as an example of how it works.

In particular, a function that is called with a lock held, and
releases it only to re-acquire it needs to be annotated as such,
since otherwise sparse will complain about an unexpected unlock,
even though "globally" the lock is constant over the call.

1 files changed, 1 insertions, 0 deletions

diff --git a/init/main.c b/init/main.c
index e448aea6300090..4b20c9303bd4f7 100644
--- a/init/main.c
+++ b/init/main.c
@@ -441,6 +441,7 @@ static void __init smp_init(void)
  */
 
 static void noinline rest_init(void)
+	__releases(kernel_lock)
 {
 	kernel_thread(init, NULL, CLONE_FS | CLONE_SIGHAND);
 	numa_default_policy();