From: Andreas Rohner <andreas.rohner-hi6Y0CQ0nG0@public.gmane.org>
To: Ryusuke Konishi
<konishi.ryusuke-Zyj7fXuS5i5L9jVzuh4AOg@public.gmane.org>
Cc: linux-nilfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH] nilfs2: fix data loss with mmap()
Date: Thu, 18 Sep 2014 12:44:16 +0200 [thread overview]
Message-ID: <541AB780.2010708@gmx.net> (raw)
In-Reply-To: <20140918.162416.1553343892940167544.konishi.ryusuke-Zyj7fXuS5i5L9jVzuh4AOg@public.gmane.org>
On 2014-09-18 09:24, Ryusuke Konishi wrote:
> On Wed, 17 Sep 2014 21:34:39 +0900 (JST), Ryusuke Konishi wrote:
>> On Wed, 17 Sep 2014 10:16:46 +0200, Andreas Rohner wrote:
>>> On 2014-09-16 15:57, Ryusuke Konishi wrote:
>>>> On Tue, 16 Sep 2014 10:38:29 +0200, Andreas Rohner wrote:
>>>>>> I'd appreciate your help on testing the patch for some old kernels.
>>>>>> (And, please declare a "Tested-by" tag in the reply mail, if the test
>>>>>> is ok).
>>>>>
>>>>> Sure I have everything set up. Which kernels do I have to test? Was
>>>>> commit 136e877 backported? I presume at least stable and some of the
>>>>> longterm kernels on https://www.kernel.org/...
>>>>
>>>> The commit 136e877 was merged to v3.10 and backported to stable trees
>>>> of earlier kernels. But, most of earlier stable trees are no longer
>>>> maintained. Well maintained trees are the following longterm kernels:
>>>>
>>>> - 3.4.y (backported commit 136e877)
>>>> - 3.10.y
>>>> - 3.14.y
>>>>
>>>> I think these three kernels are worty to be tested.
>>>
>>> I tested it on all stable kernels including 3.4.x, 3.10.x, 3.14.x. The
>>> bug is present in all of them and the patch fixes it. The patch also
>>> applies cleanly on all kernels. I sent it again yesterday, and added the
>>> Tested-by: tag.
>
> One thing I have a question.
>
> Is the original issue that commit 136e877 fixed still OK ? If you
> haven't tested it, I apprecicate if you examine the test for the prior
> issue.
Yes the original issue is still fixed. I was able to reproduce it by
reverting nilfs_set_page_dirty() to the state prior to commit 136e877.
Then I used the new version of nilfs_set_page_dirty() including my patch
and I couldn't reproduce the issue anymore. So it seems to still be fixed.
Furthermore the original issue was caused by the use of
__set_page_dirty_buffers(), which marked unmapped buffers as dirty. My
patch does not change the fix for that.
br,
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-09-18 10:44 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-15 19:47 [PATCH] nilfs2: fix data loss with mmap() Andreas Rohner
[not found] ` <1410810450-2637-1-git-send-email-andreas.rohner-hi6Y0CQ0nG0@public.gmane.org>
2014-09-15 22:01 ` Ryusuke Konishi
[not found] ` <20140916.070130.858349725408024032.konishi.ryusuke-Zyj7fXuS5i5L9jVzuh4AOg@public.gmane.org>
2014-09-15 22:24 ` Andreas Rohner
[not found] ` <54176705.6080107-hi6Y0CQ0nG0@public.gmane.org>
2014-09-16 4:42 ` Ryusuke Konishi
[not found] ` <20140916.134218.1694651966300542167.konishi.ryusuke-Zyj7fXuS5i5L9jVzuh4AOg@public.gmane.org>
2014-09-16 8:38 ` Andreas Rohner
[not found] ` <5417F705.8020306-hi6Y0CQ0nG0@public.gmane.org>
2014-09-16 13:57 ` Ryusuke Konishi
[not found] ` <20140916.225726.1211879952201061873.konishi.ryusuke-Zyj7fXuS5i5L9jVzuh4AOg@public.gmane.org>
2014-09-17 8:16 ` Andreas Rohner
[not found] ` <5419436E.4030501-hi6Y0CQ0nG0@public.gmane.org>
2014-09-17 12:34 ` Ryusuke Konishi
[not found] ` <20140917.213439.867924114484975245.konishi.ryusuke-Zyj7fXuS5i5L9jVzuh4AOg@public.gmane.org>
2014-09-18 7:24 ` Ryusuke Konishi
[not found] ` <20140918.162416.1553343892940167544.konishi.ryusuke-Zyj7fXuS5i5L9jVzuh4AOg@public.gmane.org>
2014-09-18 10:44 ` Andreas Rohner [this message]
2014-09-16 15:11 ` Andreas Rohner
-- strict thread matches above, loose matches on Subject: below --
2014-09-18 14:56 [PATCH 0/1] " Ryusuke Konishi
[not found] ` <1411052185-8118-1-git-send-email-konishi.ryusuke-Zyj7fXuS5i5L9jVzuh4AOg@public.gmane.org>
2014-09-18 14:56 ` [PATCH] " Ryusuke Konishi
2014-09-18 14:56 ` Ryusuke Konishi
[not found] ` <1411052185-8118-2-git-send-email-konishi.ryusuke-Zyj7fXuS5i5L9jVzuh4AOg@public.gmane.org>
2014-09-18 19:17 ` Andrew Morton
2014-09-18 19:17 ` Andrew Morton
[not found] ` <20140918121708.c9e9678c9ea76b057377d843-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org>
2014-09-18 23:41 ` Ryusuke Konishi
2014-09-18 23:41 ` 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=541AB780.2010708@gmx.net \
--to=andreas.rohner-hi6y0cq0ng0@public.gmane.org \
--cc=konishi.ryusuke-Zyj7fXuS5i5L9jVzuh4AOg@public.gmane.org \
--cc=linux-nilfs-u79uwXL29TY76Z2rM5mHXA@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 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.