From: Gabriel Krisman Bertazi <krisman-ZGY8ohtN/8qB+jHODAdFcQ@public.gmane.org>
To: tj-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org
Cc: axboe-tSWWG44O7X1aa/9Udqfwiw@public.gmane.org,
cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
khazhy-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org,
kernel-ZGY8ohtN/8qB+jHODAdFcQ@public.gmane.org
Subject: Re: [PATCH v2 1/2] blk-cgroup: Fix memleak on error path
Date: Thu, 22 Oct 2020 16:59:39 -0400 [thread overview]
Message-ID: <87k0vi0yf8.fsf@collabora.com> (raw)
In-Reply-To: <20201022205758.1739430-1-krisman-ZGY8ohtN/8qB+jHODAdFcQ@public.gmane.org> (Gabriel Krisman Bertazi's message of "Thu, 22 Oct 2020 16:57:57 -0400")
Gabriel Krisman Bertazi <krisman-ZGY8ohtN/8qB+jHODAdFcQ@public.gmane.org> writes:
> If new_blkg allocation raced with blk_policy change and
> blkg_lookup_check fails, new_blkg is leaked.
hm, sorry for the duplicate, the first attempt my script tripped on the
cover letter for some reason. Please disregard this one.
--
Gabriel Krisman Bertazi
next prev parent reply other threads:[~2020-10-22 20:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-22 20:57 [PATCH v2 1/2] blk-cgroup: Fix memleak on error path Gabriel Krisman Bertazi
[not found] ` <20201022205758.1739430-1-krisman-ZGY8ohtN/8qB+jHODAdFcQ@public.gmane.org>
2020-10-22 20:57 ` [PATCH v2 2/2] blk-cgroup: Pre-allocate tree node on blkg_conf_prep Gabriel Krisman Bertazi
2020-10-22 20:59 ` Gabriel Krisman Bertazi [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-10-22 20:58 [PATCH v2 0/2] Fixes to blkg_conf_prep Gabriel Krisman Bertazi
[not found] ` <20201022205842.1739739-1-krisman-ZGY8ohtN/8qB+jHODAdFcQ@public.gmane.org>
2020-10-22 20:58 ` [PATCH v2 1/2] blk-cgroup: Fix memleak on error path Gabriel Krisman Bertazi
[not found] ` <20201022205842.1739739-2-krisman-ZGY8ohtN/8qB+jHODAdFcQ@public.gmane.org>
2020-10-26 13:54 ` Tejun Heo
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=87k0vi0yf8.fsf@collabora.com \
--to=krisman-zgy8ohtn/8qb+jhodadfcq@public.gmane.org \
--cc=axboe-tSWWG44O7X1aa/9Udqfwiw@public.gmane.org \
--cc=cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=kernel-ZGY8ohtN/8qB+jHODAdFcQ@public.gmane.org \
--cc=khazhy-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org \
--cc=tj-DgEjT+Ai2ygdnm+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 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.