From: Dan Carpenter <dan.carpenter@oracle.com>
To: Oleg Drokin <green@linuxhacker.ru>
Cc: smatch@vger.kernel.org
Subject: Re: alloc_page leaks tracing
Date: Fri, 25 Mar 2022 09:48:41 +0300 [thread overview]
Message-ID: <20220325064841.GH12805@kadam> (raw)
In-Reply-To: <20220322080513.GS336@kadam>
Another option to free the page is put_page() right?
To me it looks like r5l_recovery_verify_data_checksum_for_mb() should
use free_page() but put_page() also works I think. My understanding is
that you could swap all the free_page() calls for put_page() but not the
other way round.
regards,
dan carpenter
prev parent reply other threads:[~2022-03-25 6:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-08 17:28 alloc_page leaks tracing Oleg Drokin
2022-03-10 9:42 ` Dan Carpenter
[not found] ` <82B7079C-AD17-4E5E-A245-71E9ED53E5A3@linuxhacker.ru>
2022-03-11 21:12 ` Dan Carpenter
2022-03-22 8:05 ` Dan Carpenter
2022-03-25 6:48 ` Dan Carpenter [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=20220325064841.GH12805@kadam \
--to=dan.carpenter@oracle.com \
--cc=green@linuxhacker.ru \
--cc=smatch@vger.kernel.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