linux-kernel - Re: [PATCH 0/3] SUNRPC: three bugfixes for PipeFS event handling

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: <20120425182409.GE751@fieldses.org>
Date:	Wed, 25 Apr 2012 14:24:09 -0400
From:	"J. Bruce Fields" <bfields@...ldses.org>
To:	Stanislav Kinsbursky <skinsbursky@...allels.com>
Cc:	Trond.Myklebust@...app.com, linux-nfs@...r.kernel.org,
	linux-kernel@...r.kernel.org, devel@...nvz.org
Subject: Re: [PATCH 0/3] SUNRPC: three bugfixes for PipeFS event handling

On Fri, Apr 20, 2012 at 06:18:59PM +0400, Stanislav Kinsbursky wrote:
> These bugfixes were caught (or noticed) due to the following simple script:

I'm assuming Trond should take these (possibly for 3.4?).

--b.

> 
> ======================================================================
> 
> #!/bin/bash
> service rpcbind stop
> service rpcidmapd stop
> killall -TERM rpc.statd
> umount /var/lib/nfs/rpc_pipefs
> rmmod nfs
> service rpcbind start
> service nfs start
> mount -t rpc_pipefs sunrpc /var/lib/nfs/rpc_pipefs
> 
> =======================================================================
> 
> The following series consists of:
> 
> ---
> 
> Stanislav Kinsbursky (3):
>       SUNRPC: skip clients with program without PipeFS entries
>       SUNRPC: traverse clients tree on PipeFS event
>       SUNRPC: set per-net PipeFS superblock before notification
> 
> 
>  net/sunrpc/clnt.c     |   34 ++++++++++++++++++++++++++++------
>  net/sunrpc/rpc_pipe.c |    3 ++-
>  2 files changed, 30 insertions(+), 7 deletions(-)
> 
--
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/