mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Paul E. McKenney" <paulmck@kernel.org>
To: Jules Irenge <jbi.octave@gmail.com>
Cc: rcu@vger.kernel.org, linux-kernel@vger.kernel.org, tglx@linutronix.de
Subject: Re: [PATCH 0/5] Lock warning clean up
Date: Tue, 21 Jan 2020 17:26:30 -0800	[thread overview]
Message-ID: <20200122012630.GE2935@paulmck-ThinkPad-P72> (raw)
In-Reply-To: <20200120223515.51287-1-jbi.octave@gmail.com>

On Mon, Jan 20, 2020 at 10:35:15PM +0000, Jules Irenge wrote:
> This patch series adds missing annotations to functions that register warnings of context imbalance when built with Sparse tool.
> The adds fix these warnings and give insight on what the functions are actually doing.
> In the core kernel,
> 
> 1. IRQ and RCU subsystems: exactly patch 1 and 3,  __releases() annotations were added as these functions exit the critical section
> 2. RCU subsystem again, patch 2 and 4, __acquire() annotations were added as the functions allow entry to the critical section.
> 3. TIME subsystem, patch 5 where lock is held at entry and exit of the function, an __must_hold() annotation was added.

Queued for review and testing, thank you!

I edited the commit logs, so please check to make sure that I did not
mess something up.

							Thanx, Paul

> Jules Irenge (5):
>   irq: Add  missing annotation for __irq_put_desc_unlock()
>   rcu: Add missing annotation for exit_tasks_rcu_start()
>   rcu: Add missing annotation for exit_tasks_rcu_finish()
>   rcu: Add missing annotation for rcu_nocb_bypass_lock()
>   time: Add missing annotation for __run_timer()
> 
>  kernel/irq/irqdesc.c     | 1 +
>  kernel/rcu/tree_plugin.h | 1 +
>  kernel/rcu/update.c      | 4 ++--
>  kernel/time/hrtimer.c    | 2 +-
>  4 files changed, 5 insertions(+), 3 deletions(-)
> 
> -- 
> 2.24.1
> 

  reply	other threads:[~2020-01-22  1:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-20 22:35 Jules Irenge
2020-01-22  1:26 ` Paul E. McKenney [this message]
2020-01-25  1:44   ` Jules Irenge

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20200122012630.GE2935@paulmck-ThinkPad-P72 \
    --to=paulmck@kernel.org \
    --cc=jbi.octave@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rcu@vger.kernel.org \
    --cc=tglx@linutronix.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®