LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Gene Heskett <gene.heskett@gmail.com>
To: linux-kernel@vger.kernel.org
Cc: James Bottomley <James.Bottomley@steeleye.com>,
	Mike Christie <michaelc@cs.wisc.edu>,
	Andreas Steinmetz <ast@domdv.de>,
	linux-scsi@vger.kernel.org, akpm@linux-foundation.org
Subject: Re: 2.6.20.3: kernel BUG at mm/slab.c:597 try#2
Date: Mon, 19 Mar 2007 17:47:48 -0400	[thread overview]
Message-ID: <200703191747.48826.gene.heskett@gmail.com> (raw)
In-Reply-To: <1174328987.3512.37.camel@mulgrave.il.steeleye.com>

On Monday 19 March 2007, James Bottomley wrote:
>On Mon, 2007-03-19 at 12:49 -0500, Mike Christie wrote:
>> > I can't even say if the tapes are written correctly as I can't read
>> > them (one does not reboot production machines back to 2.4.x just to
>> > try to read a backup tape - I don't have 2.6.x older than 2.6.20 on
>> > these machines).
>>
>> Could you try this patch
>> http://marc.info/?l=linux-scsi&m=116464965414878&w=2
>> I thought st was modified to not send offsets in the last elements but
>> it looks like it wasn't.
>
>Actually, there are two patches in the email referred to.  If the
>analysis that we're passing NULL to mempool_free is correct, it should
>be the second one that fixes the problem (the one that checks
>bio->bi_io_vec before freeing it).  Which would mean we have a
>nr_vecs==0 bio generated by the tar somehow.
>
>James

James, could this also be the cause of a tar based backup going crazy and 
thinking all data is new under any 2.6.21-rc* kernel I've tested so far 
with amanda, which in my case uses tar?  I've tried the fedora patched 
tar-1.15-1, and one I hand built right after 1.15-1 came out over a year 
ago, and they both do it, but only when booted to a 2.6.21-rc* kernel.

This obviously will be a show-stopper, either for amanda (and by 
inference, any app that uses tar), or for the migration of an amanda 
users machinery to a 2.6.21 kernel.

>
>-
>To unsubscribe from this list: send the line "unsubscribe linux-kernel"
> in the body of a message to majordomo@vger.kernel.org
>More majordomo info at  http://vger.kernel.org/majordomo-info.html
>Please read the FAQ at  http://www.tux.org/lkml/



-- 
Cheers, Gene
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
fractal radiation jamming the backbone

  parent reply	other threads:[~2007-03-19 21:48 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-19  0:34 Andreas Steinmetz
2007-03-19  6:00 ` Andrew Morton
2007-03-19  8:00   ` Pekka Enberg
2007-03-19  8:32     ` Pekka Enberg
2007-03-19  8:35       ` Pekka Enberg
2007-03-19 17:49 ` Mike Christie
2007-03-19 18:29   ` James Bottomley
2007-03-19 19:06     ` Mike Christie
2007-03-19 21:12       ` Mike Christie
2007-03-19 23:25         ` Andreas Steinmetz
2007-03-19 23:40           ` Andrew Morton
2007-03-19 23:46             ` Andreas Steinmetz
2007-03-19 23:25       ` Andreas Steinmetz
2007-03-19 21:47     ` Gene Heskett [this message]
2007-03-19 22:06       ` James Bottomley
2007-03-19 23:29         ` Gene Heskett

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=200703191747.48826.gene.heskett@gmail.com \
    --to=gene.heskett@gmail.com \
    --cc=James.Bottomley@steeleye.com \
    --cc=akpm@linux-foundation.org \
    --cc=ast@domdv.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=michaelc@cs.wisc.edu \
    --subject='Re: 2.6.20.3: kernel BUG at mm/slab.c:597 try#2' \
    /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

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).