OrangePi_CM5/fs/nilfs2
Ryusuke Konishi 4feedde548 nilfs2: fix use-after-free bug of ns_writer on remount
commit 8cccf05fe857a18ee26e20d11a8455a73ffd4efd upstream.

If a nilfs2 filesystem is downgraded to read-only due to metadata
corruption on disk and is remounted read/write, or if emergency read-only
remount is performed, detaching a log writer and synchronizing the
filesystem can be done at the same time.

In these cases, use-after-free of the log writer (hereinafter
nilfs->ns_writer) can happen as shown in the scenario below:

 Task1                               Task2
 --------------------------------    ------------------------------
 nilfs_construct_segment
   nilfs_segctor_sync
     init_wait
     init_waitqueue_entry
     add_wait_queue
     schedule
                                     nilfs_remount (R/W remount case)
				       nilfs_attach_log_writer
                                         nilfs_detach_log_writer
                                           nilfs_segctor_destroy
                                             kfree
     finish_wait
       _raw_spin_lock_irqsave
         __raw_spin_lock_irqsave
           do_raw_spin_lock
             debug_spin_lock_before  <-- use-after-free

While Task1 is sleeping, nilfs->ns_writer is freed by Task2.  After Task1
waked up, Task1 accesses nilfs->ns_writer which is already freed.  This
scenario diagram is based on the Shigeru Yoshida's post [1].

This patch fixes the issue by not detaching nilfs->ns_writer on remount so
that this UAF race doesn't happen.  Along with this change, this patch
also inserts a few necessary read-only checks with superblock instance
where only the ns_writer pointer was used to check if the filesystem is
read-only.

Link: https://syzkaller.appspot.com/bug?id=79a4c002e960419ca173d55e863bd09e8112df8b
Link: https://lkml.kernel.org/r/20221103141759.1836312-1-syoshida@redhat.com [1]
Link: https://lkml.kernel.org/r/20221104142959.28296-1-konishi.ryusuke@gmail.com
Signed-off-by: Ryusuke Konishi <konishi.ryusuke@gmail.com>
Reported-by: syzbot+f816fa82f8783f7a02bb@syzkaller.appspotmail.com
Reported-by: Shigeru Yoshida <syoshida@redhat.com>
Tested-by: Ryusuke Konishi <konishi.ryusuke@gmail.com>
Cc: <stable@vger.kernel.org>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
2022-11-16 09:57:16 +01:00
..
Kconfig
…
Makefile
…
alloc.c
…
alloc.h
…
bmap.c
…
bmap.h
…
btnode.c nilfs2: fix lockdep warnings in page operations for btree nodes 2022-05-25 09:17:54 +02:00
btnode.h nilfs2: fix lockdep warnings in page operations for btree nodes 2022-05-25 09:17:54 +02:00
btree.c nilfs2: fix lockdep warnings in page operations for btree nodes 2022-05-25 09:17:54 +02:00
btree.h
…
cpfile.c
…
cpfile.h
…
dat.c nilfs2: fix lockdep warnings during disk space reclamation 2022-05-25 09:17:54 +02:00
dat.h
…
dir.c
…
direct.c
…
direct.h
…
export.h
…
file.c
…
gcinode.c nilfs2: fix lockdep warnings in page operations for btree nodes 2022-05-25 09:17:54 +02:00
ifile.c
…
ifile.h
…
inode.c nilfs2: fix use-after-free bug of struct nilfs_root 2022-10-15 07:55:50 +02:00
ioctl.c
…
mdt.c nilfs2: fix lockdep warnings during disk space reclamation 2022-05-25 09:17:54 +02:00
mdt.h nilfs2: fix lockdep warnings during disk space reclamation 2022-05-25 09:17:54 +02:00
namei.c
…
nilfs.h nilfs2: fix incorrect masking of permission flags for symlinks 2022-07-21 21:20:01 +02:00
page.c nilfs2: fix lockdep warnings in page operations for btree nodes 2022-05-25 09:17:54 +02:00
page.h
…
recovery.c
…
segbuf.c
…
segbuf.h
…
segment.c nilfs2: fix use-after-free bug of ns_writer on remount 2022-11-16 09:57:16 +01:00
segment.h
…
sufile.c
…
sufile.h
…
super.c nilfs2: fix use-after-free bug of ns_writer on remount 2022-11-16 09:57:16 +01:00
sysfs.c
…
sysfs.h
…
the_nilfs.c nilfs2: fix deadlock in nilfs_count_free_blocks() 2022-11-16 09:57:16 +01:00
the_nilfs.h
…