All of lore.kernel.org
 help / color / mirror / Atom feed
From: Trond Myklebust <trond.myklebust@primarydata.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: Russell King - ARM Linux <linux@arm.linux.org.uk>,
	linuxnfs <linux-nfs@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Christoph Hellwig <hch@infradead.org>,
	Viro Alexander <viro@zeniv.linux.org.uk>,
	Christoph Hellwig <hch@lst.de>,
	linux-arm-kernel@lists.infradead.org
Subject: Re: NFS client broken in Linus' tip
Date: Mon, 3 Feb 2014 09:21:16 -0500	[thread overview]
Message-ID: <5ACE0C45-BEFA-47A8-9195-F3AB36C27752@primarydata.com> (raw)
In-Reply-To: <s5hioswy1iy.wl%tiwai@suse.de>


On Feb 3, 2014, at 4:43, Takashi Iwai <tiwai@suse.de> wrote:

> At Sun, 02 Feb 2014 17:04:38 -0500,
> Trond Myklebust wrote:
>> 
>> On Sun, 2014-02-02 at 12:27 +0000, Russell King - ARM Linux wrote:
>>> 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@cubox-i4:~# ls -al test
>>>> ls: cannot access test: No such file or directory
>>>> root@cubox-i4:~# touch test
>>>> root@cubox-i4:~# ls -al test
>>>> -rw-r--r-- 1 root root 0 Feb  1 01:01 test
>>>> root@cubox-i4:~# echo foo > test
>>>> root@cubox-i4:~# ls -al test
>>>> -rw-r--r-- 1 root root 4 Feb  1 01:01 test
>>>> root@cubox-i4:~# cat test
>>>> foo
>>>> root@cubox-i4:~# rm test
>>>> root@cubox-i4:~# echo foo > test
>>>> -bash: test: Operation not supported
>>>> root@cubox-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.
>>> 
>> Hi Russell,
>> 
>> The following patch should fix the above problem. It needs to be applied
>> on top of the one I sent you previously.
> 
> I've hit the same problem, and your two patches seem fixing it.
> I tested them on top of 3.14-rc1.  Feel free to take my tested-by tag
> 
>  Tested-by: Takashi Iwai <tiwai@suse.de>
> 
> 
>> In addition, you will want to
>> apply Noah Massey's patch from
>> http://lkml.kernel.org/r/1391135472-9639-1-git-send-email-Noah.Massey@gmail.com 
> 
> Do I still need to test this one, too?
> 

Hi Takashi,

Noah’s patch is not a replacement for the above 2 patches; it fixes a different problem. All three patches are therefore required for a complete solution.

Cheers
  Trond

--
Trond Myklebust
Linux NFS client maintainer


WARNING: multiple messages have this Message-ID (diff)
From: trond.myklebust@primarydata.com (Trond Myklebust)
To: linux-arm-kernel@lists.infradead.org
Subject: NFS client broken in Linus' tip
Date: Mon, 3 Feb 2014 09:21:16 -0500	[thread overview]
Message-ID: <5ACE0C45-BEFA-47A8-9195-F3AB36C27752@primarydata.com> (raw)
In-Reply-To: <s5hioswy1iy.wl%tiwai@suse.de>


On Feb 3, 2014, at 4:43, Takashi Iwai <tiwai@suse.de> wrote:

> At Sun, 02 Feb 2014 17:04:38 -0500,
> Trond Myklebust wrote:
>> 
>> On Sun, 2014-02-02 at 12:27 +0000, Russell King - ARM Linux wrote:
>>> 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 at cubox-i4:~# ls -al test
>>>> ls: cannot access test: No such file or directory
>>>> root at cubox-i4:~# touch test
>>>> root at cubox-i4:~# ls -al test
>>>> -rw-r--r-- 1 root root 0 Feb  1 01:01 test
>>>> root at cubox-i4:~# echo foo > test
>>>> root at cubox-i4:~# ls -al test
>>>> -rw-r--r-- 1 root root 4 Feb  1 01:01 test
>>>> root at cubox-i4:~# cat test
>>>> foo
>>>> root at cubox-i4:~# rm test
>>>> root at cubox-i4:~# echo foo > test
>>>> -bash: test: Operation not supported
>>>> root at cubox-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.
>>> 
>> Hi Russell,
>> 
>> The following patch should fix the above problem. It needs to be applied
>> on top of the one I sent you previously.
> 
> I've hit the same problem, and your two patches seem fixing it.
> I tested them on top of 3.14-rc1.  Feel free to take my tested-by tag
> 
>  Tested-by: Takashi Iwai <tiwai@suse.de>
> 
> 
>> In addition, you will want to
>> apply Noah Massey's patch from
>> http://lkml.kernel.org/r/1391135472-9639-1-git-send-email-Noah.Massey at gmail.com 
> 
> Do I still need to test this one, too?
> 

