From: "Albert Cahalan" <acahalan@gmail.com>
To: linux-kernel <linux-kernel@vger.kernel.org>
Subject: setting all 3 file times
Date: Sun, 20 May 2007 16:09:56 -0400 [thread overview]
Message-ID: <787b0d920705201309y16ba2778ob052fde375f0c58d@mail.gmail.com> (raw)
Why can we still not do this?
It's a stupid restriction. Security isn't a reason;
we have SE Linux policy and auditing to take
care of any issues. Heck, SE Linux policy could
even deny this feature for the truly paranoid.
Writing to /dev/* to update timestamps is surely
a worse security situation. (see "dump" program)
Ideally we'd have atomic update in some way.
That might mean feeding the old times into the
system call, so that the kernel can fail it if any
changes have happened meanwhile. Maybe the
syscall could take a pair of "struct stat" even,
making the operation really easy and powerful.
reply other threads:[~2007-05-20 20:10 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=787b0d920705201309y16ba2778ob052fde375f0c58d@mail.gmail.com \
--to=acahalan@gmail.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
all inboxes | Powered by JetHome®