All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nick Alcock <nick.alcock@oracle.com>
To: "Darrick J. Wong" <darrick.wong@oracle.com>
Cc: Eric Biggers <ebiggers3@gmail.com>,
	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: Tue, 14 Mar 2017 15:18:26 +0000	[thread overview]
Message-ID: <87a88nga4d.fsf@esperi.org.uk> (raw)
In-Reply-To: <20170313233701.GA5271@birch.djwong.org> (Darrick J. Wong's message of "Mon, 13 Mar 2017 16:37:01 -0700")

On 13 Mar 2017, Darrick J. Wong told this:

> I wouldn't turn on inline_data for files, period.  It's not as well tested
> as it ought to be (clearly). :/

Bah, if I don't, how will it get tested? :) this machine is newly
commissioned and doesn't have much load or important content yet: it's
just the time to try experimental and potentially dangerous things :)

(I didn't know you could turn it on in any sense other than a 'big
hammer' for everything. I have a great many symlinks, and it's really
that I'm interested in reducing seeks for...)

-- 
NULL && (void)

      reply	other threads:[~2017-03-14 15:18 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
2017-03-13 23:11   ` Nick Alcock
2017-03-13 23:37     ` Darrick J. Wong
2017-03-14 15:18       ` Nick Alcock [this message]

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=87a88nga4d.fsf@esperi.org.uk \
    --to=nick.alcock@oracle.com \
    --cc=darrick.wong@oracle.com \
    --cc=ebiggers3@gmail.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.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.