All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: Allison Henderson <achender@kernel.org>
Cc: netdev@vger.kernel.org, linux-rdma@vger.kernel.org,
	pabeni@redhat.com, edumazet@google.com, horms@kernel.org
Subject: Re: [PATCH net-next v9 00/13] net/rds: make connection lifetime reference-counted
Date: Fri, 16 Oct 2026 16:15:04 -0700	[thread overview]
Message-ID: <20261016161504.1085ed5d@kernel.org> (raw)
In-Reply-To: <d149a5b9f088994e5e98db7223b82040a302c0e9.camel@kernel.org>

On Fri, 16 Oct 2026 16:07:55 -0700 Allison Henderson wrote:
> On Fri, 2026-10-16 at 16:05 -0700, Jakub Kicinski wrote:
> > On Wed,  7 Oct 2026 20:13:20 -0700 Allison Henderson wrote:  
> > > This is v9 of the connection-lifetime set (v1 at [1], v2 at [2],
> > > v3 at [3], v4 at [6], v5 at [7], v6 at [8], v7 at [9], v8 at [10]),
> > > following
> > > "net/rds: own the fastpath locks across connection teardown"  
> > 
> > Patch 12 fails to apply now, sorry about the extra long processing
> > delay.  
> No worries, I've been tied up with a lot of extra work myself.  
> I'll come back and rebase tonight or tomorrow.  Thanks! 

I also dropped the small series for net.
Is the Medium severity concern there not worth worrying about?
If so - I'd apply that to net-next, LMK if you _really_ want
that in net.

  reply	other threads:[~2026-10-16 23:15 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-08  3:13 [PATCH net-next v9 00/13] net/rds: make connection lifetime reference-counted Allison Henderson
2026-10-08  3:13 ` [PATCH net-next v9 01/13] net/rds: ib: don't enable interrupts in rds_ib_conn_free() Allison Henderson
2026-10-08  3:32   ` sashiko-bot
2026-10-08  3:13 ` [PATCH net-next v9 02/13] net/rds: undo conn_alloc() the same way on every __rds_conn_create() exit Allison Henderson
2026-10-08  3:32   ` sashiko-bot
2026-10-08  3:13 ` [PATCH net-next v9 03/13] net/rds: ib: refuse to attach a connection to a device being removed Allison Henderson
2026-10-08  3:32   ` sashiko-bot
2026-10-12  4:17   ` netdev-bot+sashiko
2026-10-08  3:13 ` [PATCH net-next v9 04/13] net/rds: guard every work-requeueing site with rds_destroy_pending() Allison Henderson
2026-10-08  3:32   ` sashiko-bot
2026-10-08  3:13 ` [PATCH net-next v9 05/13] net/rds: make rds_destroy_pending() report a connection's own destroy Allison Henderson
2026-10-08  3:32   ` sashiko-bot
2026-10-08  3:13 ` [PATCH net-next v9 06/13] net/rds: split connection destroy into quiesce and kref-governed free Allison Henderson
2026-10-08  3:32   ` sashiko-bot
2026-10-08  3:13 ` [PATCH net-next v9 07/13] net/rds: unlink transport nodes before a possibly deferred connection free Allison Henderson
2026-10-08  3:32   ` sashiko-bot
2026-10-12  4:17   ` netdev-bot+sashiko
2026-10-08  3:13 ` [PATCH net-next v9 08/13] net/rds: wait for connections to be freed on transport unload Allison Henderson
2026-10-08  3:32   ` sashiko-bot
2026-10-08  3:13 ` [PATCH net-next v9 09/13] net/rds: hold a connection reference from struct rds_incoming Allison Henderson
2026-10-08  3:32   ` sashiko-bot
2026-10-12  4:17   ` netdev-bot+sashiko
2026-10-08  3:13 ` [PATCH net-next v9 10/13] net/rds: take cp_lock to purge cp_send_queue in the quiesce Allison Henderson
2026-10-08  3:32   ` sashiko-bot
2026-10-08  3:13 ` [PATCH net-next v9 11/13] net/rds: hold connection references in lookup, sockets and c_passive Allison Henderson
2026-10-08  3:32   ` sashiko-bot
2026-10-12  4:17   ` netdev-bot+sashiko
2026-10-08  3:13 ` [PATCH net-next v9 12/13] net/rds: pin the connection across RDMA-CM event handling Allison Henderson
2026-10-08  3:32   ` sashiko-bot
2026-10-08  3:13 ` [PATCH net-next v9 13/13] net/rds: drop rds_conn_count in favor of t_conn_count Allison Henderson
2026-10-08  3:32   ` sashiko-bot
2026-10-16 23:05 ` [PATCH net-next v9 00/13] net/rds: make connection lifetime reference-counted Jakub Kicinski
2026-10-16 23:07   ` Allison Henderson
2026-10-16 23:15     ` Jakub Kicinski [this message]
2026-10-17  0:25       ` Allison Henderson

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=20261016161504.1085ed5d@kernel.org \
    --to=kuba@kernel.org \
    --cc=achender@kernel.org \
    --cc=edumazet@google.com \
    --cc=horms@kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.