mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Myklebust, Trond" <Trond.Myklebust@netapp.com>
To: Ken Moffat <zarniwhoop@ntlworld.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: nfs3 problem with -rc{2,3} : blame
Date: Tue, 19 Jun 2012 16:20:37 +0000	[thread overview]
Message-ID: <1340122836.3754.9.camel@lade.trondhjem.org> (raw)
In-Reply-To: <20120619010641.GA22288@milliways>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="utf-8", Size: 2063 bytes --]

On Tue, 2012-06-19 at 02:06 +0100, Ken Moffat wrote:
> On Mon, Jun 18, 2012 at 11:10:52PM +0100, Ken Moffat wrote:
> > On Mon, Jun 18, 2012 at 10:03:24PM +0000, Myklebust, Trond wrote:
> > > 
> > > Doesn't 4f97615d19 fix the fs/nfs/direct.c problem too? It should.
> > > 
> > > Anyhow, if you can apply that on top of the commits that didn't compile,
> > > and then continue the bisection, that would be great. We definitely do
> > > want the !defined(CONFIG_NFS_V4) case to work in 3.5-final...
> > > 
> >  OK (I was assuming errors in different places were from different
> > causes).  I'll do that after I've rerun rc3 without NFS_V4 with
> > SUNRPC_DEBUG.  Thanks.
> 
> Bisection now points to:
> 
> 6d74743b088d116e31fe1b73f47e782ee2016b94 is the first bad commit
> commit 6d74743b088d116e31fe1b73f47e782ee2016b94
> Author: Trond Myklebust <Trond.Myklebust@netapp.com>
> Date:   Mon Apr 30 13:27:31 2012 -0400
> 
>     NFS: Simplify O_DIRECT page referencing
>     
>     The O_DIRECT code shouldn't need to hold 2 references to each
> page. The
>     reference held by the struct nfs_page should suffice.
>     
>     Signed-off-by: Trond Myklebust <Trond.Myklebust@netapp.com>
>     Cc: Fred Isaman <iisaman@netapp.com>
> 
>  I was going to revert that from 3.5.0-rc3 to confirm that my
> problem with backups was gone, and then give it more extended
> testing to prove firefox downloads were ok, but 6 of 11 hunks
> failed, the code has changed and I'm not familiar with it.

However you are saying that the problem is there when you compile a
kernel with this commit as the head, and it goes away when you compile a
kernel with commit 3e9e0ca3f19e911ce13c2e6c9858fcb41a37496c as the head?

I'm confused as to how a bug in that patch could depend on
CONFIG_NFS_V4, but I'll see what I can find.

-- 
Trond Myklebust
Linux NFS client maintainer

NetApp
Trond.Myklebust@netapp.com
www.netapp.com

ÿôèº{.nÇ+‰·Ÿ®‰­†+%ŠËÿ±éݶ\x17¥Šwÿº{.nÇ+‰·¥Š{±þG«éÿŠ{ayº\x1dʇڙë,j\a­¢f£¢·hšïêÿ‘êçz_è®\x03(­éšŽŠÝ¢j"ú\x1a¶^[m§ÿÿ¾\a«þG«éÿ¢¸?™¨è­Ú&£ø§~á¶iO•æ¬z·švØ^\x14\x04\x1a¶^[m§ÿÿÃ\fÿ¶ìÿ¢¸?–I¥

  reply	other threads:[~2012-06-19 16:20 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-17 20:07 nfs3 problem with -rc{2,3} Ken Moffat
2012-06-18  1:11 ` Ken Moffat
2012-06-18 13:42 ` Myklebust, Trond
2012-06-18 13:45   ` Myklebust, Trond
2012-06-18 14:18     ` Ken Moffat
2012-06-18 14:53       ` Myklebust, Trond
2012-06-18 16:00         ` Ken Moffat
2012-06-18 20:05           ` Ken Moffat
2012-06-18 20:11             ` Myklebust, Trond
2012-06-18 23:38               ` Ken Moffat
2012-06-18 23:44                 ` Ken Moffat
2012-06-18 21:53             ` Ken Moffat
2012-06-18 22:03               ` Myklebust, Trond
2012-06-18 22:10                 ` Ken Moffat
2012-06-19  1:06                   ` nfs3 problem with -rc{2,3} : blame Ken Moffat
2012-06-19 16:20                     ` Myklebust, Trond [this message]
2012-06-19 16:23                       ` Myklebust, Trond
2012-06-19 16:55                         ` Ken Moffat
2012-06-19 17:46                           ` Myklebust, Trond
2012-06-19 19:35                             ` Ken Moffat
2012-06-19 22:44                               ` Myklebust, Trond
2012-06-19 23:31                                 ` Ken Moffat

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=1340122836.3754.9.camel@lade.trondhjem.org \
    --to=trond.myklebust@netapp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=zarniwhoop@ntlworld.com \
    /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®