From: Al Viro <viro@ftp.linux.org.uk>
To: Stefan Richter <stefanr@s5r6.in-berlin.de>
Cc: Bernhard Kaindl <bk@suse.de>, Andrew Morton <akpm@osdl.org>,
bcollins@debian.org, scjody@modernduck.com,
linux1394-devel@lists.sourceforge.net,
linux-scsi@vger.kernel.org,
James Bottomley <James.Bottomley@SteelEye.com>
Subject: Re: Fw: [Bugme-new] [Bug 6114] New: Initio sbp2 causes: "slab error in cache_free_debugcheck(): cache `size-512(DMA)': double free, or memory outside" object was overwritten
Date: Wed, 22 Feb 2006 01:29:42 +0000 [thread overview]
Message-ID: <20060222012942.GY27946@ftp.linux.org.uk> (raw)
In-Reply-To: <43FBB1A2.9030009@s5r6.in-berlin.de>
On Wed, Feb 22, 2006 at 01:34:42AM +0100, Stefan Richter wrote:
> Al's patch is certainly better since it adds checks to the actual
> affected code region, i.e. mode_sense handling in the SCSI layers.
> James, would you integrate this patch?
>
> However sbp2 will keep some sort of skip_ms_page_8 blacklisting anyway
> because of different issues with other bridges.
Sure, but for this bridge it's not needed - with that fix we get the
right data out of bridge response. Note
+sda: missing header in MODE_SENSE response
and
+SCSI device sda: drive cache: write back
in that diff. The former is exactly what we get when we detect that
sort of breakage (bare page 6 without header) and the latter is where
we manage to get the cache type.
next prev parent reply other threads:[~2006-02-22 1:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20060221040511.35b69d26.akpm@osdl.org>
[not found] ` <43FB6545.8080103@s5r6.in-berlin.de>
[not found] ` <43FB67BD.7030101@s5r6.in-berlin.de>
[not found] ` <20060221134543.5f844d7c.akpm@osdl.org>
[not found] ` <43FB9FE5.8070309@s5r6.in-berlin.de>
[not found] ` <Pine.LNX.4.64.0602220041070.21474@jbgna.fhfr.qr>
2006-02-22 0:34 ` Fw: [Bugme-new] [Bug 6114] New: Initio sbp2 causes: "slab error in cache_free_debugcheck(): cache `size-512(DMA)': double free, or memory outside" object was overwritten Stefan Richter
2006-02-22 1:29 ` Al Viro [this message]
2006-02-22 6:05 ` Stefan Richter
2006-02-22 0:53 Douglas Gilbert
2006-02-22 1:20 ` Al Viro
2006-02-22 2:39 ` Douglas Gilbert
2006-02-22 3:25 ` Al Viro
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=20060222012942.GY27946@ftp.linux.org.uk \
--to=viro@ftp.linux.org.uk \
--cc=James.Bottomley@SteelEye.com \
--cc=akpm@osdl.org \
--cc=bcollins@debian.org \
--cc=bk@suse.de \
--cc=linux-scsi@vger.kernel.org \
--cc=linux1394-devel@lists.sourceforge.net \
--cc=scjody@modernduck.com \
--cc=stefanr@s5r6.in-berlin.de \
/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