All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jaegeuk Kim <jaegeuk@kernel.org>
To: Chao Yu <chao@kernel.org>
Cc: syzbot+1a8e2b31f2ac9bd3d148@syzkaller.appspotmail.com,
	linux-kernel@vger.kernel.org,
	linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH] f2fs: fix to avoid use-after-free in f2fs_stop_gc_thread()
Date: Sat, 27 Jul 2024 15:27:00 +0000	[thread overview]
Message-ID: <ZqURxBYKHipWcz_U@google.com> (raw)
In-Reply-To: <ZqUOFzAPXE8plKU0@google.com>

On 07/27, Jaegeuk Kim wrote:
> On 07/25, Chao Yu wrote:
> > syzbot reports a f2fs bug as below:
> > 
> >  __dump_stack lib/dump_stack.c:88 [inline]
> >  dump_stack_lvl+0x241/0x360 lib/dump_stack.c:114
> >  print_report+0xe8/0x550 mm/kasan/report.c:491
> >  kasan_report+0x143/0x180 mm/kasan/report.c:601
> >  kasan_check_range+0x282/0x290 mm/kasan/generic.c:189
> >  instrument_atomic_read_write include/linux/instrumented.h:96 [inline]
> >  atomic_fetch_add_relaxed include/linux/atomic/atomic-instrumented.h:252 [inline]
> >  __refcount_add include/linux/refcount.h:184 [inline]
> >  __refcount_inc include/linux/refcount.h:241 [inline]
> >  refcount_inc include/linux/refcount.h:258 [inline]
> >  get_task_struct include/linux/sched/task.h:118 [inline]
> >  kthread_stop+0xca/0x630 kernel/kthread.c:704
> >  f2fs_stop_gc_thread+0x65/0xb0 fs/f2fs/gc.c:210
> >  f2fs_do_shutdown+0x192/0x540 fs/f2fs/file.c:2283
> >  f2fs_ioc_shutdown fs/f2fs/file.c:2325 [inline]
> >  __f2fs_ioctl+0x443a/0xbe60 fs/f2fs/file.c:4325
> >  vfs_ioctl fs/ioctl.c:51 [inline]
> >  __do_sys_ioctl fs/ioctl.c:907 [inline]
> >  __se_sys_ioctl+0xfc/0x170 fs/ioctl.c:893
> >  do_syscall_x64 arch/x86/entry/common.c:52 [inline]
> >  do_syscall_64+0xf3/0x230 arch/x86/entry/common.c:83
> >  entry_SYSCALL_64_after_hwframe+0x77/0x7f
> > 
> > The root cause is below race condition, it may cause use-after-free
> > issue in sbi->gc_th pointer.
> > 
> > - remount
> >  - f2fs_remount
> >   - f2fs_stop_gc_thread
> >    - kfree(gc_th)
> > 				- f2fs_ioc_shutdown
> > 				 - f2fs_do_shutdown
> > 				  - f2fs_stop_gc_thread
> > 				   - kthread_stop(gc_th->f2fs_gc_task)
> > 
> > We will call f2fs_do_shutdown() in two paths:
> > - for f2fs_ioc_shutdown() path, we should grab sb->s_umount semaphore
> > for fixing.
> > - for f2fs_shutdown() path, it's safe since caller has already grabbed
> > sb->s_umount semaphore.
> > 
> > Reported-by: syzbot+1a8e2b31f2ac9bd3d148@syzkaller.appspotmail.com
> > Closes: https://lore.kernel.org/linux-f2fs-devel/0000000000005c7ccb061e032b9b@google.com
> > Fixes: 7950e9ac638e ("f2fs: stop gc/discard thread after fs shutdown")
> > Signed-off-by: Chao Yu <chao@kernel.org>
> > ---
> >  fs/f2fs/file.c | 3 +++
> >  1 file changed, 3 insertions(+)
> > 
> > diff --git a/fs/f2fs/file.c b/fs/f2fs/file.c
> > index 7a37f2b393b9..62d72da25754 100644
> > --- a/fs/f2fs/file.c
> > +++ b/fs/f2fs/file.c
> > @@ -2388,7 +2388,10 @@ static int f2fs_ioc_shutdown(struct file *filp, unsigned long arg)
> >  		}
> >  	}
> >  
> > +	/* grab sb->s_umount to avoid racing w/ remount() */
> > +	down_read(&sbi->sb->s_umount);
> 
> Is this safe for freeze_bdev()?

bdev_freeze
 -> fs_bdev_freeze
  -> get_bdev_super
   -> bdev_super_lock(bdev, true)
    -> super_lock(sb, true)
     -> __super_lock(sb, true)
      -> down_write(s_umount)

> 
> >  	ret = f2fs_do_shutdown(sbi, in, readonly);
> > +	up_read(&sbi->sb->s_umount);
> >  
> >  	if (need_drop)
> >  		mnt_drop_write_file(filp);
> > -- 
> > 2.40.1


_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel

WARNING: multiple messages have this Message-ID (diff)
From: Jaegeuk Kim <jaegeuk@kernel.org>
To: Chao Yu <chao@kernel.org>
Cc: linux-f2fs-devel@lists.sourceforge.net,
	linux-kernel@vger.kernel.org,
	syzbot+1a8e2b31f2ac9bd3d148@syzkaller.appspotmail.com
