From: John Stultz <john.stultz@linaro.org>
To: Kees Cook <keescook@chromium.org>
Cc: Ulf Hansson <ulf.hansson@linaro.org>,
Chris Ball <chris@printf.net>,
Peter Maydell <peter.maydell@linaro.org>,
Johan Rudholm <jrudholm@gmail.com>,
Russell King - ARM Linux <linux@arm.linux.org.uk>,
"Theodore Ts'o" <tytso@mit.edu>,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: [Regression] 3.15 mmc related ext4 corruption with qemu-system-arm
Date: Fri, 08 Aug 2014 17:17:54 -0700 [thread overview]
Message-ID: <53E568B2.40206@linaro.org> (raw)
In-Reply-To: <CAGXu5j+Q8F8TKy8sxCL6pxD-cni4RKxy46HwsCSZE+mWpuyn-g@mail.gmail.com>
On 08/08/2014 05:15 PM, Kees Cook wrote:
> On Fri, Aug 8, 2014 at 2:14 PM, John Stultz <john.stultz@linaro.org> wrote:
>> I sunk a couple of weeks bisecting to try to narrow down the more
>> sporadic issue, but was unsuccessful past the initial commit above.
>> Since then I've been far too swamped to spend any more time on it. Even
>> so, its a *major* pain for testing but it seems like no one else really
>> cares?
> I'm in the same boat as far as poor bisection results. :(
>
> However, I keep using the 3-patch mmci fix series from Ulf, and
> haven't hit any trouble with them. Though perhaps I'm just getting
> lucky?
>
> http://git.kernel.org/cgit/linux/kernel/git/kees/linux.git/log/?h=arm/fix-mmci
I guess I'll give that another shot then.
thanks
-john
next prev parent reply other threads:[~2014-08-09 0:18 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-12 5:35 [Regression] 3.15 mmc related ext4 corruption with qemu-system-arm John Stultz
2014-06-12 12:09 ` Ulf Hansson
2014-06-12 12:15 ` Peter Maydell
2014-06-13 11:35 ` Ulf Hansson
2014-06-12 23:51 ` John Stultz
2014-06-13 12:28 ` Ulf Hansson
2014-06-16 7:22 ` Jeff Chua
2014-06-16 13:02 ` Ulf Hansson
2014-08-08 21:14 ` John Stultz
2014-08-09 0:15 ` Kees Cook
2014-08-09 0:17 ` John Stultz [this message]
2014-08-09 0:32 ` Theodore Ts'o
2014-08-09 4:03 ` John Stultz
2014-08-11 8:04 ` Ulf Hansson
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=53E568B2.40206@linaro.org \
--to=john.stultz@linaro.org \
--cc=chris@printf.net \
--cc=jrudholm@gmail.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=peter.maydell@linaro.org \
--cc=tytso@mit.edu \
--cc=ulf.hansson@linaro.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.