linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Miklos Szeredi <miklos@szeredi.hu>
To: Tetsuo Handa <penguin-kernel@i-love.sakura.ne.jp>
Cc: syzbot <syzbot+ec3986119086fe4eec97@syzkaller.appspotmail.com>,
	linux-fsdevel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: [PATCH] fuse: don't keep dead fuse_conn at fuse_fill_super().
Date: Thu, 31 May 2018 12:19:21 +0200	[thread overview]
Message-ID: <CAJfpegurFYKVXhRCman9A8JnrnvVPXaK+zBL5HHUzVi3tJG0Cw@mail.gmail.com> (raw)
In-Reply-To: <cfafbb9a-9e47-2489-8c71-9a6bc0d40e80@I-love.SAKURA.ne.jp>

On Wed, May 9, 2018 at 1:01 PM, Tetsuo Handa
<penguin-kernel@i-love.sakura.ne.jp> wrote:
> From 606d54cd24b5b00e7a7e3597aabbe89719defc56 Mon Sep 17 00:00:00 2001
> From: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
> Date: Tue, 1 May 2018 13:12:14 +0900
> Subject: [PATCH] fuse: don't keep dead fuse_conn at fuse_fill_super().
>
> syzbot is reporting use-after-free at fuse_kill_sb_blk() [1].
> Since sb->s_fs_info field is not cleared after fc was released by
> fuse_conn_put() when initialization failed, fuse_kill_sb_blk() finds
> already released fc and tries to hold the lock. Fix this by clearing
> sb->s_fs_info field after calling fuse_conn_put().

Thanks, applied.

Miklos

      parent reply	other threads:[~2018-05-31 10:19 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-30 13:34 KASAN: use-after-free Read in fuse_kill_sb_blk syzbot
2018-05-01 10:03 ` Tetsuo Handa
2018-05-09 11:01   ` [PATCH] fuse: don't keep dead fuse_conn at fuse_fill_super() Tetsuo Handa
2018-05-19 14:03     ` Tetsuo Handa
2018-05-31 10:19     ` Miklos Szeredi [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=CAJfpegurFYKVXhRCman9A8JnrnvVPXaK+zBL5HHUzVi3tJG0Cw@mail.gmail.com \
    --to=miklos@szeredi.hu \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=penguin-kernel@i-love.sakura.ne.jp \
    --cc=syzbot+ec3986119086fe4eec97@syzkaller.appspotmail.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;
as well as URLs for NNTP newsgroup(s).