public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: "Steinar H. Gunderson" <sgunderson@bigfoot.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	bugme-daemon@bugzilla.kernel.org, linux-scsi@vger.kernel.org
Subject: Re: [Bugme-new] [Bug 38312] New: Oops in kmem_cache_alloc
Date: Mon, 27 Jun 2011 16:34:55 -0500	[thread overview]
Message-ID: <1309210495.2605.6.camel@mulgrave> (raw)
In-Reply-To: <20110627210443.GB18664@uio.no>

On Mon, 2011-06-27 at 23:04 +0200, Steinar H. Gunderson wrote:
> On Mon, Jun 27, 2011 at 03:41:40PM -0500, James Bottomley wrote:
> > Possibly ... if it's a refcounting bug on the host structure (which
> > would cause shost->pool to have bogus data).  However, in that case,
> > there should be some reference to freeing the host in the logs above the
> > oops (or some event that triggered it).   For just a running system, we
> > don't ever free the host structure until all the devices are gone.
> 
> I checked the serial port log (I log the serial console from another machine,
> to be sure to get these kinds of bugs even if they hit the network and/or
> SCSI subsystems), and the only thing is that cron seems to have segfaulted a
> time. This is unusual, but I take it it shouldn't crash the kernel in itself
> (and it might be due to the result of some glibc up- and downgrading around
> that time).

That does make it pretty unlikely to be a bogus pointer caused by reuse
of a freed host structure.  At this point, I'm afraid, I don't have any
other ideas.

James



  reply	other threads:[~2011-06-27 21:34 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-38312-10286@https.bugzilla.kernel.org/>
2011-06-27 20:30 ` [Bugme-new] [Bug 38312] New: Oops in kmem_cache_alloc Andrew Morton
2011-06-27 20:41   ` James Bottomley
2011-06-27 21:04     ` Steinar H. Gunderson
2011-06-27 21:34       ` James Bottomley [this message]
2011-06-29 21:19     ` Andrew Morton

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=1309210495.2605.6.camel@mulgrave \
    --to=james.bottomley@hansenpartnership.com \
    --cc=akpm@linux-foundation.org \
    --cc=bugme-daemon@bugzilla.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=sgunderson@bigfoot.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