linux-kernel - Re: [f2fs-dev] [PATCH 1/2] f2fs: don't allow any writes on readonly mount

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <48d45bbd-baaf-e29e-8351-df375ee5a8b0@huawei.com>
Date:   Mon, 7 Dec 2020 15:51:28 +0800
From:   Chao Yu <yuchao0@...wei.com>
To:     Jaegeuk Kim <jaegeuk@...nel.org>, <linux-kernel@...r.kernel.org>,
        <linux-f2fs-devel@...ts.sourceforge.net>, <kernel-team@...roid.com>
Subject: Re: [f2fs-dev] [PATCH 1/2] f2fs: don't allow any writes on readonly
 mount

On 2020/12/4 4:55, Jaegeuk Kim wrote:
> generic_make_request: Trying to write to read-only block-device dm-5 (partno 0)
> WARNING: CPU: 7 PID: 546 at block/blk-core.c:2190 generic_make_request_checks+0x664/0x690
> pc : generic_make_request_checks+0x664/0x690
> lr : generic_make_request_checks+0x664/0x690
> Call trace:
>   generic_make_request_checks+0x664/0x690
>   generic_make_request+0xf0/0x3a4
>   submit_bio+0x80/0x250
>   __submit_merged_bio+0x368/0x4e0
>   __submit_merged_write_cond.llvm.12294350193007536502+0xe0/0x3e8
>   f2fs_wait_on_page_writeback+0x84/0x128
>   f2fs_convert_inline_page+0x35c/0x6f8
>   f2fs_convert_inline_inode+0xe0/0x2e0
>   f2fs_file_mmap+0x48/0x9c
>   mmap_region+0x41c/0x74c
>   do_mmap+0x40c/0x4fc
>   vm_mmap_pgoff+0xb8/0x114
>   vm_mmap+0x34/0x48
>   elf_map+0x68/0x108
>   load_elf_binary+0x538/0xb70
>   search_binary_handler+0xac/0x1dc
>   exec_binprm+0x50/0x15c
>   __do_execve_file+0x620/0x740
>   __arm64_sys_execve+0x54/0x68
>   el0_svc_common+0x9c/0x168
>   el0_svc_handler+0x60/0x6c
>   el0_svc+0x8/0xc
> 
> Signed-off-by: Jaegeuk Kim <jaegeuk@...nel.org>

Reviewed-by: Chao Yu <yuchao0@...wei.com>

Thanks,