From: Gao Xiang <hsiangkao@linux.alibaba.com>
To: Huang Jianan <jnhuang95@gmail.com>
Cc: Dongliang Mu <dzm91@hust.edu.cn>, Gao Xiang <xiang@kernel.org>,
Chao Yu <chao@kernel.org>, syzkaller <syzkaller@googlegroups.com>,
linux-erofs@lists.ozlabs.org,
Dongliang Mu <mudongliangabcd@gmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] fs: erofs: remember if kobject_init_and_add was done
Date: Tue, 15 Mar 2022 18:55:50 +0800 [thread overview]
Message-ID: <YjBwtqsEOZ5JbqvS@B-P7TQMD6M-0146.local> (raw)
In-Reply-To: <bca8f865-bc3e-44d7-7298-c2c7e8973580@gmail.com>
On Tue, Mar 15, 2022 at 06:43:01PM +0800, Huang Jianan wrote:
> 在 2022/3/15 15:51, Dongliang Mu 写道:
> > 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 remembering if kobject_init_and_add is successful.
> >
> > Note that I've tested the patch and the crash does not occur any more.
> >
> > Reported-by: syzkaller <syzkaller@googlegroups.com>
> > Signed-off-by: Dongliang Mu <mudongliangabcd@gmail.com>
> > ---
> > fs/erofs/internal.h | 1 +
> > fs/erofs/sysfs.c | 9 ++++++---
> > 2 files changed, 7 insertions(+), 3 deletions(-)
> >
> > diff --git a/fs/erofs/internal.h b/fs/erofs/internal.h
> > index 5aa2cf2c2f80..9e20665e3f68 100644
> > --- a/fs/erofs/internal.h
> > +++ b/fs/erofs/internal.h
> > @@ -144,6 +144,7 @@ struct erofs_sb_info {
> > u32 feature_incompat;
> > /* sysfs support */
> > + bool s_sysfs_inited;
>
> Hi Dongliang,
>
> How about using sbi->s_kobj.state_in_sysfs to avoid adding a extra member in
> sbi ?
Ok, I have no tendency of these (I'm fine with either ways).
I've seen some usage like:
static inline int device_is_registered(struct device *dev)
{
return dev->kobj.state_in_sysfs;
}
But I'm still not sure if we need to rely on such internal
interface.. More thoughts?
Thanks,
Gao Xiang
>
> Thanks,
> Jianan
>
> > struct kobject s_kobj; /* /sys/fs/erofs/<devname> */
> > struct completion s_kobj_unregister;
> > };
> > diff --git a/fs/erofs/sysfs.c b/fs/erofs/sysfs.c
> > index dac252bc9228..2b48a4df19b4 100644
> > --- a/fs/erofs/sysfs.c
> > +++ b/fs/erofs/sysfs.c
> > @@ -209,6 +209,7 @@ int erofs_register_sysfs(struct super_block *sb)
> > "%s", sb->s_id);
> > if (err)
> > goto put_sb_kobj;
> > + sbi->s_sysfs_inited = true;
> > return 0;
> > put_sb_kobj:
> > @@ -221,9 +222,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_sysfs_inited) {
> > + kobject_del(&sbi->s_kobj);
> > + kobject_put(&sbi->s_kobj);
> > + wait_for_completion(&sbi->s_kobj_unregister);
> > + }
> > }
> > int __init erofs_init_sysfs(void)
next prev parent reply other threads:[~2022-03-15 10:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-15 7:51 [PATCH] fs: erofs: remember if kobject_init_and_add was done Dongliang Mu
2022-03-15 8:33 ` Gao Xiang
2022-03-15 10:43 ` Huang Jianan
2022-03-15 10:55 ` Gao Xiang [this message]
2022-03-15 11:05 ` Huang Jianan
2022-03-15 11:59 ` Dongliang Mu
2022-03-15 12:25 ` Gao Xiang
2022-03-15 12:44 ` Dongliang Mu
2022-03-15 13:30 ` Dongliang Mu
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=YjBwtqsEOZ5JbqvS@B-P7TQMD6M-0146.local \
--to=hsiangkao@linux.alibaba.com \
--cc=chao@kernel.org \
--cc=dzm91@hust.edu.cn \
--cc=jnhuang95@gmail.com \
--cc=linux-erofs@lists.ozlabs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mudongliangabcd@gmail.com \
--cc=syzkaller@googlegroups.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: 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).