All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chao Yu <yuchao0@huawei.com>
To: Jaegeuk Kim <jaegeuk@kernel.org>, <linux-kernel@vger.kernel.org>,
	<linux-f2fs-devel@lists.sourceforge.net>,
	<kernel-team@android.com>
Subject: Re: [f2fs-dev] [PATCH 1/2] f2fs: don't allow any writes on readonly mount
Date: Mon, 7 Dec 2020 15:51:28 +0800	[thread overview]
Message-ID: <48d45bbd-baaf-e29e-8351-df375ee5a8b0@huawei.com> (raw)
In-Reply-To: <20201203205522.891082-1-jaegeuk@kernel.org>

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@kernel.org>

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

Thanks,

WARNING: multiple messages have this Message-ID (diff)
From: Chao Yu <yuchao0@huawei.com>
To: Jaegeuk Kim <jaegeuk@kernel.org>, <linux-kernel@vger.kernel.org>,
	<linux-f2fs-devel@lists.sourceforge.net>,
	<kernel-team@android.com>
Subject: Re: [f2fs-dev] [PATCH 1/2] f2fs: don't allow any writes on readonly mount
Date: Mon, 7 Dec 2020 15:51:28 +0800	[thread overview]
Message-ID: <48d45bbd-baaf-e29e-8351-df375ee5a8b0@huawei.com> (raw)
In-Reply-To: <20201203205522.891082-1-jaegeuk@kernel.org>

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@kernel.org>

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

Thanks,


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

  parent reply	other threads:[~2020-12-07  7:52 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-03 20:55 [PATCH 1/2] f2fs: don't allow any writes on readonly mount Jaegeuk Kim
2020-12-03 20:55 ` [f2fs-dev] " Jaegeuk Kim
2020-12-03 20:55 ` [PATCH 2/2] f2fs: introduce max_io_bytes, a sysfs entry, to limit bio size Jaegeuk Kim
2020-12-03 20:55   ` [f2fs-dev] " Jaegeuk Kim
2020-12-07  7:55   ` Chao Yu
2020-12-07  7:55     ` Chao Yu
2020-12-07  7:51 ` Chao Yu [this message]
2020-12-07  7:51   ` [f2fs-dev] [PATCH 1/2] f2fs: don't allow any writes on readonly mount 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=48d45bbd-baaf-e29e-8351-df375ee5a8b0@huawei.com \
    --to=yuchao0@huawei.com \
    --cc=jaegeuk@kernel.org \
    --cc=kernel-team@android.com \
    --cc=linux-f2fs-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    /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.