From: Brandon Philips <brandon@ifup.co>
To: Vlastimil Babka <vbabka@suse.cz>,
Anthony Romano <anthony.romano@coreos.com>,
hughd@google.com, Christoph Hellwig <hch@infradead.org>,
Cong Wang <amwang@redhat.com>, Kay Sievers <kay@vrfy.org>,
Andrew Morton <akpm@linux-foundation.org>,
Matthew Garrett <mjg59@srcf.ucam.org>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] tmpfs: don't undo fallocate past its last page
Date: Sat, 04 Jun 2016 01:10:11 +0000 [thread overview]
Message-ID: <CAEm7KtxBiDTsErPXUK32GbQF=9EAKtQJ7rM1oHR0WP304VvuBw@mail.gmail.com> (raw)
In-Reply-To: <5739B60E.1090700@suse.cz>
[-- Attachment #1: Type: text/plain, Size: 1396 bytes --]
On Mon, May 16, 2016 at 4:59 AM Vlastimil Babka <vbabka@suse.cz> wrote:
> On 05/08/2016 03:16 PM, Anthony Romano wrote:
> > When fallocate is interrupted it will undo a range that extends one byte
> > past its range of allocated pages. This can corrupt an in-use page by
> > zeroing out its first byte. Instead, undo using the inclusive byte range.
> > Signed-off-by: Anthony Romano <anthony.romano@coreos.com>
>
> Looks like a stable candidate patch. Can you point out the commit that
> introduced the bug, for the Fixes: tag?
>
Bumping this thread as I don't think this patch has gotten picked up. And
cc'ing folks from 1635f6a74152f1dcd1b888231609d64875f0a81a.
Thank you,
Brandon
> > ---
> > mm/shmem.c | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/mm/shmem.c b/mm/shmem.c
> > index 719bd6b..f0f9405 100644
> > --- a/mm/shmem.c
> > +++ b/mm/shmem.c
> > @@ -2238,7 +2238,7 @@ static long shmem_fallocate(struct file *file, int
> mode, loff_t offset,
> > /* Remove the !PageUptodate pages we added */
> > shmem_undo_range(inode,
> > (loff_t)start << PAGE_SHIFT,
> > - (loff_t)index << PAGE_SHIFT, true);
> > + ((loff_t)index << PAGE_SHIFT) - 1, true);
> > goto undone;
> > }
> >
> >
>
>
[-- Attachment #2: Type: text/html, Size: 2199 bytes --]
next prev parent reply other threads:[~2016-06-04 1:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-08 13:16 Anthony Romano
2016-05-16 11:59 ` Vlastimil Babka
2016-05-16 13:55 ` Anthony Romano
2016-06-04 1:10 ` Brandon Philips [this message]
2016-06-06 4:05 ` Brandon Philips
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='CAEm7KtxBiDTsErPXUK32GbQF=9EAKtQJ7rM1oHR0WP304VvuBw@mail.gmail.com' \
--to=brandon@ifup.co \
--cc=akpm@linux-foundation.org \
--cc=amwang@redhat.com \
--cc=anthony.romano@coreos.com \
--cc=hch@infradead.org \
--cc=hughd@google.com \
--cc=kay@vrfy.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mjg59@srcf.ucam.org \
--cc=vbabka@suse.cz \
/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