From: Christoph Hellwig <hch@lst.de>
To: Chung-Chiang Cheng <shepjeng@gmail.com>
Cc: Christoph Hellwig <hch@lst.de>,
jlbec@evilplan.org,
Pantelis Antoniou <pantelis.antoniou@konsulko.com>,
linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
Chung-Chiang Cheng <cccheng@synology.com>
Subject: Re: [PATCH] configfs: fix memleak in configfs_release_bin_file
Date: Tue, 22 Jun 2021 10:04:32 +0200 [thread overview]
Message-ID: <20210622080432.GA2232@lst.de> (raw)
In-Reply-To: <CAHuHWt=2ZoQJz1tVpJ7SzqUDwPXthNHksq2-uTFCzHmv+E7qWA@mail.gmail.com>
Thanks. I'v split this into one to move the vfree attribute to you
and a cleanup on top and applied the result to the configfs tree:
http://git.infradead.org/users/hch/configfs.git/shortlog/refs/heads/for-next
prev parent reply other threads:[~2021-06-22 8:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-18 7:59 [PATCH] configfs: fix memleak in configfs_release_bin_file Chung-Chiang Cheng
2021-06-22 6:04 ` Christoph Hellwig
2021-06-22 7:40 ` Chung-Chiang Cheng
2021-06-22 8:04 ` Christoph Hellwig [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=20210622080432.GA2232@lst.de \
--to=hch@lst.de \
--cc=cccheng@synology.com \
--cc=jlbec@evilplan.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pantelis.antoniou@konsulko.com \
--cc=shepjeng@gmail.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).