public inbox for cgroups@vger.kernel.org
 help / color / mirror / Atom feed
From: Tejun Heo <tj-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
To: Jan Kara <jack-AlSwsSmVLrQ@public.gmane.org>
Cc: "Michal Koutný" <mkoutny-IBi9RG/b67k@public.gmane.org>,
	"Paolo Valente"
	<paolo.valente-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>,
	linux-block-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	fvogdt-l3A5Bk7waGM@public.gmane.org,
	cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: Use after free with BFQ and cgroups
Date: Tue, 30 Nov 2021 06:22:13 -1000	[thread overview]
Message-ID: <YaZPtZcdMKwhzzy/@slm.duckdns.org> (raw)
In-Reply-To: <20211130115010.GF7174-4I4JzKEfoa/jFM9bn6wA6Q@public.gmane.org>

Hello,

On Tue, Nov 30, 2021 at 12:50:10PM +0100, Jan Kara wrote:
> The problem is bfq_queue associated with a task effectively holds a
> reference to the potentially dead cgroup and the reference can stay there
> until the task (that itself got reparented to the root cgroup) exits. So I
> think we need to reparent these bfq_queue structures as well to avoid
> holding cgroup in zombie state excessively long.

Ah, I see. Yeah, that's not great. Agree that it'd be better to reparent
(probably just punt to the root cgroup).

Thanks.

-- 
tejun

      parent reply	other threads:[~2021-11-30 16:22 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20211125172809.GC19572@quack2.suse.cz>
     [not found] ` <20211125172809.GC19572-4I4JzKEfoa/jFM9bn6wA6Q@public.gmane.org>
2021-11-26 14:47   ` Use after free with BFQ and cgroups Michal Koutný
     [not found]     ` <20211126144724.GA31093-9OudH3eul5jcvrawFnH+a6VXKuFTiq87@public.gmane.org>
2021-11-29 17:11       ` Jan Kara
2021-12-09  2:23         ` yukuai (C)
2021-12-13 17:33           ` Jan Kara
     [not found]             ` <20211213173354.GE14044-4I4JzKEfoa/jFM9bn6wA6Q@public.gmane.org>
2021-12-14  1:24               ` yukuai (C)
     [not found]                 ` <896161a3-922c-63b3-6e6f-9f6005a46bd4-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>
2021-12-20 18:38                   ` Jan Kara
     [not found]           ` <f03b2b1c-808a-c657-327d-03165b988e7d-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>
2021-12-09 15:33             ` Paolo Valente
2021-12-22 15:21             ` Jan Kara
     [not found]               ` <20211222152103.GF685-4I4JzKEfoa/jFM9bn6wA6Q@public.gmane.org>
2021-12-23  1:02                 ` yukuai (C)
     [not found]                   ` <d770663a-911c-c9c1-1185-558634f4c738-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>
2021-12-23 17:13                     ` Jan Kara
2021-11-29 17:12     ` Tejun Heo
2021-11-30 11:50       ` Jan Kara
     [not found]         ` <20211130115010.GF7174-4I4JzKEfoa/jFM9bn6wA6Q@public.gmane.org>
2021-11-30 16:22           ` Tejun Heo [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=YaZPtZcdMKwhzzy/@slm.duckdns.org \
    --to=tj-dgejt+ai2ygdnm+yrofe0a@public.gmane.org \
    --cc=cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=fvogdt-l3A5Bk7waGM@public.gmane.org \
    --cc=jack-AlSwsSmVLrQ@public.gmane.org \
    --cc=linux-block-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=mkoutny-IBi9RG/b67k@public.gmane.org \
    --cc=paolo.valente-QSEj5FYQhm4dnm+yROfE0A@public.gmane.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