linux-kernel - Re: NFS client broken in Linus' tip

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 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:	Sun, 2 Feb 2014 12:27:58 +0000
From:	Russell King - ARM Linux <linux@....linux.org.uk>
To:	Trond Myklebust <trond.myklebust@...marydata.com>
Cc:	linux-nfs@...r.kernel.org, linux-kernel@...r.kernel.org,
	Christoph Hellwig <hch@...radead.org>,
	Al Viro <viro@...iv.linux.org.uk>,
	Christoph Hellwig <hch@....de>,
	linux-arm-kernel@...ts.infradead.org
Subject: Re: NFS client broken in Linus' tip

On Sat, Feb 01, 2014 at 01:03:28AM +0000, Russell King - ARM Linux wrote:
> On Fri, Jan 31, 2014 at 03:59:30PM -0500, Trond Myklebust wrote:
> > On Thu, 2014-01-30 at 15:38 +0000, Russell King - ARM Linux wrote:
> > > On Thu, Jan 30, 2014 at 06:32:08AM -0800, Christoph Hellwig wrote:
> > > > On Thu, Jan 30, 2014 at 02:27:52PM +0000, Russell King - ARM Linux wrote:
> > > > > Yes and no.  I still end up with an empty /etc/mtab, but the file now
> > > > > exists.  However, I can create and echo data into /etc/mtab, but it seems
> > > > > that can't happen at boot time.
> > > > 
> > > > Odd.  Can you disable CONFIG_NFSD_V3_ACL for now to isolate the issue?
> > > 
> > > Unfortunately, that results in some problem at boot time, which
> > > ultimately ends up with the other three CPUs being stopped, and
> > > hence the original reason scrolls off the screen before it can be
> > > read... even at 1920p.
> > > 
> > Hi Russell,
> > 
> > The following patch fixes the issue for me.
> 
> It doesn't entirely fix the issue for me, instead we've got even weirder
> behaviour:
> 
> root@...ox-i4:~# ls -al test
> ls: cannot access test: No such file or directory
> root@...ox-i4:~# touch test
> root@...ox-i4:~# ls -al test
> -rw-r--r-- 1 root root 0 Feb  1 01:01 test
> root@...ox-i4:~# echo foo > test
> root@...ox-i4:~# ls -al test
> -rw-r--r-- 1 root root 4 Feb  1 01:01 test
> root@...ox-i4:~# cat test
> foo
> root@...ox-i4:~# rm test
> root@...ox-i4:~# echo foo > test
> -bash: test: Operation not supported
> root@...ox-i4:~# ls -al test
> -rw-r--r-- 1 root root 0 Feb  1 01:01 test

FYI, I just tested Linus' tip, and NFS is still broken.

-- 
FTTC broadband for 0.8mile line: 5.8Mbps down 500kbps up.  Estimation
in database were 13.1 to 19Mbit for a good line, about 7.5+ for a bad.
Estimate before purchase was "up to 13.2Mbit".
--
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/