public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Stephen Powell <zlinuxman@wowway.com>
To: Heiko Carstens <heiko.carstens@de.ibm.com>
Cc: Jan Glauber <jang@linux.vnet.ibm.com>,
	Jonathan Nieder <jrnieder@gmail.com>,
	linux-s390@vger.kernel.org, linux-kernel@vger.kernel.org,
	622570@bugs.debian.org
Subject: Re: [OOPS s390] Unable to handle kernel pointer dereference at virtual kernel address (null)
Date: Wed, 20 Apr 2011 22:34:54 -0400 (EDT)	[thread overview]
Message-ID: <248142179.74791.1303353294865.JavaMail.root@md01.wow.synacor.com> (raw)
In-Reply-To: <20110418115141.GA3157@osiris.boeblingen.de.ibm.com>

On Mon, 18 Apr 2011 07:51:41 -0400 (EDT), Heiko Carstens wrote:
> 
> That's a bug in the pfault interrupt code. After a cleanup patch which
> simplified lowcore accesses we are left with a dereference which shouldn't
> be there.  The patch below should fix it.
> The bug was introduced with 2.6.37-rc1.
> 
> diff --git a/arch/s390/mm/fault.c b/arch/s390/mm/fault.c
> index 9217e33..4cf85fe 100644
> --- a/arch/s390/mm/fault.c
> +++ b/arch/s390/mm/fault.c
> @@ -558,9 +558,9 @@ static void pfault_interrupt(unsigned int ext_int_code,
>  	 * Get the token (= address of the task structure of the affected task).
>  	 */
>  #ifdef CONFIG_64BIT
> -	tsk = *(struct task_struct **) param64;
> +	tsk = (struct task_struct *) param64;
>  #else
> -	tsk = *(struct task_struct **) param32;
> +	tsk = (struct task_struct *) param32;
>  #endif
>  
>  	if (subcode & 0x0080) {

I applied the above patch and re-built the kernel.  I did not apply
Jan Glauber's suggested patch, since Heiko's suggested patch seemed to be a
"direct hit".  I have had the server up for more than 24 hours now,
which is definitely a good sign.  Without this patch, I've not been able
to keep a 2.6.38 s390x kernel up for more than a few hours.  Unfortunately,
since I can't reproduce the problem on demand, I cannot say with 100%
certainty that the problem is fixed, but it looks good and makes sense.

-- 
  .''`.     Stephen Powell    
 : :'  :
 `. `'`
   `-

  reply	other threads:[~2011-04-21  2:42 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <2099315211.286690.1302917498637.JavaMail.root@md01.wow.synacor.com>
2011-04-16  1:48 ` [OOPS s390] Unable to handle kernel pointer dereference at virtual kernel address (null) Jonathan Nieder
2011-04-18  8:45   ` Jan Glauber
2011-04-18 11:51     ` Heiko Carstens
2011-04-21  2:34       ` Stephen Powell [this message]
2011-04-19  6:34   ` Heiko Carstens
2011-04-19  6:41     ` Jonathan Nieder
2011-04-21  2:45     ` Stephen Powell

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=248142179.74791.1303353294865.JavaMail.root@md01.wow.synacor.com \
    --to=zlinuxman@wowway.com \
    --cc=622570@bugs.debian.org \
    --cc=heiko.carstens@de.ibm.com \
    --cc=jang@linux.vnet.ibm.com \
    --cc=jrnieder@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-s390@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox