From: Christoph Hellwig <hch@infradead.org>
To: Daniel Barkalow <barkalow@iabervon.org>,
Christoph Hellwig <hch@tuxera.com>,
linux-kernel@vger.kernel.org
Subject: Re: Problems with hfsplus on ipods in 2.6.38+
Date: Mon, 18 Jul 2011 11:01:41 -0400 [thread overview]
Message-ID: <20110718150141.GA28123@infradead.org> (raw)
In-Reply-To: <20110718133651.GA19552@thinkpad-t410>
On Mon, Jul 18, 2011 at 08:36:51AM -0500, Seth Forshee wrote:
> On Fri, Jul 15, 2011 at 09:39:00AM -0500, Seth Forshee wrote:
> > What I also see are GPFs in memory allocation code, which is what I
> > believe others have seen with my patch, and so far I haven't seen those
> > with the reversions. So I'm suspecting memory corruption, but I don't
> > yet see where the corruption is coming form. I found one problem, but I
> > don't suspect it's responsible for the GPFs.
>
> I had some torture tests running over the weekend with the "one
> problem" mentioned above fixed, which was a couple of kfrees that were
> still using the old vhdr pointers. There were no oopses over a couple of
> days of testing. I've posted a new build on the bug in launchpad in
> hopes of getting some testing from those who were getting oopses quite
> readily. The updated patch follows.
Thanks a lot Seth. I'll put it into my queue for Linux 3.1, and if
everthing works out fine we can push it out to -stable.
next prev parent reply other threads:[~2011-07-18 15:01 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-14 2:10 Problems with hfsplus on ipods in 2.6.38+ Daniel Barkalow
2011-07-14 13:53 ` Seth Forshee
2011-07-14 14:45 ` Christoph Hellwig
2011-07-14 15:24 ` Seth Forshee
2011-07-14 17:43 ` Daniel Barkalow
2011-07-15 1:26 ` Daniel Barkalow
2011-07-15 14:39 ` Seth Forshee
2011-07-15 15:43 ` Daniel Barkalow
2011-07-15 16:21 ` Seth Forshee
2011-07-18 13:36 ` Seth Forshee
2011-07-18 15:01 ` Christoph Hellwig [this message]
2011-07-18 16:46 ` Daniel Barkalow
2011-07-19 4:16 ` Daniel Barkalow
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=20110718150141.GA28123@infradead.org \
--to=hch@infradead.org \
--cc=barkalow@iabervon.org \
--cc=hch@tuxera.com \
--cc=linux-kernel@vger.kernel.org \
/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