linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "J. Bruce Fields" <bfields@fieldses.org>
To: bjschuma@netapp.com
Cc: Trond.Myklebust@netapp.com, linux-nfs@vger.kernel.org
Subject: Re: [PATCH] SUNRPC: Set alloc_slot for backchannel tcp ops
Date: Mon, 24 Sep 2012 13:42:46 -0400	[thread overview]
Message-ID: <20120924174246.GA12238@fieldses.org> (raw)
In-Reply-To: <1348508341-19642-1-git-send-email-bjschuma@netapp.com>

On Mon, Sep 24, 2012 at 01:39:01PM -0400, bjschuma@netapp.com wrote:
> From: Bryan Schumaker <bjschuma@netapp.com>
> 
> f39c1bfb5a03e2d255451bff05be0d7255298fa4 (SUNRPC: Fix a UDP transport
> regression) introduced the "alloc_slot" function for xprt operations,
> but never created one for the backchannel operations.  This patch fixes
> a null pointer dereference when mounting NFS over v4.1.

Thanks, I just rebased some of my work to 3.6 and ran across that!  It
crashes the 4.1 server very quickly....

--b.

> 
> Call Trace:
>  [<ffffffffa0207957>] ? xprt_reserve+0x47/0x50 [sunrpc]
>  [<ffffffffa02023a4>] call_reserve+0x34/0x60 [sunrpc]
>  [<ffffffffa020e280>] __rpc_execute+0x90/0x400 [sunrpc]
>  [<ffffffffa020e61a>] rpc_async_schedule+0x2a/0x40 [sunrpc]
>  [<ffffffff81073589>] process_one_work+0x139/0x500
>  [<ffffffff81070e70>] ? alloc_worker+0x70/0x70
>  [<ffffffffa020e5f0>] ? __rpc_execute+0x400/0x400 [sunrpc]
>  [<ffffffff81073d1e>] worker_thread+0x15e/0x460
>  [<ffffffff8145c839>] ? preempt_schedule+0x49/0x70
>  [<ffffffff81073bc0>] ? rescuer_thread+0x230/0x230
>  [<ffffffff81079603>] kthread+0x93/0xa0
>  [<ffffffff81465d04>] kernel_thread_helper+0x4/0x10
>  [<ffffffff81079570>] ? kthread_freezable_should_stop+0x70/0x70
>  [<ffffffff81465d00>] ? gs_change+0x13/0x13
> 
> Signed-off-by: Bryan Schumaker <bjschuma@netapp.com>
> ---
>  net/sunrpc/xprtsock.c | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/net/sunrpc/xprtsock.c b/net/sunrpc/xprtsock.c
> index 86b7777..aaaadfb 100644
> --- a/net/sunrpc/xprtsock.c
> +++ b/net/sunrpc/xprtsock.c
> @@ -2521,6 +2521,7 @@ static struct rpc_xprt_ops xs_tcp_ops = {
>  static struct rpc_xprt_ops bc_tcp_ops = {
>  	.reserve_xprt		= xprt_reserve_xprt,
>  	.release_xprt		= xprt_release_xprt,
> +	.alloc_slot		= xprt_alloc_slot,
>  	.rpcbind		= xs_local_rpcbind,
>  	.buf_alloc		= bc_malloc,
>  	.buf_free		= bc_free,
> -- 
> 1.7.12.1
> 
> --
> To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2012-09-24 17:42 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-24 17:39 [PATCH] SUNRPC: Set alloc_slot for backchannel tcp ops bjschuma
2012-09-24 17:42 ` J. Bruce Fields [this message]
2012-09-24 17:52   ` Bryan Schumaker
2012-09-24 19:31     ` Myklebust, Trond
2012-09-25 19:08       ` J. Bruce Fields
2012-10-19 19:39 ` J. Bruce Fields
2012-10-19 20:23   ` Myklebust, Trond
2012-10-19 21:01     ` J. Bruce Fields
2012-10-19 21:05       ` Myklebust, Trond
2012-10-19 21:11         ` J. Bruce Fields
2012-10-27 23:25   ` Ben Hutchings
  -- strict thread matches above, loose matches on Subject: below --
2012-10-22 16:35 Trond Myklebust

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=20120924174246.GA12238@fieldses.org \
    --to=bfields@fieldses.org \
    --cc=Trond.Myklebust@netapp.com \
    --cc=bjschuma@netapp.com \
    --cc=linux-nfs@vger.kernel.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).