From: Leon Pollak <leonp@plris.com>
To: Brian Norris <computersforpeace@gmail.com>
Cc: Richard Weinberger <richard@nod.at>,
linux-mtd@lists.infradead.org,
Linux Kernel <linux-kernel@vger.kernel.org>,
Al Viro <viro@zeniv.linux.org.uk>,
Artem Bityutskiy <dedekind1@gmail.com>
Subject: Re: What is wrong?
Date: Tue, 04 Mar 2014 10:54:04 +0200 [thread overview]
Message-ID: <20500571.Fgyz0I6ATm@leonp.plris.com> (raw)
In-Reply-To: <20140304083325.GJ13420@norris-Latitude-E6410>
Hello, all.
I am really sorry for the silence - I was on the business trip and
returned today.
I will recheck everything and try. Meanwhile, the news are not good: our
guys say that it appears that the additional sync DOES NOT SOLVE the
issue.
I ask for excuse, but as I did not know the exact processing, I was
mistaken and, probably, used already gc-ted unit for tests.
Sorry, again.
BR
On Tuesday 04 March 2014 00:33:25 Brian Norris wrote:
> On Mon, Mar 03, 2014 at 03:13:36PM -0600, Andrew Ruder wrote:
> > On Thu, Feb 27, 2014 at 01:22:08PM -0800, Brian Norris wrote:
> > > Perhaps Richard or Andrew can comment on whether this patch should
> > > help you. But I think JFFS2 on NAND uses write-buffered support
> > > which can be affected by this bug.
> >
> > Definitely sounds like the same issue and I'm kind of glad to see it
> > crop up in another filesystem.
>
> We haven't confirmed that the *patch* actually affects Leon's problem;
> just that if he runs an additional 'sync' it solves his problem.
> Leon, did you get to try the patch?
>
> Anyway, should commit 807612db2f9940b9fa6deaef054eb16d51bd3e00 be
> marked for -stable?
>
> Brian
--
Leon
next prev parent reply other threads:[~2014-03-04 9:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4315632.KkRm7kzq26@leonp.plris.com>
[not found] ` <20140227011148.GI4194@ld-irv-0074>
[not found] ` <1553411.O1igofskp7@leonp.plris.com>
2014-02-27 21:22 ` Brian Norris
2014-03-03 21:13 ` Andrew Ruder
2014-03-04 8:33 ` Brian Norris
2014-03-04 8:54 ` Leon Pollak [this message]
2014-03-04 16:40 ` Andrew Ruder
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=20500571.Fgyz0I6ATm@leonp.plris.com \
--to=leonp@plris.com \
--cc=computersforpeace@gmail.com \
--cc=dedekind1@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=richard@nod.at \
--cc=viro@zeniv.linux.org.uk \
/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
all inboxes | Powered by JetHome®