From: Dongliang Mu <dzm91@hust.edu.cn> To: Gao Xiang <xiang@kernel.org>, Chao Yu <chao@kernel.org> Cc: Dongliang Mu <mudongliangabcd@gmail.com>, linux-erofs@lists.ozlabs.org, linux-kernel@vger.kernel.org Subject: [PATCH] fs: erofs: add sanity check for kobject in erofs_unregister_sysfs Date: Tue, 15 Mar 2022 21:28:14 +0800 [thread overview] Message-ID: <20220315132814.12332-1-dzm91@hust.edu.cn> (raw) From: Dongliang Mu <mudongliangabcd@gmail.com> Syzkaller hit 'WARNING: kobject bug in erofs_unregister_sysfs'. This bug is triggered by injecting fault in kobject_init_and_add of erofs_unregister_sysfs. Fix this by adding sanity check for kobject in erofs_unregister_sysfs Note that I've tested the patch and the crash does not occur any more. Signed-off-by: Dongliang Mu <mudongliangabcd@gmail.com> --- fs/erofs/sysfs.c | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/fs/erofs/sysfs.c b/fs/erofs/sysfs.c index dac252bc9228..f3babf1e6608 100644 --- a/fs/erofs/sysfs.c +++ b/fs/erofs/sysfs.c @@ -221,9 +221,11 @@ void erofs_unregister_sysfs(struct super_block *sb) { struct erofs_sb_info *sbi = EROFS_SB(sb); - kobject_del(&sbi->s_kobj); - kobject_put(&sbi->s_kobj); - wait_for_completion(&sbi->s_kobj_unregister); + if (sbi->s_kobj.state_in_sysfs) { + kobject_del(&sbi->s_kobj); + kobject_put(&sbi->s_kobj); + wait_for_completion(&sbi->s_kobj_unregister); + } } int __init erofs_init_sysfs(void) -- 2.25.1
WARNING: multiple messages have this Message-ID (diff)
From: Dongliang Mu <dzm91@hust.edu.cn> To: Gao Xiang <xiang@kernel.org>, Chao Yu <chao@kernel.org> Cc: linux-erofs@lists.ozlabs.org, Dongliang Mu <mudongliangabcd@gmail.com>, linux-kernel@vger.kernel.org Subject: [PATCH] fs: erofs: add sanity check for kobject in erofs_unregister_sysfs Date: Tue, 15 Mar 2022 21:28:14 +0800 [thread overview] Message-ID: <20220315132814.12332-1-dzm91@hust.edu.cn> (raw) From: Dongliang Mu <mudongliangabcd@gmail.com> Syzkaller hit 'WARNING: kobject bug in erofs_unregister_sysfs'. This bug is triggered by injecting fault in kobject_init_and_add of erofs_unregister_sysfs. Fix this by adding sanity check for kobject in erofs_unregister_sysfs Note that I've tested the patch and the crash does not occur any more. Signed-off-by: Dongliang Mu <mudongliangabcd@gmail.com> --- fs/erofs/sysfs.c | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/fs/erofs/sysfs.c b/fs/erofs/sysfs.c index dac252bc9228..f3babf1e6608 100644 --- a/fs/erofs/sysfs.c +++ b/fs/erofs/sysfs.c @@ -221,9 +221,11 @@ void erofs_unregister_sysfs(struct super_block *sb) { struct erofs_sb_info *sbi = EROFS_SB(sb); - kobject_del(&sbi->s_kobj); - kobject_put(&sbi->s_kobj); - wait_for_completion(&sbi->s_kobj_unregister); + if (sbi->s_kobj.state_in_sysfs) { + kobject_del(&sbi->s_kobj); + kobject_put(&sbi->s_kobj); + wait_for_completion(&sbi->s_kobj_unregister); + } } int __init erofs_init_sysfs(void) -- 2.25.1
next reply other threads:[~2022-03-15 13:28 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-03-15 13:28 Dongliang Mu [this message] 2022-03-15 13:28 ` [PATCH] fs: erofs: add sanity check for kobject in erofs_unregister_sysfs Dongliang Mu 2022-03-15 13:34 ` Gao Xiang 2022-03-15 13:34 ` Gao Xiang 2022-03-16 1:45 ` Chao Yu 2022-03-16 1:45 ` Chao Yu
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=20220315132814.12332-1-dzm91@hust.edu.cn \ --to=dzm91@hust.edu.cn \ --cc=chao@kernel.org \ --cc=linux-erofs@lists.ozlabs.org \ --cc=linux-kernel@vger.kernel.org \ --cc=mudongliangabcd@gmail.com \ --cc=xiang@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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.