From: Seth Forshee <seth.forshee@canonical.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: 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: Thu, 14 Jul 2011 10:24:09 -0500 [thread overview]
Message-ID: <20110714152409.GB28501@thinkpad-t410> (raw)
In-Reply-To: <20110714144514.GA6145@infradead.org>
On Thu, Jul 14, 2011 at 10:45:14AM -0400, Christoph Hellwig wrote:
> On Thu, Jul 14, 2011 at 08:53:02AM -0500, Seth Forshee wrote:
> > This has had some discussion on lkml previously [1]. I've been trying to
> > work on a fix, but the current iteration has problems, and I haven't
> > been able to get testers to provide the logs I've requested to help me
> > see what's going wrong. If you'd like to help by providing logs from the
> > most recent test build on the bug you linked to (or using the patches
> > from that build) that would be great. I unfortunately don't have any
> > large-sector devices to test with and cannot reproduce the problems on
> > 512-byte sector devices.
>
> I've been trying to get a large block size test device using qemu
> or scsi_debug but haven't managed to get back to it. If you can get
> Daniel to test you're patches I'd really appreciate your help.
I wasn't aware of scsi_debug. I'll also try to test using that and see
if I can recreate the problems.
next prev parent reply other threads:[~2011-07-14 15:24 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 [this message]
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
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=20110714152409.GB28501@thinkpad-t410 \
--to=seth.forshee@canonical.com \
--cc=barkalow@iabervon.org \
--cc=hch@infradead.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