Subject: Re: [PATCH] f2fs: fix to avoid use-after-free in f2fs_stop_gc_thread()
Date: Sat, 27 Jul 2024 15:27:00 +0000	[thread overview]
Message-ID: <ZqURxBYKHipWcz_U@google.com> (raw)
In-Reply-To: <ZqUOFzAPXE8plKU0@google.com>

On 07/27, Jaegeuk Kim wrote:
> On 07/25, Chao Yu wrote:
> > syzbot reports a f2fs bug as below:
> > 
> >  __dump_stack lib/dump_stack.c:88 [inline]
> >  dump_stack_lvl+0x241/0x360 lib/dump_stack.c:114
> >  print_report+0xe8/0x550 mm/kasan/report.c:491
> >  kasan_report+0x143/0x180 mm/kasan/report.c:601
> >  kasan_check_range+0x282/0x290 mm/kasan/generic.c:189
> >  instrument_atomic_read_write include/linux/instrumented.h:96 [inline]
> >  atomic_fetch_add_relaxed include/linux/atomic/atomic-instrumented.h:252 [inline]
> >  __refcount_add include/linux/refcount.h:184 [inline]
> >  __refcount_inc include/linux/refcount.h:241 [inline]
> >  refcount_inc include/linux/refcount.h:258 [inline]
> >  get_task_struct include/linux/sched/task.h:118 [inline]
> >  kthread_stop+0xca/0x630 kernel/kthread.c:704
> >  f2fs_stop_gc_thread+0x65/0xb0 fs/f2fs/gc.c:210
> >  f2fs_do_shutdown+0x192/0x540 fs/f2fs/file.c:2283
> >  f2fs_ioc_shutdown fs/f2fs/file.c:2325 [inline]
> >  __f2fs_ioctl+0x443a/0xbe60 fs/f2fs/file.c:4325
> >  vfs_ioctl fs/ioctl.c:51 [inline]
> >  __do_sys_ioctl fs/ioctl.c:907 [inline]
> >  __se_sys_ioctl+0xfc/0x170 fs/ioctl.c:893
> >  do_syscall_x64 arch/x86/entry/common.c:52 [inline]
> >  do_syscall_64+0xf3/0x230 arch/x86/entry/common.c:83
> >  entry_SYSCALL_64_after_hwframe+0x77/0x7f
> > 
> > The root cause is below race condition, it may cause use-after-free
> > issue in sbi->gc_th pointer.
> > 
> > - remount
> >  - f2fs_remount
> >   - f2fs_stop_gc_thread
> >    - kfree(gc_th)
> > 				- f2fs_ioc_shutdown
> > 				 - f2fs_do_shutdown
> > 				  - f2fs_stop_gc_thread
> > 				   - kthread_stop(gc_th->f2fs_gc_task)
> > 
> > We will call f2fs_do_shutdown() in two paths:
> > - for f2fs_ioc_shutdown() path, we should grab sb->s_umount semaphore
> > for fixing.
> > - for f2fs_shutdown() path, it's safe since caller has already grabbed
> > sb->s_umount semaphore.
> > 
> > Reported-by: syzbot+1a8e2b31f2ac9bd3d148@syzkaller.appspotmail.com
> > Closes: https://lore.kernel.org/linux-f2fs-devel/0000000000005c7ccb061e032b9b@google.com
> > Fixes: 7950e9ac638e ("f2fs: stop gc/discard thread after fs shutdown")
> > Signed-off-by: Chao Yu <chao@kernel.org>
> > ---
> >  fs/f2fs/file.c | 3 +++
> >  1 file changed, 3 insertions(+)
> > 
> > diff --git a/fs/f2fs/file.c b/fs/f2fs/file.c
> > index 7a37f2b393b9..62d72da25754 100644
> > --- a/fs/f2fs/file.c
> > +++ b/fs/f2fs/file.c
> > @@ -2388,7 +2388,10 @@ static int f2fs_ioc_shutdown(struct file *filp, unsigned long arg)
> >  		}
> >  	}
> >  
> > +	/* grab sb->s_umount to avoid racing w/ remount() */
> > +	down_read(&sbi->sb->s_umount);
> 
> Is this safe for freeze_bdev()?

bdev_freeze
 -> fs_bdev_freeze
  -> get_bdev_super
   -> bdev_super_lock(bdev, true)
    -> super_lock(sb, true)
     -> __super_lock(sb, true)
      -> down_write(s_umount)

> 
> >  	ret = f2fs_do_shutdown(sbi, in, readonly);
> > +	up_read(&sbi->sb->s_umount);
> >  
> >  	if (need_drop)
> >  		mnt_drop_write_file(filp);
> > -- 
> > 2.40.1

  reply	other threads:[~2024-07-27 15:27 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-25  2:08 [f2fs-dev] [PATCH] f2fs: fix to avoid use-after-free in f2fs_stop_gc_thread() Chao Yu
2024-07-25  2:08 ` Chao Yu
2024-07-27 15:11 ` [f2fs-dev] " Jaegeuk Kim
2024-07-27 15:11   ` Jaegeuk Kim
2024-07-27 15:27   ` Jaegeuk Kim [this message]
2024-07-27 15:27     ` Jaegeuk Kim
2024-07-29  1:11     ` [f2fs-dev] " Chao Yu
2024-07-29  1:11       ` Chao Yu

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=ZqURxBYKHipWcz_U@google.com \
    --to=jaegeuk@kernel.org \
    --cc=chao@kernel.org \
    --cc=linux-f2fs-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=syzbot+1a8e2b31f2ac9bd3d148@syzkaller.appspotmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.