public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: ebiederm@xmission.com (Eric W. Biederman)
To: Andi Kleen <ak@suse.de>
Cc: Jamie Lokier <lk@tantalophile.demon.co.uk>,
	"David S. Miller" <davem@redhat.com>,
	taka@valinux.co.jp, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] zerocopy NFS updated
Date: 13 Apr 2002 13:19:46 -0600	[thread overview]
Message-ID: <m1662vjtil.fsf@frodo.biederman.org> (raw)
In-Reply-To: <20020412.213011.45159995.taka@valinux.co.jp> <20020412143559.A25386@wotan.suse.de> <20020412222252.A25184@kushida.apsleyroad.org> <20020412.143150.74519563.davem@redhat.com> <20020413012142.A25295@kushida.apsleyroad.org> <20020413083952.A32648@wotan.suse.de>

Andi Kleen <ak@suse.de> writes:

> > I wonder if it is reasonable to depend on that: -- i.e. I'll only ever
> > see zeros, not say random bytes, or ones or something.  I'm sure that's
> > so with the current kernel, and probably all of them ever (except for
> > bugs) but I wonder whether it's ok to rely on that.
> 
> With truncates you should only ever see zeros. If you want this guarantee
> over system crashes you need to make sure to use the right file system
> though (e.g. ext2 or reiserfs without the ordered data mode patches or
> ext3 in writeback mode could give you junk if the system crashes at the
> wrong time). Still depending on only seeing zeroes would
> seem to be a bit fragile on me (what happens when the disk dies for 
> example?), using some other locking protocol is probably more safe.

Could the garbage from ext3 in writeback mode be considered an
information leak?  I know that is why most places in the kernel
initialize pages to 0.  So you don't accidentally see what another
user put there.

Eric
k

  parent reply	other threads:[~2002-04-13 19:26 UTC|newest]

Thread overview: 55+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20020410.190550.83626375.taka@valinux.co.jp.suse.lists.linux.kernel>
2002-04-10 19:32 ` [PATCH] zerocopy NFS updated Andi Kleen
2002-04-11  2:30   ` David S. Miller
2002-04-11  6:46     ` Hirokazu Takahashi
2002-04-11  6:48       ` David S. Miller
2002-04-11  7:41         ` Hirokazu Takahashi
2002-04-11  7:52           ` David S. Miller
2002-04-11 11:38             ` Hirokazu Takahashi
2002-04-11 11:36               ` David S. Miller
2002-04-11 18:00                 ` Denis Vlasenko
2002-04-11 13:16                   ` Andi Kleen
2002-04-11 17:36                     ` Benjamin LaHaise
2002-04-16  0:17                     ` Mike Fedyk
2002-04-16 15:37                       ` Oliver Xymoron
2002-04-11 17:33             ` Benjamin LaHaise
2002-04-12  8:10               ` Hirokazu Takahashi
2002-04-12 12:30         ` Hirokazu Takahashi
2002-04-12 12:35           ` Andi Kleen
2002-04-12 21:22             ` Jamie Lokier
2002-04-12 21:31               ` David S. Miller
2002-04-13  0:21                 ` Jamie Lokier
2002-04-13  6:39                   ` Andi Kleen
2002-04-13  8:01                     ` Hirokazu Takahashi
2002-04-13 19:19                     ` Eric W. Biederman [this message]
2002-04-13 19:37                       ` Andi Kleen
2002-04-13 20:34                         ` Eric W. Biederman
2002-04-24 23:11                           ` Mike Fedyk
2002-04-25 17:11                             ` Andreas Dilger
2002-04-13 18:52                 ` Chris Wedgwood
2002-04-14  0:07                   ` Keith Owens
2002-04-14  8:19                     ` Chris Wedgwood
2002-04-14  8:40                       ` Keith Owens
2002-04-12 21:39             ` David S. Miller
2002-04-15  1:30               ` Hirokazu Takahashi
2002-04-15  4:23                 ` David S. Miller
2002-04-16  1:03                   ` Hirokazu Takahashi
2002-04-16  1:41                     ` Jakob Østergaard
2002-04-16  2:20                       ` Hirokazu Takahashi
2002-04-18  5:01                       ` Hirokazu Takahashi
2002-04-18  7:58                         ` Jakob Østergaard
2002-04-18  8:53                         ` Trond Myklebust
2002-04-19  3:21                           ` Hirokazu Takahashi
2002-04-19  9:18                             ` Trond Myklebust
2002-04-20  7:47                               ` Hirokazu Takahashi
2002-04-25 12:37                                 ` Possible bug with UDP and SO_REUSEADDR. Was " Terje Eggestad
2002-04-26  2:43                                   ` David S. Miller
2002-04-26  7:38                                     ` Terje Eggestad
2002-04-29  0:41                                     ` Possible bug with UDP and SO_REUSEADDR David Schwartz
2002-04-29  8:06                                       ` Terje Eggestad
2002-04-29  8:44                                         ` David Schwartz
2002-04-29 10:03                                           ` Terje Eggestad
2002-04-29 10:38                                             ` David Schwartz
2002-04-29 14:20                                               ` Terje Eggestad
     [not found]                               ` <200204192128.QAA24592@popmail.austin.ibm.com>
2002-04-20 10:14                                 ` [PATCH] zerocopy NFS updated Hirokazu Takahashi
2002-04-20 15:49                                   ` Andrew Theurer
2002-04-10 10:05 Hirokazu Takahashi

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=m1662vjtil.fsf@frodo.biederman.org \
    --to=ebiederm@xmission.com \
    --cc=ak@suse.de \
    --cc=davem@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lk@tantalophile.demon.co.uk \
    --cc=taka@valinux.co.jp \
    /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