public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Li Zefan <lizf@cn.fujitsu.com>
To: Zdenek Kabelac <zdenek.kabelac@gmail.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	mbroz@redhat.com, tytso@mit.edu, jens.axboe@oracle.com,
	mingo@elte.hu
Subject: Re: [PATCH] Add missing blk_trace_remove_sysfs to be in pair with blk_trace_init_sysfs
Date: Tue, 22 Sep 2009 14:09:07 +0800	[thread overview]
Message-ID: <4AB86A03.7060207@cn.fujitsu.com> (raw)
In-Reply-To: <c4e36d110909210307m6579807ehe4d659053c4dc696@mail.gmail.com>

Zdenek Kabelac wrote:
> Subject: [PATCH] Add missing blk_trace_remove_sysfs to be in pair with
> blk_trace_init_sysfs
> From: Zdenek Kabelac <zkabelac@redhat.com>
> 
> Adds missing blk_trace_remove_sysfs() to be in pair with
> blk_trace_init_sysfs() introduced in commit
> 1d54ad6da9192fed5dd3b60224d9f2dfea0dcd82.
> 
> Problem was noticed via kmemleak backtrace when some sysfs entries
> were note properly destroyed during  device removal:
> 

Thanks for reporting and fixing this!

> @@ -465,6 +466,7 @@ void blk_unregister_queue(struct gendisk *disk)
> 
>  		kobject_uevent(&q->kobj, KOBJ_REMOVE);
>  		kobject_del(&q->kobj);
> +		blk_trace_remove_sysfs(disk_to_dev(disk));

This should be moved outside of 'if'.

>  		kobject_put(&disk_to_dev(disk)->kobj);
>  	}
>  }

  reply	other threads:[~2009-09-22  6:10 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-21 10:07 [PATCH] Add missing blk_trace_remove_sysfs to be in pair with blk_trace_init_sysfs Zdenek Kabelac
2009-09-22  6:09 ` Li Zefan [this message]
2009-09-22  7:57   ` Zdenek Kabelac
2009-09-24  1:07     ` Li Zefan
2009-09-24 10:26       ` Zdenek Kabelac
2009-09-25  0:59         ` Li Zefan
2009-09-25  4:16         ` Jens Axboe

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=4AB86A03.7060207@cn.fujitsu.com \
    --to=lizf@cn.fujitsu.com \
    --cc=jens.axboe@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mbroz@redhat.com \
    --cc=mingo@elte.hu \
    --cc=tytso@mit.edu \
    --cc=zdenek.kabelac@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