Hi Takashi,

Noah?s patch is not a replacement for the above 2 patches; it fixes a different problem. All three patches are therefore required for a complete solution.

Cheers
  Trond

--
Trond Myklebust
Linux NFS client maintainer

  reply	other threads:[~2014-02-03 14:21 UTC|newest]

Thread overview: 52+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-30 14:08 NFS client broken in Linus' tip Russell King - ARM Linux
2014-01-30 14:08 ` Russell King - ARM Linux
2014-01-30 14:14 ` Christoph Hellwig
2014-01-30 14:14   ` Christoph Hellwig
2014-01-30 14:27   ` Russell King - ARM Linux
2014-01-30 14:27     ` Russell King - ARM Linux
2014-01-30 14:32     ` Christoph Hellwig
2014-01-30 14:32       ` Christoph Hellwig
2014-01-30 15:38       ` Russell King - ARM Linux
2014-01-30 15:38         ` Russell King - ARM Linux
2014-01-31 20:59         ` Trond Myklebust
2014-01-31 20:59           ` Trond Myklebust
2014-02-01  1:03           ` Russell King - ARM Linux
2014-02-01  1:03             ` Russell King - ARM Linux
2014-02-02 12:27             ` Russell King - ARM Linux
2014-02-02 12:27               ` Russell King - ARM Linux
2014-02-02 22:04               ` Trond Myklebust
2014-02-02 22:04                 ` Trond Myklebust
2014-02-03  9:43                 ` Takashi Iwai
2014-02-03  9:43                   ` Takashi Iwai
2014-02-03 14:21                   ` Trond Myklebust [this message]
2014-02-03 14:21                     ` Trond Myklebust
2014-02-03 14:24                     ` Takashi Iwai
2014-02-03 14:24                       ` Takashi Iwai
2014-02-03  8:03           ` Christoph Hellwig
2014-02-03  8:03             ` Christoph Hellwig
2014-02-03 14:17             ` Trond Myklebust
2014-02-03 14:17               ` Trond Myklebust
2014-02-03 14:57               ` Christoph Hellwig
2014-02-03 14:57                 ` Christoph Hellwig
2014-02-03 15:45                 ` Trond Myklebust
2014-02-03 15:45                   ` Trond Myklebust
2014-02-03 20:22                   ` Trond Myklebust
2014-02-03 20:22                     ` Trond Myklebust
2014-02-03 20:25                     ` Russell King - ARM Linux
2014-02-03 20:25                       ` Russell King - ARM Linux
2014-02-03 20:25                     ` Christoph Hellwig
2014-02-03 20:25                       ` Christoph Hellwig
2014-02-03 20:32                       ` Trond Myklebust
2014-02-03 20:32                         ` Trond Myklebust
2014-02-03 20:54           ` Christoph Hellwig
2014-02-03 20:54             ` Christoph Hellwig
2014-01-30 14:17 ` Trond Myklebust
2014-01-30 14:17   ` Trond Myklebust
2014-01-30 14:30   ` Russell King - ARM Linux
2014-01-30 14:30     ` Russell King - ARM Linux
2014-01-30 14:45     ` Trond Myklebust
2014-01-30 14:45       ` Trond Myklebust
2014-01-30 15:17 ` Root NFS panicing on Linus' tip (Re: NFS client broken in Linus' tip) Ezequiel Garcia
2014-01-30 15:17   ` Ezequiel Garcia
2014-01-30 16:08   ` Russell King - ARM Linux
2014-01-30 16:08     ` Russell King - ARM Linux

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=5ACE0C45-BEFA-47A8-9195-F3AB36C27752@primarydata.com \
    --to=trond.myklebust@primarydata.com \
    --cc=hch@infradead.org \
    --cc=hch@lst.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --cc=tiwai@suse.de \
    --cc=viro@zeniv.linux.org.uk \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.