From: David Miller <davem@davemloft.net>
To: dhowells@redhat.com
Cc: netdev@vger.kernel.org, linux-afs@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next 0/8] rxrpc: Overhaul call refcounting
Date: Wed, 07 Sep 2016 17:22:16 -0700 (PDT) [thread overview]
Message-ID: <20160907.172216.1425039504750660925.davem@davemloft.net> (raw)
In-Reply-To: <147326174610.26593.17043098689515647894.stgit@warthog.procyon.org.uk>
From: David Howells <dhowells@redhat.com>
Date: Wed, 07 Sep 2016 16:22:26 +0100
>
> Here's a set of mostly small patches leading up to one big one.
>
> The big patch at the end of the series overhauls how rxrpc_call refcounting
> is handled, making it more sane so that calls bound to user IDs are _only_
> released from socket operations or kernel API functions. Further, the
> patch stops calls from holding refs on their parent socket - which can
> prevent the socket from being cleaned up.
>
> The second largest patch improves the call tracking tracepoint by providing
> extra information about the situation in which gets and puts occur. This
> allows distinctions to be drawn between refs held by the socket user ID
> tree, refs held by the work queue (to be implemented by a future patch) and
> other refs.
>
> The other patches include a couple of cleanups and some simple alterations
> to avoid NULL pointer dereferences in the big patch.
>
> The patches can be found here also (non-terminally on the branch):
>
> http://git.kernel.org/cgit/linux/kernel/git/dhowells/linux-fs.git/log/?h=rxrpc-rewrite
>
> Tagged thusly:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/dhowells/linux-fs.git
> rxrpc-rewrite-20160907-1
Pulled.
prev parent reply other threads:[~2016-09-08 0:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-07 15:22 [PATCH net-next 0/8] rxrpc: Overhaul call refcounting David Howells
2016-09-07 15:22 ` [PATCH net-next 1/8] rxrpc: Whitespace cleanup David Howells
2016-09-07 15:22 ` [PATCH net-next 2/8] rxrpc: Delete unused rxrpc_kernel_free_skb() David Howells
2016-09-07 15:22 ` [PATCH net-next 3/8] rxrpc: Improve the call tracking tracepoint David Howells
2016-09-07 15:22 ` [PATCH net-next 4/8] rxrpc: Use call->peer rather than call->conn->params.peer David Howells
2016-09-07 15:23 ` [PATCH net-next 5/8] rxrpc: Cache the security index in the rxrpc_call struct David Howells
2016-09-07 15:23 ` [PATCH net-next 6/8] rxrpc: Pass the connection pointer to rxrpc_post_packet_to_call() David Howells
2016-09-07 15:23 ` [PATCH net-next 7/8] rxrpc: Use rxrpc_is_service_call() rather than rxrpc_conn_is_service() David Howells
2016-09-07 15:23 ` [PATCH net-next 8/8] rxrpc: Calls shouldn't hold socket refs David Howells
2016-09-08 0:22 ` David Miller [this message]
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=20160907.172216.1425039504750660925.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=dhowells@redhat.com \
--cc=linux-afs@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@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).