linux-kernel - Re: BUG at net/sunrpc/svc

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]

Date:	Fri, 18 Jan 2013 10:56:31 -0500
From:	"J. Bruce Fields" <bfields@...ldses.org>
To:	Mark Lord <kernel@...savvy.com>
Cc:	Stanislav Kinsbursky <skinsbursky@...allels.com>,
	linux-nfs@...r.kernel.org,
	Linux Kernel <linux-kernel@...r.kernel.org>
Subject: Re: BUG at net/sunrpc/svc_xprt.c:921

On Fri, Jan 18, 2013 at 10:48:02AM -0500, Mark Lord wrote:
> On 13-01-18 12:37 AM, Stanislav Kinsbursky wrote:
> >
> > You have more than one NFS mount in different network namespaces, haven't you?
> >
> 
> No, I don't (knowingly) use (multiple) namespaces at all.

Right, I don't think that's necessary.  Stanislav, look at
nfs_callback_down:

	nfs_callback_down_net(minorversion, cb_info->serv, net);
        cb_info->users--;
	if (cb_info->users == 0 && cb_info->task != NULL) {
		kthread_stop(cb_info->task);
		...

It's first destroying the service, then destroying the thread.  That's
the wrong order.  So we could still have the thread running svc_recv()
after the rpc service is destroyed.

--b.

> Usually I disable them in the kernel .config,
> though it appears the currently running kernel has this:
> 
> CONFIG_NAMESPACES=y
> # CONFIG_UTS_NS is not set
> # CONFIG_IPC_NS is not set
> # CONFIG_PID_NS is not set
> # CONFIG_NET_NS is not set
> 
> The full .config was attached to the first post in this thread.
> 
> Cheers
> 
--
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/