All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pan Xinhui <xinhuix.pan@intel.com>
To: Greg KH <greg@kroah.com>
Cc: stable@vger.kernel.org
Subject: Re: [PATCH] kernel/smp.c: fix a panic as cp->info is used wrongly and a list corruption
Date: Fri, 15 May 2015 10:25:13 +0800	[thread overview]
Message-ID: <55555909.7050805@intel.com> (raw)
In-Reply-To: <20150512121459.GB25401@kroah.com>

hi,Greg
	thanks for your kind reply :)
I will send out patch V2 later. let me do some explanation here first.
this feature which I am working on is reverted totally by commit fc21c0 in upstream, maybe the author notice the code is buggy.
So I just fix it, not revert this feature here, big change is not accepted in stable kernel tree.

thanks again for your help.

thanks
xinhui

On 2015年05月12日 20:14, Greg KH wrote:
> On Wed, May 13, 2015 at 05:03:04PM +0800, Pan Xinhui wrote:
>> this patch reverts commit 3440a1ca99707f093e9568ba9762764d3162dd8f which causes the regression.
>>
>> 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 has lost control of pointer cp.
>> cp is passed in and may be freed later in other places.
>>
>> Cc: <stable@vger.kernel.org> # 3.10
>> Signed-off-by: xinhuix.pan <xinhuix.pan@intel.com>
>> ---
>>   include/linux/smp.h |  1 +
>>   kernel/softirq.c    | 10 +++++++---
>>   2 files changed, 8 insertions(+), 3 deletions(-)
>
> <formletter>
>
> This is not the correct way to submit patches for inclusion in the
> stable kernel tree.  Please read Documentation/stable_kernel_rules.txt
> for how to do this properly.
>
> </formletter>
>

      reply	other threads:[~2015-05-14  2:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-13  9:03 [PATCH] kernel/smp.c: fix a panic as cp->info is used wrongly and a list corruption Pan Xinhui
2015-05-12 12:14 ` Greg KH
2015-05-15  2:25   ` Pan Xinhui [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=55555909.7050805@intel.com \
    --to=xinhuix.pan@intel.com \
    --cc=greg@kroah.com \
    --cc=stable@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.