stable.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jiri Slaby <jslaby@suse.cz>
To: Pan Xinhui <xinhuix.pan@intel.com>, stable@vger.kernel.org
Subject: Re: [PATCH V2] kernel/smp.c: fix a panic as cp->info is used wrongly and a, list corruption
Date: Tue, 30 Jun 2015 14:17:32 +0200	[thread overview]
Message-ID: <559288DC.5020401@suse.cz> (raw)
In-Reply-To: <5555B683.9070300@intel.com>

On 05/15/2015, 11:04 AM, Pan Xinhui wrote:
> this patch reverts commit 3440a1 which causes the regression and fix a
> list corruption.
> 
> base knowledge: kernel call cp->func using cp->info as its argument.
> like cp->func(cp->info);
> 
> current code is totally wrong, as 1) &softirq is at stack. 2) cp->info
> don't point to struct call_single_data.
> So in remote_softirq_receive,
> 1) If the caller had left __try_remote_softirq, dereferencing cp->info
> could not fetch the correct value.
> 2) And we can't get struct call_single_data *cp anymore.
> 
> The list corruption is below.
> __local_trigger will add cp->list into softirq_work_list. But no one
> will delete cp->list on behalf of us.
> if we can succeed to raise_softirq_irqoff, we must delete it from
> softirq_work_list. because we will lost control of pointer cp.
> cp is passed in and may be freed later in other places.
> 
> Signed-off-by: Pan Xinhui <xinhuix.pan@intel.com>
> ---
> Changes in v2:
>  no codes changed from v1, just update the comment.
>  upstream commit fc21c0 fix this issue, as it removes the total feature. :)
>  the buggy codes exist in v3.10 and v3.12.

Applied fc21c0cff2f425891b28ff6fb6b03b325c977428 to 3.12. Thanks.

-- 
js
suse labs

      parent reply	other threads:[~2015-06-30 12:17 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-15  9:04 [PATCH V2] kernel/smp.c: fix a panic as cp->info is used wrongly and a, list corruption Pan Xinhui
2015-05-14 12:50 ` Greg KH
2015-05-15 13:07   ` Pan Xinhui
2015-05-15 18:32     ` Greg KH
2015-06-30 12:17 ` Jiri Slaby [this message]

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=559288DC.5020401@suse.cz \
    --to=jslaby@suse.cz \
    --cc=stable@vger.kernel.org \
    --cc=xinhuix.pan@intel.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;
as well as URLs for NNTP newsgroup(s).