[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <7222772aed3bf4651dc4ed580ade3e6bd33b253d.camel@linux.ibm.com>
Date: Thu, 30 Sep 2021 15:46:52 -0400
From: Mimi Zohar <zohar@...ux.ibm.com>
To: liqiong <liqiong@...china.com>, Simon.THOBY@...eris.fr
Cc: dmitry.kasatkin@...il.com, jmorris@...ei.org, serge@...lyn.com,
linux-integrity@...r.kernel.org,
linux-security-module@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] ima: fix deadlock when traversing "ima_default_rules".
Hi Liqiong,
On Sat, 2021-09-18 at 11:11 +0800, liqiong wrote:
> The current IMA ruleset is identified by the variable "ima_rules"
> that default to "&ima_default_rules". When loading a custom policy
> for the first time, the variable is updated to "&ima_policy_rules"
> instead. That update isn't RCU-safe, and deadlocks are possible.
> Indeed, some functions like ima_match_policy() may loop indefinitely
> when traversing "ima_default_rules" with list_for_each_entry_rcu().
>
> When iterating over the default ruleset back to head, if the list
> head is "ima_default_rules", and "ima_rules" have been updated to
> "&ima_policy_rules", the loop condition (&entry->list != ima_rules)
> stays always true, traversing won't terminate, causing a soft lockup
> and RCU stalls.
>
> Introduce a temporary value for "ima_rules" when iterating over
> the ruleset to avoid the deadlocks.
>
> Signed-off-by: liqiong <liqiong@...china.com>
> Reviewed-by: THOBY Simon <Simon.THOBY@...eris.fr>
> Fixes: 38d859f991f3 ("IMA: policy can now be updated multiple times")
> Signed-off-by: Mimi Zohar <zohar@...ux.ibm.com>
> Reported-by: kernel test robot <lkp@...el.com>
> Fix sparse: incompatible types in comparison expression.
The "Fix sparse" line shouldn't be on a separate line. Either post the
one line fix as a separate patch using the normal "Fixes:" tag or fix
the "Reported-by" line, as previously suggested.
thanks,
Mimi
Powered by blists - more mailing lists