From: Arnaud Faucher <arnaud.faucher@gmail.com>
To: Juergen Beisert <jbe@pengutronix.de>, Mel Gorman <mel@csn.ul.ie>
Cc: Robert Schwebel <r.schwebel@pengutronix.de>,
linux-kernel@vger.kernel.org
Subject: Re: Patch "page-allocator: preserve PFN ordering when __GFP_COLD is set" fails on my system
Date: Wed, 12 Aug 2009 14:29:27 -0400 [thread overview]
Message-ID: <1250101767.4628.22.camel@green> (raw)
I have a rather similar problem on a driver that I try to keep
up-to-date with recent kernel versions
(http://code.ximeta.com/trac-ndas/ticket/1110#comment:30). The NDAS
hardware is an ethernet-enabled disk controller on one chip, kind of a
cheap iSCSI.
In my case there is no oops: the symptoms are that the read blocks seem
to be swapped or full of garbage.
After investigation in the NDAS code, the bug triggers when the driver
tries to merge adjacent requests, before sending them to the controller.
I had to disable this merge in order to restore normal behavior, at the
expense of a reduced efficiency.
Mel's buffer overrun theory seems to apply in the NDAS driver case,
where the original requests adjacency test seems faulty.
May it also be the cause of the SD mounting crash ?
next reply other threads:[~2009-08-12 18:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-12 18:29 Arnaud Faucher [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-08-11 16:30 Patch "page-allocator: preserve PFN ordering when __GFP_COLD is set" fails on my system Juergen Beisert
2009-08-12 7:47 ` Robert Schwebel
2009-08-12 9:20 ` Mel Gorman
2009-08-12 11:11 ` Juergen Beisert
2009-08-12 13:50 ` Mel Gorman
2009-08-12 15:35 ` Juergen Beisert
2009-08-12 18:40 ` Arnaud Faucher
2009-08-13 8:39 ` Mel Gorman
2009-08-13 9:22 ` Juergen Beisert
2009-10-16 8:10 ` Juergen Beisert
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=1250101767.4628.22.camel@green \
--to=arnaud.faucher@gmail.com \
--cc=200908121735.44439.jbe@pengutronix.de \
--cc=jbe@pengutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mel@csn.ul.ie \
--cc=r.schwebel@pengutronix.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