From: Andreas Rohner <andreas.rohner-hi6Y0CQ0nG0@public.gmane.org>
To: Ryusuke Konishi
<konishi.ryusuke-Zyj7fXuS5i5L9jVzuh4AOg@public.gmane.org>
Cc: Vyacheslav Dubeyko
<slava-yeENwD64cLxBDgjK7y7TUQ@public.gmane.org>,
linux-nilfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH] nilfs2: fix segctor bug that causes file system corruption
Date: Thu, 02 Jan 2014 23:45:40 +0100 [thread overview]
Message-ID: <52C5EC14.2030300@gmx.net> (raw)
In-Reply-To: <20140103.021703.220046134.konishi.ryusuke-Zyj7fXuS5i5L9jVzuh4AOg@public.gmane.org>
Hi Ryusuke and Vyacheslav,
On 2014-01-02 18:17, Ryusuke Konishi wrote:
> I am thinking of sending this to upstream. But, before that, please
> test the patch enough in the same situation to confirm that it
> actually fixes the problem and it doesn't cause other issues.
I have tested it before, but to be on the safe side, I have rerun my
benchmark (it runs for several hours), and as far as I can tell the
patch does fix the problem and it doesn't cause any other issues.
best regards,
Andreas Rohner
--
To unsubscribe from this list: send the line "unsubscribe linux-nilfs" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2014-01-02 22:45 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-02 14:48 [PATCH] nilfs2: fix segctor bug that causes file system corruption Andreas Rohner
[not found] ` <1388674131-22579-1-git-send-email-andreas.rohner-hi6Y0CQ0nG0@public.gmane.org>
2014-01-02 16:59 ` Vyacheslav Dubeyko
[not found] ` <741898E4-B794-47FF-ABF6-2DCACA2AED43-yeENwD64cLxBDgjK7y7TUQ@public.gmane.org>
2014-01-02 16:38 ` Andreas Rohner
[not found] ` <52C5961F.8000608-hi6Y0CQ0nG0@public.gmane.org>
2014-01-02 17:17 ` Ryusuke Konishi
[not found] ` <20140103.021703.220046134.konishi.ryusuke-Zyj7fXuS5i5L9jVzuh4AOg@public.gmane.org>
2014-01-02 20:16 ` Vyacheslav Dubeyko
[not found] ` <88B1B6B6-1AC9-4BC4-9776-C07D1360A99F-yeENwD64cLxBDgjK7y7TUQ@public.gmane.org>
2014-01-02 19:54 ` Ryusuke Konishi
2014-01-02 22:45 ` Andreas Rohner [this message]
[not found] ` <52C5EC14.2030300-hi6Y0CQ0nG0@public.gmane.org>
2014-01-03 2:05 ` Ryusuke Konishi
-- strict thread matches above, loose matches on Subject: below --
2014-01-03 18:48 Mark Trumpold
2014-01-03 19:37 ` Andreas Rohner
2014-01-08 17:22 Ryusuke Konishi
[not found] ` <1389201735-3739-1-git-send-email-konishi.ryusuke-Zyj7fXuS5i5L9jVzuh4AOg@public.gmane.org>
2014-01-08 17:55 ` Ryusuke Konishi
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=52C5EC14.2030300@gmx.net \
--to=andreas.rohner-hi6y0cq0ng0@public.gmane.org \
--cc=konishi.ryusuke-Zyj7fXuS5i5L9jVzuh4AOg@public.gmane.org \
--cc=linux-nilfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=slava-yeENwD64cLxBDgjK7y7TUQ@public.gmane.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