public inbox for io-uring@vger.kernel.org
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Jens Axboe <axboe@kernel.dk>, Peter Zijlstra <peterz@infradead.org>
Cc: "Jann Horn" <jannh@google.com>, "Ingo Molnar" <mingo@redhat.com>,
	"Darren Hart" <dvhart@infradead.org>,
	"Davidlohr Bueso" <dave@stgolabs.net>,
	"André Almeida" <andrealmeid@igalia.com>,
	"kernel list" <linux-kernel@vger.kernel.org>,
	"Pavel Begunkov" <asml.silence@gmail.com>,
	io-uring <io-uring@vger.kernel.org>
Subject: Re: futex+io_uring: futex_q::task can maybe be dangling (but is not actually accessed, so it's fine)
Date: Wed, 15 Jan 2025 18:05:32 +0100	[thread overview]
Message-ID: <87msfsatyb.ffs@tglx> (raw)
In-Reply-To: <5603e468-9891-46a3-9ef7-13830cc975e5@kernel.dk>

On Wed, Jan 15 2025 at 08:32, Jens Axboe wrote:
> Here's the raw patch. Should've done this initially rather than just
> tackle __futex_queue(), for some reason I thought/assumed that
> futex_queue() was more widely used.

'git grep' is pretty useful to validate such assumptions :)

> What do you think?

Looks about right.

Thanks,

        tglx

  reply	other threads:[~2025-01-15 17:05 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-10 22:26 futex+io_uring: futex_q::task can maybe be dangling (but is not actually accessed, so it's fine) Jann Horn
2025-01-11  3:33 ` Jens Axboe
2025-01-13 13:53   ` Jann Horn
2025-01-13 14:38   ` Peter Zijlstra
2025-01-13 14:41     ` Jens Axboe
2025-01-15 10:20     ` Thomas Gleixner
2025-01-15 15:23       ` Jens Axboe
2025-01-15 15:32         ` Jens Axboe
2025-01-15 17:05           ` Thomas Gleixner [this message]
2025-01-15 17:07             ` Jens Axboe

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=87msfsatyb.ffs@tglx \
    --to=tglx@linutronix.de \
    --cc=andrealmeid@igalia.com \
    --cc=asml.silence@gmail.com \
    --cc=axboe@kernel.dk \
    --cc=dave@stgolabs.net \
    --cc=dvhart@infradead.org \
    --cc=io-uring@vger.kernel.org \
    --cc=jannh@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.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