From: "Stephen C. Tweedie" <sct@redhat.com>
To: Bill Davidsen <davidsen@tmr.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Stephen Tweedie <sct@redhat.com>
Subject: Re: RFC: one solution to sys_sync livelock fix
Date: Fri, 15 Feb 2002 18:19:32 +0000 [thread overview]
Message-ID: <20020215181932.B5074@redhat.com> (raw)
In-Reply-To: <Pine.LNX.3.96.1020213172509.12448G-100000@gatekeeper.tmr.com>
In-Reply-To: <Pine.LNX.3.96.1020213172509.12448G-100000@gatekeeper.tmr.com>; from davidsen@tmr.com on Wed, Feb 13, 2002 at 05:37:42PM -0500
Hi,
On Wed, Feb 13, 2002 at 05:37:42PM -0500, Bill Davidsen wrote:
> What would happen if the sync(2) call from a non-root user were treated as
> if it were an fsync(2) call on every file open for write?
Then you'd lose writes for files you have written to but since
closed; and you'd seriously hurt the users of journaling filesystems
who assume you can "sync" as an unprivileged user and then turn power
off.
--Stephen
next prev parent reply other threads:[~2002-02-15 18:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-13 22:37 RFC: one solution to sys_sync livelock fix Bill Davidsen
2002-02-15 18:19 ` Stephen C. Tweedie [this message]
2002-02-17 12:36 ` Bill Davidsen
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=20020215181932.B5074@redhat.com \
--to=sct@redhat.com \
--cc=davidsen@tmr.com \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox