linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ulrich Drepper <drepper@redhat.com>
To: Andreas Dilger <adilger@dilger.ca>
Cc: Christoph Hellwig <hch@lst.de>,
	viro@zeniv.linux.org.uk, linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH 2/2] add f_flags to struct statfs(64)
Date: Mon, 28 Jun 2010 12:52:56 -0700	[thread overview]
Message-ID: <4C28FD98.1010300@redhat.com> (raw)
In-Reply-To: <60FB0305-A632-4A63-9BD8-DA07CC69B7D7@dilger.ca>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 06/28/2010 11:43 AM, Andreas Dilger wrote:
> I would advocate at least an 8-bit magic value, if there is a concern
> about this field not always being 0-filled on older kernels, or not
> using any ST_VALID flag at all, if it was always zero-filled in the
> past.

Did anyone go back and check which kernel versions didn't clear the
spare fields (if any)?

Instead of using a magic number which doesn't provide 100% security in
that case and steals a number of bits which might be needed in future I
rather see a new syscall.  The new {,f}statfs would be an alias for the
old one, exactly the same implementation.  With this it is much safer to
check for the new kernel behavior.  In future this isn't necessary since
from point on it is guaranteed that the spare bits are zeroed.

- -- 
➧ Ulrich Drepper ➧ Red Hat, Inc. ➧ 444 Castro St ➧ Mountain View, CA ❖
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.14 (GNU/Linux)

iEYEARECAAYFAkwo/ZgACgkQ2ijCOnn/RHSdVQCgzgHQj5A3/MLSYMbxX2xotoye
aPsAnRzGEK0pz7LYQ9mIYUHa/upoFuoS
=3oan
-----END PGP SIGNATURE-----
--
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2010-06-28 19:53 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-26  9:35 [PATCH 2/2] add f_flags to struct statfs(64) Christoph Hellwig
2010-06-26  9:56 ` Nick Piggin
2010-06-26 13:09   ` Christoph Hellwig
2010-06-26 13:16     ` Nick Piggin
2010-06-26 12:55 ` Neil Brown
2010-06-26 13:12   ` Christoph Hellwig
2010-06-27  7:55 ` Tao Ma
2010-06-27  9:20   ` Christoph Hellwig
2010-06-28 18:43 ` Andreas Dilger
2010-06-28 19:52   ` Ulrich Drepper [this message]
2010-06-28 20:07     ` Andreas Dilger
2010-06-29  8:57     ` Nick Piggin
2010-06-29  9:25       ` Christoph Hellwig
2010-06-29  9:59       ` Ulrich Drepper
2010-06-29 11:05         ` Nick Piggin
2010-06-29 12:57         ` Christoph Hellwig
  -- strict thread matches above, loose matches on Subject: below --
2010-07-07 16:53 Christoph Hellwig
2010-07-07 17:11 ` Ulrich Drepper
2010-07-07 17:31   ` Linus Torvalds
2010-07-07 17:33     ` Christoph Hellwig
2010-07-07 17:55       ` Miklos Szeredi
2010-07-07 18:06         ` Linus Torvalds
2010-07-07 18:50           ` Nick Piggin
2010-07-07 19:30             ` Linus Torvalds
2010-07-18  6:41               ` Christoph Hellwig
2010-07-18 17:03                 ` Linus Torvalds
2010-07-07 18:16       ` Nick Piggin

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=4C28FD98.1010300@redhat.com \
    --to=drepper@redhat.com \
    --cc=adilger@dilger.ca \
    --cc=hch@lst.de \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=viro@zeniv.linux.org.uk \
    /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;
as well as URLs for NNTP newsgroup(s).