From: Jan Kara <jack@suse.cz>
To: Zumeng Chen <zumeng.chen@gmail.com>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org, axboe@fb.com,
jack@suse.cz, tj@kernel.org, geliangtang@gmail.com
Subject: Re: [PATCH ] mm/backing-dev.c: remove a null kfree and fix a false kmemleak in backing-dev
Date: Wed, 27 Sep 2017 11:40:49 +0200 [thread overview]
Message-ID: <20170927094049.GC25746@quack2.suse.cz> (raw)
In-Reply-To: <1506496508-31715-1-git-send-email-zumeng.chen@gmail.com>
On Wed 27-09-17 15:15:08, Zumeng Chen wrote:
> It seems kfree(new_congested) does nothing since new_congested has already
> been set null pointer before kfree, so remove it.
>
> Meanwhile kmemleak reports the following memory leakage:
>
> unreferenced object 0xcadbb440 (size 64):
> comm "kworker/0:4", pid 1399, jiffies 4294946504 (age 808.290s)
> hex dump (first 32 bytes):
> 00 00 00 00 01 00 00 00 00 00 00 00 01 00 00 00 ................
> 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
> backtrace:
> [<c028fb64>] kmem_cache_alloc_trace+0x2c4/0x3cc
> [<c025fe70>] wb_congested_get_create+0x9c/0x140
> [<c0260100>] wb_init+0x184/0x1f4
> [<c02601fc>] bdi_init+0x8c/0xd4
> [<c051f75c>] blk_alloc_queue_node+0x9c/0x2d8
> [<c05227e8>] blk_init_queue_node+0x2c/0x64
> [<c052283c>] blk_init_queue+0x1c/0x20
> [<c06c7b30>] __scsi_alloc_queue+0x28/0x44
> [<c06caf4c>] scsi_alloc_queue+0x24/0x80
> [<c06cc0b8>] scsi_alloc_sdev+0x21c/0x34c
> [<c06ccc00>] scsi_probe_and_add_lun+0x878/0xb04
> [<c06cd114>] __scsi_scan_target+0x288/0x59c
> [<c06cd4b0>] scsi_scan_channel+0x88/0x9c
> [<c06cd9b8>] scsi_scan_host_selected+0x118/0x130
> [<c06cda70>] do_scsi_scan_host+0xa0/0xa4
> [<c06cdbe4>] scsi_scan_host+0x170/0x1b4
>
> wb_congested allocates memory for congested when wb_congested_get_create,
> and release it when exit or failure by wb_congested_put.
>
The patch is just wrong. Think what will happen if we decide to allocate
new_congested but then loose a race with somebody creating the same congested
structure (so we find it in the rb-tree).
Honza
> Signed-off-by: Zumeng Chen <zumeng.chen@gmail.com>
> ---
> mm/backing-dev.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/mm/backing-dev.c b/mm/backing-dev.c
> index e19606b..d816b2a 100644
> --- a/mm/backing-dev.c
> +++ b/mm/backing-dev.c
> @@ -457,6 +457,7 @@ wb_congested_get_create(struct backing_dev_info *bdi, int blkcg_id, gfp_t gfp)
>
> /* allocate storage for new one and retry */
> new_congested = kzalloc(sizeof(*new_congested), gfp);
> + kmemleak_ignore(new_congested);
> if (!new_congested)
> return NULL;
>
> @@ -468,7 +469,6 @@ wb_congested_get_create(struct backing_dev_info *bdi, int blkcg_id, gfp_t gfp)
> found:
> atomic_inc(&congested->refcnt);
> spin_unlock_irqrestore(&cgwb_lock, flags);
> - kfree(new_congested);
> return congested;
> }
>
> --
> 2.7.4
>
--
Jan Kara <jack@suse.com>
SUSE Labs, CR
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2017-09-27 9:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-27 7:15 Zumeng Chen
2017-09-27 9:40 ` Jan Kara [this message]
2017-09-27 13:35 ` Zumeng Chen
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=20170927094049.GC25746@quack2.suse.cz \
--to=jack@suse.cz \
--cc=axboe@fb.com \
--cc=geliangtang@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=tj@kernel.org \
--cc=zumeng.chen@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