linux-kernel - Re: nfs3 problem with -rc{2,3}

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 18 Jun 2012 21:05:25 +0100
From:	Ken Moffat <zarniwhoop@...world.com>
To:	"Myklebust, Trond" <Trond.Myklebust@...app.com>
Cc:	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: nfs3 problem with -rc{2,3}

On Mon, Jun 18, 2012 at 05:00:05PM +0100, Ken Moffat wrote:
> > 
> > OK. You said you had bisected this down to 15 patches? Can you please
> > tell me which ones?
> > 
> 
>  I'm just about to resume, to see if I can get anywhere - the rc2
> version built fine, so I'm guessing that some more of the remaining
> versions will also build.  Not sure which commits are still
> outstanding.
> 

 Turned out that almost everything from 3e9e0ca3 failed to compile,
until 4f97615d (fix for NFS_V4_1 undefined) resolved that, (only had
one or two still to try when I decided to use 'git visualize').  And
it was bad by 4f97615d.

 Added all the NFS v4 / 4.1 client options to my config :
3e9e0ca3 is now good, I'll start a fresh bisect between these two.

 Actually, I'd better retry 4f97515d to confirm it is still bad with
this config. [ saves this message, tests ... ].  Rude words!  If I
enable all the NFS v4 client options, 4f97615d is good.

 Looks, to me, as if something in that untested range of patches, or
in 3e9e0ca3 itself, causes the problem *if* nfs v4 is not enabled.

 I suppose I'll have to enable v4 in my configs.

ĸen
-- 
das eine Mal als Tragödie, das andere Mal als Farce
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/