From: Eric Biggers <ebiggers3@gmail.com>
To: Nick Alcock <nick.alcock@oracle.com>
Cc: linux-ext4@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: v4.7--v4.10+: ext4: repeatable inline-data oops (and fs corruption) caused by msync() of shared writable mmap (with recipe)
Date: Sun, 12 Mar 2017 17:52:32 -0700 [thread overview]
Message-ID: <20170313005232.GA593@zzz> (raw)
In-Reply-To: <874lzdcj9r.fsf@esperi.org.uk>
On Wed, Mar 01, 2017 at 11:45:52AM +0000, Nick Alcock wrote:
> [Resend, after the first attempt, from my home address, failed with
> endless greylisting followed by "4.5.0 Interactive router timed out"
> from all but the lowest-priority MX for vger, and "Name server:
> bl-ckh-le.kernel.org.: host not found" for the apparently-nonexistent
> lowest-priority MX. Maybe it'll work better from here.]
>
> I first spotted this -- or it spotted me -- back in the v4.7.x days. It
> is still present in v4.10.
>
> Here's a replication recipe, given a reasonable rootfs with a compiler
> on it, and assuming a blank virtio disk on /dev/vdb:
>
Hi Nick, thanks for reporting this. I've sent a patch which should fix this,
and Cc'ed you. This actually seems to been a bug for a very long time, maybe
even ever since the inline_data feature was introduced. (I was able to
reproduce it in a 3.18 kernel, at least.) I'm not sure why it didn't get
noticed earlier --- maybe hardly anyone ever writes to small files with mmap...
- Eric
next prev parent reply other threads:[~2017-03-13 0:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-01 11:45 v4.7--v4.10+: ext4: repeatable inline-data oops (and fs corruption) caused by msync() of shared writable mmap (with recipe) Nick Alcock
2017-03-13 0:52 ` Eric Biggers [this message]
2017-03-13 23:11 ` Nick Alcock
2017-03-13 23:37 ` Darrick J. Wong
2017-03-14 15:18 ` Nick Alcock
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=20170313005232.GA593@zzz \
--to=ebiggers3@gmail.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=nick.alcock@oracle.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.