From: syzbot <syzbot+3a0f6c96e37e347c6ba9@syzkaller.appspotmail.com>
To: sudumbha@cisco.com
Cc: sudumbha@cisco.com, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [Linux Kernel Bug] memory leak in ubi_attach
Date: Fri, 15 Nov 2024 06:11:13 -0800 [thread overview]
Message-ID: <67375681.050a0220.2a2fcc.007d.GAE@google.com> (raw)
In-Reply-To: <PH0PR11MB7496D8FBFAC72061A9C5F07CD1242@PH0PR11MB7496.namprd11.prod.outlook.com>
> #syz test: git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git<http://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git> 8cf0b93919e13d1e8d4466eb4080a4c4d9d66d7b
This crash does not have a reproducer. I cannot test it.
>
> ----------------------------------------------------------------------------------
> diff --git a/mm/slub.c b/mm/slub.c
> index 5b832512044e..dc77128358d8 100644
> --- a/mm/slub.c
> +++ b/mm/slub.c
> @@ -7098,8 +7098,11 @@ static int sysfs_slab_add(struct kmem_cache *s)
>
> s->kobj.kset = kset;
> err = kobject_init_and_add(&s->kobj, &slab_ktype, NULL, "%s", name);
> - if (err)
> + if (err) {
> + kfree_const(s->kobj.name);
> + s->kobj.name = NULL;
> goto out;
> + }
>
> err = sysfs_create_group(&s->kobj, &slab_attr_group);
> if (err)
> --
> 2.42.0
>
> ----------------------------------------------------------------------------------
>
> Thanks & regards,
> Sudhir
>
next parent reply other threads:[~2024-11-15 14:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <PH0PR11MB7496D8FBFAC72061A9C5F07CD1242@PH0PR11MB7496.namprd11.prod.outlook.com>
2024-11-15 14:11 ` syzbot [this message]
2024-01-23 3:53 [Linux Kernel Bug] memory leak in ubi_attach Chenyuan Yang
2024-01-23 4:55 ` Zhihao Cheng
[not found] ` <CALGdzuryBbCqGAhox9ZWaQHD5dSQNApfGmCP+rYZ7O4MCRH+rw@mail.gmail.com>
2024-01-24 12:44 ` Zhihao Cheng
2024-01-24 14:41 ` Chenyuan Yang
2024-01-29 11:51 ` Zhihao Cheng
2024-10-11 1:23 ` Chenyuan Yang
2024-10-11 5:35 ` Greg KH
2024-10-15 3:41 ` Ryder Wang
2024-10-15 6:54 ` gregkh
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=67375681.050a0220.2a2fcc.007d.GAE@google.com \
--to=syzbot+3a0f6c96e37e347c6ba9@syzkaller.appspotmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sudumbha@cisco.com \
--cc=syzkaller-bugs@googlegroups.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