From: Aaron Straus <aaron@merfinllc.com>
To: Chuck Lever <chuck.lever@oracle.com>
Cc: Neil Brown <neilb@suse.de>,
Linux NFS Mailing List <linux-nfs@vger.kernel.org>,
Trond Myklebust <trond.myklebust@fys.uio.no>,
LKML Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [NFS] blocks of zeros (NULLs) in NFS files in kernels >= 2.6.20
Date: Fri, 5 Sep 2008 17:03:51 -0700 [thread overview]
Message-ID: <20080906000351.GE12911@merfinllc.com> (raw)
In-Reply-To: <0A24B45A-9761-4310-B1DB-B4738964E862@oracle.com>
[-- Attachment #1: Type: text/plain, Size: 800 bytes --]
On Sep 05 03:56 PM, Chuck Lever wrote:
> > I can try to bisect between 2.6.19 <-> 2.6.20.
>
> That's a good start.
Hi,
OK. Bisected.
This is the commit where we start to see blocks of NULLs in NFS files.
e261f51f25b98c213e0b3d7f2109b117d714f69d is first bad commit
commit e261f51f25b98c213e0b3d7f2109b117d714f69d
Author: Trond Myklebust <Trond.Myklebust@netapp.com>
Date: Tue Dec 5 00:35:41 2006 -0500
NFS: Make nfs_updatepage() mark the page as dirty.
This will ensure that we can call set_page_writeback() from within
nfs_writepage(), which is always called with the page lock set.
Signed-off-by: Trond Myklebust <Trond.Myklebust@netapp.com>
Thanks,
=a=
--
===================
Aaron Straus
aaron@merfinllc.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 191 bytes --]
next prev parent reply other threads:[~2008-09-06 0:04 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-05 19:19 blocks of zeros (NULLs) in NFS files in kernels >= 2.6.20 Aaron Straus
2008-09-05 19:56 ` [NFS] " Chuck Lever
2008-09-05 20:04 ` Aaron Straus
2008-09-05 20:36 ` Bernd Eckenfels
2008-09-05 20:36 ` Chuck Lever
2008-09-05 22:14 ` Aaron Straus
2008-09-06 0:03 ` Aaron Straus [this message]
2008-09-08 19:02 ` Aaron Straus
2008-09-08 21:15 ` Chuck Lever
2008-09-08 22:02 ` Aaron Straus
2008-09-09 19:46 ` Aaron Straus
2008-09-11 16:55 ` Chuck Lever
2008-09-11 17:19 ` Aaron Straus
2008-09-11 17:48 ` Chuck Lever
2008-09-11 18:49 ` Aaron Straus
2008-09-22 16:05 ` Hans-Peter Jansen
2008-09-22 16:35 ` Trond Myklebust
2008-09-22 17:04 ` Aaron Straus
2008-09-22 17:26 ` Chuck Lever
2008-09-22 17:37 ` Aaron Straus
2008-09-22 17:29 ` Trond Myklebust
2008-09-22 17:45 ` Aaron Straus
2008-09-22 18:43 ` Aaron Straus
2008-09-22 18:45 ` Hans-Peter Jansen
2008-09-22 18:45 ` Hans-Peter Jansen
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=20080906000351.GE12911@merfinllc.com \
--to=aaron@merfinllc.com \
--cc=chuck.lever@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=neilb@suse.de \
--cc=trond.myklebust@fys.uio.no \
/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