LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Mike Christie <michaelc@cs.wisc.edu>
To: James Bottomley <James.Bottomley@SteelEye.com>
Cc: Andreas Steinmetz <ast@domdv.de>,
Linux Kernel Mailinglist <linux-kernel@vger.kernel.org>,
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 16:12:49 -0500 [thread overview]
Message-ID: <45FEFCD1.6070109@cs.wisc.edu> (raw)
In-Reply-To: <45FEDF23.1060801@cs.wisc.edu>
Mike Christie wrote:
> 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.
>>
>
> I think we might only need the first patch if the problem is similar to
> what the lsi guys were seeing. I thought the problem is that we are not
> estimating how large the transfer is correctly because we do not take
> into account offsets at the end. This results in nr_vecs being zero when
> it should be a valid value. I thought Kai's patch:
> http://bugzilla.kernel.org/show_bug.cgi?id=7919
> http://git.kernel.org/?p=linux/kernel/git/jejb/scsi-misc-2.6.git;a=commitdiff;h=9abe16c670bd3d4ab5519257514f9f291383d104
> fixed the problem on st's side,
Oh, I noticed that the subject for the mail references 2.6.30.3 and the
patch for st in the bugzilla did not make into 2.6.20 and is not in .3.
Could we try the st patch in the bugzilla first?
next prev parent reply other threads:[~2007-03-19 21:13 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 [this message]
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
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=45FEFCD1.6070109@cs.wisc.edu \
--to=michaelc@cs.wisc.edu \
--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 \
--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).