From: Jaegeuk Kim <jaegeuk@kernel.org>
To: linux-kernel@vger.kernel.org, linux-f2fs-devel@lists.sourceforge.net
Cc: Jaegeuk Kim <jaegeuk@kernel.org>
Subject: [f2fs-dev] [PATCH 4/4] f2fs: free sysfs kobject
Date: Wed, 18 Dec 2019 12:09:47 -0800 [thread overview]
Message-ID: <20191218200947.20445-4-jaegeuk@kernel.org> (raw)
In-Reply-To: <20191218200947.20445-1-jaegeuk@kernel.org>
Detected kmemleak.
Signed-off-by: Jaegeuk Kim <jaegeuk@kernel.org>
---
fs/f2fs/sysfs.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/fs/f2fs/sysfs.c b/fs/f2fs/sysfs.c
index 70945ceb9c0c..5963316f391a 100644
--- a/fs/f2fs/sysfs.c
+++ b/fs/f2fs/sysfs.c
@@ -786,4 +786,5 @@ void f2fs_unregister_sysfs(struct f2fs_sb_info *sbi)
remove_proc_entry(sbi->sb->s_id, f2fs_proc_root);
}
kobject_del(&sbi->s_kobj);
+ kobject_put(&sbi->s_kobj);
}
--
2.24.0.525.g8f36a354ae-goog
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
next prev parent reply other threads:[~2019-12-18 20:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-18 20:09 [f2fs-dev] [PATCH 1/4] f2fs: convert inline_dir early before starting rename Jaegeuk Kim
2019-12-18 20:09 ` [f2fs-dev] [PATCH 2/4] f2fs: don't put new_page twice in f2fs_rename Jaegeuk Kim
2019-12-28 6:50 ` Chao Yu
2019-12-18 20:09 ` [f2fs-dev] [PATCH 3/4] f2fs: declare nested quota_sem and remove unnecessary sems Jaegeuk Kim
2019-12-18 20:09 ` Jaegeuk Kim [this message]
2019-12-28 10:09 ` [f2fs-dev] [PATCH 4/4] f2fs: free sysfs kobject Chao Yu
2019-12-28 6:32 ` [f2fs-dev] [PATCH 1/4] f2fs: convert inline_dir early before starting rename Chao Yu
2019-12-31 0:06 ` Jaegeuk Kim
2019-12-31 1:22 ` Chao Yu
2020-01-02 18:36 ` [f2fs-dev] [PATCH 1/4 v2] " Jaegeuk Kim
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=20191218200947.20445-4-jaegeuk@kernel.org \
--to=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@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;
as well as URLs for NNTP newsgroup(s).