cluster-devel.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Guillaume Nault <gnault@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [PATCH v1 2/3] Treewide: Stop corrupting socket's task_frag
Date: Wed, 30 Nov 2022 12:48:35 +0100	[thread overview]
Message-ID: <20221130114835.GA29316@pc-4.home> (raw)
In-Reply-To: <20221129140242.GA15747@lst.de>

On Tue, Nov 29, 2022 at 03:02:42PM +0100, Christoph Hellwig wrote:
> Hmm.  Having to set a flag to not accidentally corrupt per-task
> state seems a bit fragile.  Wouldn't it make sense to find a way to opt
> into the feature only for sockets created from the syscall layer?

That's something I originally considered. But, as far as I can see, nbd
needs this flag _and_ uses sockets created in user space. So it'd still
need to opt out manually.


  parent reply	other threads:[~2022-11-30 11:48 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <cover.1669036433.git.bcodding@redhat.com>
2022-11-21 13:35 ` [Cluster-devel] [PATCH v1 2/3] Treewide: Stop corrupting socket's task_frag Benjamin Coddington
2022-11-29 14:02   ` Christoph Hellwig
2022-11-29 16:47     ` Benjamin Coddington
2022-11-30 12:07       ` Guillaume Nault
2022-11-29 17:42     ` Jeff Layton
2022-11-30 11:48     ` Guillaume Nault [this message]
2022-12-09 12:37   ` Paolo Abeni
2022-12-09 16:11     ` Jakub Kicinski
2022-12-09 16:50       ` Paolo Abeni
2022-11-21 13:56 ` David Howells
2022-11-21 14:34   ` Benjamin Coddington
2022-11-21 21:40     ` Shuah Khan
2022-11-21 21:43       ` Shuah Khan
2022-11-21 22:01         ` Benjamin Coddington
2022-11-21 22:32           ` Shuah Khan
2022-11-22 14:23             ` Benjamin Coddington

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=20221130114835.GA29316@pc-4.home \
    --to=gnault@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 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).