linux-kernel - Re: nfs broken in net-next? -- now in mainline

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-next>] [day] [month] [year] [list]

Message-ID: <86802c440912091234t74fd2311t33c85379c06dd55c@mail.gmail.com>
Date:	Wed, 9 Dec 2009 12:34:36 -0800
From:	Yinghai Lu <yhlu.kernel@...il.com>
To:	Suresh Jayaraman <sjayaraman@...e.de>, Ingo Molnar <mingo@...e.hu>,
	Linus Torvalds <torvalds@...ux-foundation.org>
Cc:	David Miller <davem@...emloft.net>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	NetDev <netdev@...r.kernel.org>
Subject: Re: nfs broken in net-next? -- now in mainline

On Thu, Oct 29, 2009 at 2:03 AM, Yinghai Lu <yhlu.kernel@...il.com> wrote:
> On Thu, Oct 29, 2009 at 12:23 AM, Suresh Jayaraman <sjayaraman@...e.de> wrote:
>> On 10/29/2009 01:43 AM, Yinghai Lu wrote:
>>> pk12-3214-189-102:~ # mount -t nfs 10.6.75.100:/data/shared/pxeboot /x
>>> mount.nfs: rpc.statd is not running but is required for remote locking.
>>> mount.nfs: Either use '-o nolock' to keep locks local, or start statd.
>>
>> rpc.statd on client should have be started by mount.nfs when a nfs
>> filesystem is mounted. Is this not happening for some reason or do you
>> see any errors in syslog?
>>
>>>
>>> using opensuse11.1
>>>
>>
>> Are you using 11.1 betas? I know of a problem where non-root user mounts
>> fail to start rpc.statd in betas that got fixed later:
>>
>> http://marc.info/?l=linux-nfs&m=122748525624094&w=2
>>
>> Is the problem seen only recently (after updating to net-next)?
>>
>
> only happen with net-next.
>
> linus tree and tip tree are ok.
>

Finally it reached linus tree and tip.

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