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,
	jhubbard@nvidia.com, leon@kernel.org
Subject: Re: [PATCH net-next 0/3] net/rds: Bug fix ports
Date: Mon, 27 Jul 2026 15:49:52 -0700	[thread overview]
Message-ID: <20260727154952.0bc24e1a@kernel.org> (raw)
In-Reply-To: <e770554d9ca05784abb3c9d1ccd378295f46fa08.camel@kernel.org>

On Sat, 25 Jul 2026 09:25:21 -0700 Allison Henderson wrote:
> Apologies, this should have been a v2.  Let me know if folks want the
> resend for the book keeping or would rather forgo the spam.

All good, Sashiko has a comment -- 
https://sashiko.dev/#/patchset/20260725082939.2546624-3-achender@kernel.org

I'm guessing that nothing can get queued at the point where we call
flush? Since it's late in the exit path?

  reply	other threads:[~2026-07-27 22:49 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-25  8:29 [PATCH net-next 0/3] net/rds: Bug fix ports Allison Henderson
2026-07-25  8:29 ` [PATCH net-next 1/3] net/rds: don't use unpin_user_pages_dirty_lock() from atomic context Allison Henderson
2026-07-25  8:29 ` [PATCH net-next 2/3] net/rds: hold the socket while an rds_mr references it Allison Henderson
2026-07-25  8:29 ` [PATCH net-next 3/3] net/rds: fix rds_message leak in the rds_send_xmit() drop path Allison Henderson
2026-07-25 16:25 ` [PATCH net-next 0/3] net/rds: Bug fix ports Allison Henderson
2026-07-27 22:49   ` Jakub Kicinski [this message]
2026-07-27 23:34     ` 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=20260727154952.0bc24e1a@kernel.org \
    --to=kuba@kernel.org \
    --cc=achender@kernel.org \
    --cc=edumazet@google.com \
    --cc=horms@kernel.org \
    --cc=jhubbard@nvidia.com \
    --cc=leon@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.