From: Pavel Skripkin <paskripkin@gmail.com>
To: "Theodore Ts'o" <tytso@mit.edu>
Cc: Vegard Nossum <vegard.nossum@oracle.com>,
akpm@linux-foundation.org, peterz@infradead.org, axboe@kernel.dk,
pmladek@suse.com, adilger.kernel@dilger.ca,
linux-ext4@vger.kernel.org, linux-kernel@vger.kernel.org,
syzbot+d9e482e303930fa4f6ff@syzkaller.appspotmail.com
Subject: Re: [PATCH] ext4: fix memory leak in ext4_fill_super
Date: Fri, 30 Apr 2021 01:05:47 +0300 [thread overview]
Message-ID: <20210430010547.38f27e39@gmail.com> (raw)
In-Reply-To: <YIsn+JToAkPqDPq5@mit.edu>
On Thu, 29 Apr 2021 17:41:12 -0400
"Theodore Ts'o" <tytso@mit.edu> wrote:
> On Thu, Apr 29, 2021 at 11:09:56PM +0300, Pavel Skripkin wrote:
> > > we will exit with -ENOMEM. So at the very least all callers of
> > > kthread_stop() also need to check for -ENOMEM as well as -EINTR
> > > --- or, be somehow sure that the thread function was successfully
> > > called and started. In this particular case, the ext4 mount code
> > > had just started the kmmpd thread, and then detected that
> > > something else had gone wrong, and failed the mount before the
> > > kmmpd thread ever had a chance to run.
> >
> > There is a small problem about -ENOMEM...
>
> What I'd suggest is that we simply move
>
> > exit_thread:
> > EXT4_SB(sb)->s_mmp_tsk = NULL;
> > kfree(data);
> > brelse(bh);
> > return retval;
> > }
>
> out of the thread function. That means hanging struct mmpd_data off
> the struct ext4_sb_info structure, and then adding a function like
> this to fs/ext4/mmp.c
>
> static void ext4_stop_mmpd(struct ext4_sb_info *sbi)
> {
> if (sbi->s_mmp_tsk) {
> kthread_stop(sbi->s_mmp_tsk);
> brelse(sbi->s_mmp_data->bh);
> kfree(sbi->s_mmp_data);
> sbi->s_mmp_data = NULL;
> sbi->s_mmp_tsk = NULL;
> }
> }
>
> Basically, just move all of the cleanup so it is done after the
> kthread is stopped, so we don't have to do any fancy error checking.
> We just do it unconditionally.
This sound much better than my idea. Will do it in v2.
Thanks!
>
> - Ted
>
> P.S. Actually, we could drop the struct mmpd_data altogether, and
> just hang the buffer head as sbi->s_mmp_bh. Then we can just pass the
> struct super * as the private pointer to kmmpd().
>
With regards,
Pavel Skripkin
next prev parent reply other threads:[~2021-04-29 22:05 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-28 17:28 [PATCH] ext4: fix memory leak in ext4_fill_super Pavel Skripkin
2021-04-29 10:01 ` Vegard Nossum
2021-04-29 11:08 ` Pavel Skripkin
2021-04-29 11:33 ` Pavel Skripkin
2021-04-29 17:05 ` Theodore Ts'o
2021-04-29 19:20 ` Pavel Skripkin
2021-04-29 20:09 ` Pavel Skripkin
2021-04-29 21:41 ` Theodore Ts'o
2021-04-29 22:05 ` Pavel Skripkin [this message]
2021-04-30 3:44 ` Theodore Ts'o
2021-04-30 18:50 ` [PATCH v2] " Pavel Skripkin
2021-05-17 13:40 ` Pavel Skripkin
2021-05-17 18:34 ` Pavel Skripkin
2021-06-05 12:52 ` [RESEND PATCH " Pavel Skripkin
2021-06-17 1:15 ` [PATCH " Theodore Ts'o
-- strict thread matches above, loose matches on Subject: below --
2021-04-28 22:19 [PATCH] " Alexey Makhalov
2021-05-21 4:43 ` Theodore Y. Ts'o
2021-05-21 7:43 ` Alexey Makhalov
2021-05-21 14:29 ` Theodore Y. Ts'o
2021-05-21 16:12 ` Alexey Makhalov
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=20210430010547.38f27e39@gmail.com \
--to=paskripkin@gmail.com \
--cc=adilger.kernel@dilger.ca \
--cc=akpm@linux-foundation.org \
--cc=axboe@kernel.dk \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=pmladek@suse.com \
--cc=syzbot+d9e482e303930fa4f6ff@syzkaller.appspotmail.com \
--cc=tytso@mit.edu \
--cc=vegard.nossum@oracle.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;
as well as URLs for NNTP newsgroup(s).