mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Bart Van Assche <bvanassche@acm.org>
To: Waiman Long <longman@redhat.com>,
	Peter Zijlstra <peterz@infradead.org>,
	Ingo Molnar <mingo@redhat.com>, Will Deacon <will.deacon@arm.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] locking/lockdep: Fix potential buffer overrun problem in stack_trace[]
Date: Thu, 19 Dec 2019 18:57:13 -0800	[thread overview]
Message-ID: <0cdfb26d-7faa-9da0-05b9-79bb21703283@acm.org> (raw)
In-Reply-To: <20191219182812.20191-1-longman@redhat.com>

On 2019-12-19 10:28, Waiman Long wrote:
> If the lockdep code is really running out of the stack_trace entries,
> there is a possiblity that buffer overrun can happen and corrupt the
             ^^^^^^^^^^
             possibility?
> data immediately after stack_trace[].
> 
> If there is less than LOCK_TRACE_SIZE_IN_LONGS entries left before
> the call to save_trace(), the max_entries computation will leave it
> with a very large positive number because of its unsigned nature. The
> subsequent call to stack_trace_save() will then corrupt the data after
> stack_trace[]. Fix that by changing max_entries to a signed integer
> and check for negative value before calling stack_trace_save().
> 
> Fixes: 12593b7467f9 ("locking/lockdep: Reduce space occupied by stack traces")
> Signed-off-by: Waiman Long <longman@redhat.com>
> ---
>  kernel/locking/lockdep.c | 7 +++----
>  1 file changed, 3 insertions(+), 4 deletions(-)
> 
> diff --git a/kernel/locking/lockdep.c b/kernel/locking/lockdep.c
> index 32282e7112d3..56e260a7582f 100644
> --- a/kernel/locking/lockdep.c
> +++ b/kernel/locking/lockdep.c
> @@ -482,7 +482,7 @@ static struct lock_trace *save_trace(void)
>  	struct lock_trace *trace, *t2;
>  	struct hlist_head *hash_head;
>  	u32 hash;
> -	unsigned int max_entries;
> +	int max_entries;
>  
>  	BUILD_BUG_ON_NOT_POWER_OF_2(STACK_TRACE_HASH_SIZE);
>  	BUILD_BUG_ON(LOCK_TRACE_SIZE_IN_LONGS >= MAX_STACK_TRACE_ENTRIES);
> @@ -490,10 +490,8 @@ static struct lock_trace *save_trace(void)
>  	trace = (struct lock_trace *)(stack_trace + nr_stack_trace_entries);
>  	max_entries = MAX_STACK_TRACE_ENTRIES - nr_stack_trace_entries -
>  		LOCK_TRACE_SIZE_IN_LONGS;
> -	trace->nr_entries = stack_trace_save(trace->entries, max_entries, 3);
>  
> -	if (nr_stack_trace_entries >= MAX_STACK_TRACE_ENTRIES -
> -	    LOCK_TRACE_SIZE_IN_LONGS - 1) {
> +	if (max_entries < 0) {
>  		if (!debug_locks_off_graph_unlock())
>  			return NULL;
>  
> @@ -502,6 +500,7 @@ static struct lock_trace *save_trace(void)
>  
>  		return NULL;
>  	}
> +	trace->nr_entries = stack_trace_save(trace->entries, max_entries, 3);
>  
>  	hash = jhash(trace->entries, trace->nr_entries *
>  		     sizeof(trace->entries[0]), 0);

I'm not sure whether it is useful to call stack_trace_save() if
max_entries == 0. How about changing the "max_entries < 0" test into
"max_entries <= 0"?

Thanks,

Bart.



  reply	other threads:[~2019-12-20  2:58 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-19 18:28 Waiman Long
2019-12-20  2:57 ` Bart Van Assche [this message]
2019-12-20 13:34   ` Waiman Long

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=0cdfb26d-7faa-9da0-05b9-79bb21703283@acm.org \
    --to=bvanassche@acm.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=longman@redhat.com \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.org \
    --cc=will.deacon@arm.com \
    /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®