linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Nick Piggin <npiggin@suse.de>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Miklos Szeredi <miklos@szeredi.hu>,
	Christoph Hellwig <hch@lst.de>,
	drepper@redhat.com, viro@zeniv.linux.org.uk,
	linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH 2/2] add f_flags to struct statfs(64)
Date: Thu, 8 Jul 2010 04:50:32 +1000	[thread overview]
Message-ID: <20100707185032.GH9263@laptop> (raw)
In-Reply-To: <AANLkTimP0vhIWEebU27ndSHf48SCRs9YhJJCGfG0KJnC@mail.gmail.com>

On Wed, Jul 07, 2010 at 11:06:29AM -0700, Linus Torvalds wrote:
> On Wed, Jul 7, 2010 at 10:55 AM, Miklos Szeredi <miklos@szeredi.hu> wrote:
> >
> > 1.0     - doesn't touch spare fields
> > 1.2.13  - doesn't touch spare fields
> > 2.0.40  - copies spare fields from uninitialized kernel stack
> > 2.2.26  - copies spare fields from uninitialized kernel stack
> > 2.4 onward - zeroes spare fields
> 
> I think at least some of the compat_ functions don't zero  the fields
> even now (the kstatfs struct, yes, but then don't copy them to user
> space).
> 
> As to any uninitialized kernel stack copying, we really don't even
> want to care. Not only are those ancient kernels (and nobody is going
> to upgrade glibc if they haven't upgraded the kernel), but it's
> clearly a kernel bug, and the potential "wrong f_flags" problem is way
> smaller than the "leaks kernel data" problem.
> 
> Not that anybody even uses statvfs(). The first google hit on
> statvfs() I found was somebody implementing a compatibility statfs()
> on top of it, and obviously ignoring any f_flags field. So the only
> reason this is even an issue in the first place is just the tbench
> performance issue.
> 
> In other words: NOBODY CARES. It's that simple. So please, guys - just
> do the obvious thing, or shut the h*ll up about it. There is _no_
> reason to care in the least about any of this.

Well we do want to be simple I think, but it's not *totally* just
for dbench performance :) Actually dbench is supposed to be an fs
syscall reply of samba running a file server workload. For one
reason or another, it calls statvfs a lot.

Not sure if anything else is remotely performance critical, but statvfs
is preferred these days for portability, so proper atomicity of f_flags is
nice too.

--
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-07-07 18:50 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-07 16:53 [PATCH 2/2] add f_flags to struct statfs(64) 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 [this message]
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
  -- strict thread matches above, loose matches on Subject: below --
2010-06-26  9:35 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
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

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=20100707185032.GH9263@laptop \
    --to=npiggin@suse.de \
    --cc=drepper@redhat.com \
    --cc=hch@lst.de \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=miklos@szeredi.hu \
    --cc=torvalds@linux-foundation.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).