From: Jens Axboe <axboe@kernel.dk>
To: Davidlohr Bueso <dave@stgolabs.net>
Cc: linux-kernel@vger.kernel.org, Davidlohr Bueso <dbueso@suse.de>,
oleg@redhat.com, linux-block@vger.kernel.org
Subject: Re: [PATCH] block: fix ioprio_get(IOPRIO_WHO_PGRP) vs setuid(2)
Date: Fri, 10 Dec 2021 11:26:14 -0700 [thread overview]
Message-ID: <163916077449.627295.16747606305851596098.b4-ty@kernel.dk> (raw)
In-Reply-To: <20211210182058.43417-1-dave@stgolabs.net>
On Fri, 10 Dec 2021 10:20:58 -0800, Davidlohr Bueso wrote:
> do_each_pid_thread(PIDTYPE_PGID) can race with a concurrent
> change_pid(PIDTYPE_PGID) that can move the task from one hlist
> to another while iterating. Serialize ioprio_get to take
> the tasklist_lock in this case, just like it's set counterpart.
>
>
Applied, thanks!
[1/1] block: fix ioprio_get(IOPRIO_WHO_PGRP) vs setuid(2)
commit: e6a59aac8a8713f335a37d762db0dbe80e7f6d38
Best regards,
--
Jens Axboe
prev parent reply other threads:[~2021-12-10 18:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-10 18:20 [PATCH] block: fix ioprio_get(IOPRIO_WHO_PGRP) vs setuid(2) Davidlohr Bueso
2021-12-10 18:26 ` Jens Axboe [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=163916077449.627295.16747606305851596098.b4-ty@kernel.dk \
--to=axboe@kernel.dk \
--cc=dave@stgolabs.net \
--cc=dbueso@suse.de \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=oleg@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