From: Eric Whitney <enwlinux@gmail.com>
To: "Wilcox, Matthew R" <matthew.r.wilcox@intel.com>
Cc: "Namjae Jeon" <namjae.jeon@samsung.com>,
"'Andrew Morton'" <akpm@linux-foundation.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
linux-ext4 <linux-ext4@vger.kernel.org>,
"Lukáš Czerner" <lczerner@redhat.com>,
"'Eric Whitney'" <enwlinux@gmail.com>,
"Ashish Sangwan" <a.sangwan@samsung.com>
Subject: Re: [PATCH] msync: fix incorrect fstart calculation
Date: Fri, 27 Jun 2014 12:12:56 -0400 [thread overview]
Message-ID: <20140627161256.GA8164@wallace> (raw)
In-Reply-To: <100D68C7BA14664A8938383216E40DE0407A787B@FMSMSX114.amr.corp.intel.com>
I can confirm that this patch corrects the ext4 regressions I reported on
3.16-rc1 for data_journal.
Additionally, it corrects regressions for two other tests I have not yet
reported. Those tests include generic/263 when running with the
data=journal mount option, and generic/219 (a quota test that doesn't use
fsx) when running with all xfstests-bld scenarios (4k, ext4, nojournal, 1k,
etc.) with the exception of bigalloc. The generic/219 failure on bigalloc in
3.16-rc1 is not a regression, and was present in earlier releases.
With this patch, ext4 3.16-rc3 regression results on x64_64 should look much
more like 3.15 final.
Thanks guys!
Eric
* Wilcox, Matthew R <matthew.r.wilcox@intel.com>:
> Acked-by: Matthew Wilcox <matthew.r.wilcox@intel.com>
> ________________________________________
> From: Namjae Jeon [namjae.jeon@samsung.com]
> Sent: June 27, 2014 4:38 AM
> To: 'Andrew Morton'
> Cc: linux-mm@kvack.org; linux-ext4; Lukáš Czerner; Wilcox, Matthew R; 'Eric Whitney'; Ashish Sangwan
> Subject: [PATCH] msync: fix incorrect fstart calculation
>
> Fix a regression caused by Commit 7fc34a62ca mm/msync.c: sync only
> the requested range in msync().
> xfstests generic/075 fail occured on ext4 data=journal mode because
> the intended range was not syncing due to wrong fstart calculation.
>
> Cc: Matthew Wilcox <matthew.r.wilcox@intel.com>
> Cc: Lukáš Czerner <lczerner@redhat.com>
> Reported-by: Eric Whitney <enwlinux@gmail.com>
> Signed-off-by: Namjae Jeon <namjae.jeon@samsung.com>
> Signed-off-by: Ashish Sangwan <a.sangwan@samsung.com>
> ---
> mm/msync.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/mm/msync.c b/mm/msync.c
> index a5c6736..ad97dce 100644
> --- a/mm/msync.c
> +++ b/mm/msync.c
> @@ -78,7 +78,8 @@ SYSCALL_DEFINE3(msync, unsigned long, start, size_t, len, int, flags)
> goto out_unlock;
> }
> file = vma->vm_file;
> - fstart = start + ((loff_t)vma->vm_pgoff << PAGE_SHIFT);
> + fstart = (start - vma->vm_start) +
> + ((loff_t)vma->vm_pgoff << PAGE_SHIFT);
> fend = fstart + (min(end, vma->vm_end) - start) - 1;
> start = vma->vm_end;
> if ((flags & MS_SYNC) && file &&
> --
> 1.7.11-rc0
>
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
WARNING: multiple messages have this Message-ID (diff)
From: Eric Whitney <enwlinux@gmail.com>
To: "Wilcox, Matthew R" <matthew.r.wilcox@intel.com>
Cc: "Namjae Jeon" <namjae.jeon@samsung.com>,
"'Andrew Morton'" <akpm@linux-foundation.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
linux-ext4 <linux-ext4@vger.kernel.org>,
"Lukáš Czerner" <lczerner@redhat.com>,
"'Eric Whitney'" <enwlinux@gmail.com>,
"Ashish Sangwan" <a.sangwan@samsung.com>
Subject: Re: [PATCH] msync: fix incorrect fstart calculation
Date: Fri, 27 Jun 2014 12:12:56 -0400 [thread overview]
Message-ID: <20140627161256.GA8164@wallace> (raw)
In-Reply-To: <100D68C7BA14664A8938383216E40DE0407A787B@FMSMSX114.amr.corp.intel.com>
I can confirm that this patch corrects the ext4 regressions I reported on
3.16-rc1 for data_journal.
Additionally, it corrects regressions for two other tests I have not yet
reported. Those tests include generic/263 when running with the
data=journal mount option, and generic/219 (a quota test that doesn't use
fsx) when running with all xfstests-bld scenarios (4k, ext4, nojournal, 1k,
etc.) with the exception of bigalloc. The generic/219 failure on bigalloc in
3.16-rc1 is not a regression, and was present in earlier releases.
With this patch, ext4 3.16-rc3 regression results on x64_64 should look much
more like 3.15 final.
Thanks guys!
Eric
* Wilcox, Matthew R <matthew.r.wilcox@intel.com>:
> Acked-by: Matthew Wilcox <matthew.r.wilcox@intel.com>
> ________________________________________
> From: Namjae Jeon [namjae.jeon@samsung.com]
> Sent: June 27, 2014 4:38 AM
> To: 'Andrew Morton'
> Cc: linux-mm@kvack.org; linux-ext4; LukA!A! Czerner; Wilcox, Matthew R; 'Eric Whitney'; Ashish Sangwan
> Subject: [PATCH] msync: fix incorrect fstart calculation
>
> Fix a regression caused by Commit 7fc34a62ca mm/msync.c: sync only
> the requested range in msync().
> xfstests generic/075 fail occured on ext4 data=journal mode because
> the intended range was not syncing due to wrong fstart calculation.
>
> Cc: Matthew Wilcox <matthew.r.wilcox@intel.com>
> Cc: LukA!A! Czerner <lczerner@redhat.com>
> Reported-by: Eric Whitney <enwlinux@gmail.com>
> Signed-off-by: Namjae Jeon <namjae.jeon@samsung.com>
> Signed-off-by: Ashish Sangwan <a.sangwan@samsung.com>
> ---
> mm/msync.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/mm/msync.c b/mm/msync.c
> index a5c6736..ad97dce 100644
> --- a/mm/msync.c
> +++ b/mm/msync.c
> @@ -78,7 +78,8 @@ SYSCALL_DEFINE3(msync, unsigned long, start, size_t, len, int, flags)
> goto out_unlock;
> }
> file = vma->vm_file;
> - fstart = start + ((loff_t)vma->vm_pgoff << PAGE_SHIFT);
> + fstart = (start - vma->vm_start) +
> + ((loff_t)vma->vm_pgoff << PAGE_SHIFT);
> fend = fstart + (min(end, vma->vm_end) - start) - 1;
> start = vma->vm_end;
> if ((flags & MS_SYNC) && file &&
> --
> 1.7.11-rc0
>
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2014-06-27 16:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-27 11:38 [PATCH] msync: fix incorrect fstart calculation Namjae Jeon
2014-06-27 11:51 ` Lukáš Czerner
2014-06-27 11:51 ` Lukáš Czerner
2014-06-27 12:43 ` Wilcox, Matthew R
2014-06-27 16:12 ` Eric Whitney [this message]
2014-06-27 16:12 ` Eric Whitney
2014-06-28 19:14 ` Theodore Ts'o
2014-06-28 19:14 ` Theodore Ts'o
2014-06-28 19:44 ` Andrew Morton
2014-06-28 19:57 ` Theodore Ts'o
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=20140627161256.GA8164@wallace \
--to=enwlinux@gmail.com \
--cc=a.sangwan@samsung.com \
--cc=akpm@linux-foundation.org \
--cc=lczerner@redhat.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=matthew.r.wilcox@intel.com \
--cc=namjae.jeon@samsung.com \
/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.