linux-kernel - Re: NFS/AFS/Selinux issues with 2.26.29

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]

Message-Id: <1238020424.26487.81.camel@heimdal.trondhjem.org>
Date:	Wed, 25 Mar 2009 18:33:44 -0400
From:	Trond Myklebust <trond.myklebust@....uio.no>
To:	Richard A Nelson <cowboy@...ux.vnet.ibm.com>
Cc:	linux-kernel@...r.kernel.org, linux-nfs@...r.kernel.org,
	openafs-devel@...nafs.org
Subject: Re: NFS/AFS/Selinux issues with 2.26.29

On Wed, 2009-03-25 at 15:09 -0700, Richard A Nelson wrote:
> 1) 2.6.29 NFS clients can no longer lock files:
>    #strace -f lockfile fubar
>    ...
>    uname({sys="Linux", node="gothic-ave", ...}) = 0
>    lstat64("_V0H.jaqyJB.gothic-ave", 0xbfdac9ec) = -1 ENOENT (No such file or directory)
>    open("_V0H.jaqyJB.gothic-ave", O_WRONLY|O_CREAT|O_EXCL|O_LARGEFILE, 0444) = -1 EINVAL (Invalid argument)
>    write(2, "lockfile: ", 10lockfile: )              = 10
>    write(2, "Try praying", 11Try praying)             = 11
>    write(2, ", giving up on \"", 16, giving up on ")       = 16
>    write(2, "fubar", 5fubar)                    = 5
>    write(2, "\"\n", 2"
> 
>    clients still on 2.6.28 and lower work fine ... the server *is* 2.26.29

lockfile works fine for me, both on NFSv3 and NFSv4 against my NetApp
filers, and as far as I can remember, there have been no changes to the
exclusive create code in the 2.6.29 client.

Given that you are claiming to be seeing selinux problems on
2.6.29-based servers, could you therefore please check again after
downgrading the server kernel?

Trond

--
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/