From: Dave Chinner <david@fromorbit.com>
To: d.g.jansen@googlemail.com
Cc: linux-kernel@vger.kernel.org, akpm@linux-foundation.org, tytso@mit.edu
Subject: Re: [rfc] Ignore Fsync Calls in Laptop_Mode
Date: Fri, 20 May 2011 13:39:49 +1000 [thread overview]
Message-ID: <20110520033949.GQ32466@dastard> (raw)
In-Reply-To: <BANLkTikGxbcMBD=3W_9_mpZBoVDc8HrX8A@mail.gmail.com>
On Thu, May 19, 2011 at 03:34:46PM +0200, Dennis Jansen wrote:
> This is my first proper kernel code proposal so please bear with me!
>
> =Summary for busy kernel hackers=
> Problem: laptop_mode wants to keep applications from waking the hard
> disks but fsync calls can "sneak through". (IMHO this is a bug.)
>
> Proposed solution: Pretend the fsync was executed and successful.
> Insert two lines into the fsync and fdatasync calls in fs/sync.c:
> if (unlikely(laptop_mode))
> return 0;
No, no, no, no, no, no, no, no, no, no.
There is _absolutely no justification_ for putting people's data at
risk like this. If you want to do make fsync/fdatasync calls
no-ops, then go install libeatmydata on your systems. It's your
data, and you make the decision to risk it, not us.
And BTW, I just added your name to my "ignore fileystem/data
corruption bug reports from these people" list, because that's
exactly where you'll end up with if you follow this path.
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
next prev parent reply other threads:[~2011-05-20 3:39 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-19 13:34 [rfc] Ignore Fsync Calls in Laptop_Mode Dennis Jansen
2011-05-19 13:43 ` Alan Cox
[not found] ` <BANLkTikFRwPY_qOQpPmCmNUJbBUsGcuGUw@mail.gmail.com>
[not found] ` <20110519153928.40521b93@lxorguk.ukuu.org.uk>
2011-05-19 15:01 ` D. Jansen
2011-05-19 15:02 ` D. Jansen
2011-05-20 15:34 ` Valdis.Kletnieks
2011-05-20 3:39 ` Dave Chinner [this message]
2011-05-20 6:01 ` D. Jansen
2011-05-22 0:48 ` Dave Chinner
2011-05-23 8:12 ` Oliver Neukum
2011-05-23 13:05 ` D. Jansen
2011-05-25 0:00 ` Dave Chinner
2011-05-25 6:50 ` Oliver Neukum
2011-05-26 7:01 ` D. Jansen
2011-05-26 10:49 ` Theodore Tso
[not found] ` <BANLkTimNjt4=9v33Z9Nr12xa6GmyJ-Ue5A@mail.gmail.com>
2011-05-26 13:31 ` Ted Ts'o
2011-05-26 16:05 ` D. Jansen
2011-05-26 16:21 ` Ted Ts'o
2011-05-27 7:12 ` D. Jansen
2011-05-27 14:17 ` Theodore Tso
2011-05-27 17:51 ` david
2011-05-29 10:45 ` D. Jansen
2011-05-30 1:53 ` david
2011-05-30 7:13 ` Oliver Neukum
2011-05-30 12:55 ` Valdis.Kletnieks
2011-05-30 18:03 ` david
2011-05-30 13:55 ` D. Jansen
2011-05-30 18:02 ` david
2011-05-30 18:28 ` D. Jansen
2011-05-30 18:43 ` Valdis.Kletnieks
2011-05-30 19:54 ` D. Jansen
2011-05-30 18:45 ` david
2011-05-30 19:49 ` D. Jansen
2011-05-30 20:53 ` david
2011-05-30 21:24 ` D. Jansen
2011-05-30 22:41 ` david
2011-05-31 2:03 ` Ted Ts'o
2011-05-31 2:26 ` david
2011-05-31 13:47 ` D. Jansen
2011-05-31 18:23 ` david
2011-05-31 18:37 ` D. Jansen
2011-05-31 18:54 ` david
2011-05-31 19:04 ` D. Jansen
2011-06-02 7:42 ` D. Jansen
2011-05-31 8:22 ` Valdis.Kletnieks
2011-05-30 22:10 ` Jesper Juhl
2011-05-31 6:48 ` Oliver Neukum
2011-05-26 19:31 ` Matthew Garrett
2011-05-27 7:22 ` D. Jansen
2011-05-20 15:28 ` Valdis.Kletnieks
2011-05-20 16:40 ` D. Jansen
2011-05-20 22:03 ` torbenh
2011-05-21 8:23 ` D. Jansen
2011-05-23 8:22 ` Jesper Juhl
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=20110520033949.GQ32466@dastard \
--to=david@fromorbit.com \
--cc=akpm@linux-foundation.org \
--cc=d.g.jansen@googlemail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tytso@mit.edu \
/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.