linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pavel Skripkin <paskripkin@gmail.com>
To: syzbot <syzbot+deb25600c2fd79ffd367@syzkaller.appspotmail.com>
Cc: adilger.kernel@dilger.ca, clang-built-linux@googlegroups.com,
	linux-ext4@vger.kernel.org, linux-kernel@vger.kernel.org,
	nathan@kernel.org, ndesaulniers@google.com,
	syzkaller-bugs@googlegroups.com, tytso@mit.edu
Subject: Re: [syzbot] INFO: task hung in ext4_put_super
Date: Fri, 16 Jul 2021 14:20:57 +0300	[thread overview]
Message-ID: <20210716142057.0f1f6045@gmail.com> (raw)
In-Reply-To: <000000000000f36f9505c73ae373@google.com>

On Fri, 16 Jul 2021 03:17:09 -0700
syzbot <syzbot+deb25600c2fd79ffd367@syzkaller.appspotmail.com> wrote:

> syzbot suspects this issue was fixed by commit:
> 
> commit 618f003199c6188e01472b03cdbba227f1dc5f24
> Author: Pavel Skripkin <paskripkin@gmail.com>
> Date:   Fri Apr 30 18:50:46 2021 +0000
> 
>     ext4: fix memory leak in ext4_fill_super
> 
> bisection log:
> https://syzkaller.appspot.com/x/bisect.txt?x=17ebaa22300000 start
> commit:   2f7b98d1e55c Merge tag 'drm-fixes-2021-04-16' of
> git://ano.. git tree:       upstream kernel config:
> https://syzkaller.appspot.com/x/.config?x=398c4d0fe6f66e68 dashboard
> link: https://syzkaller.appspot.com/bug?extid=deb25600c2fd79ffd367
> syz repro:
> https://syzkaller.appspot.com/x/repro.syz?x=170d645ad00000 C
> reproducer:   https://syzkaller.appspot.com/x/repro.c?x=16a03a2ed00000
> 
> If the result looks correct, please mark the issue as fixed by
> replying with:
> 
> #syz fix: ext4: fix memory leak in ext4_fill_super
> 
> For information about bisection process see:
> https://goo.gl/tpsmEJ#bisection


This looks correct. I've tested this patch a long time ago, but forgot
to mark it as fixed.

#syz fix: ext4: fix memory leak in ext4_fill_super

 
With regards,
Pavel Skripkin

      reply	other threads:[~2021-07-16 11:23 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-17 11:27 [syzbot] INFO: task hung in ext4_put_super syzbot
2021-05-17 18:09 ` Pavel Skripkin
2021-05-17 18:30   ` syzbot
2021-07-16 10:17 ` syzbot
2021-07-16 11:20   ` Pavel Skripkin [this message]

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=20210716142057.0f1f6045@gmail.com \
    --to=paskripkin@gmail.com \
    --cc=adilger.kernel@dilger.ca \
    --cc=clang-built-linux@googlegroups.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nathan@kernel.org \
    --cc=ndesaulniers@google.com \
    --cc=syzbot+deb25600c2fd79ffd367@syzkaller.appspotmail.com \
    --cc=syzkaller-bugs@googlegroups.com \
    --cc=tytso@mit.edu \
    /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).