linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Chao Yu <chao@kernel.org>
To: Jan Prusakowski <jprusakowski@google.com>, jaegeuk@kernel.org
Cc: chao@kernel.org, linux-kernel@vger.kernel.org,
	linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH] f2fs: vm_unmap_ram() may be called from an invalid context
Date: Thu, 24 Jul 2025 20:51:04 +0800	[thread overview]
Message-ID: <f3f1810b-667b-4b3a-a9fb-606a87097f86@kernel.org> (raw)
In-Reply-To: <20250724103016.5164-1-jprusakowski@google.com>

Jan,

On 2025/7/24 18:30, Jan Prusakowski via Linux-f2fs-devel wrote:
> When testing F2FS with xfstests using UFS backed virtual disks the
> kernel complains sometimes that f2fs_release_decomp_mem() calls
> vm_unmap_ram() from an invalid context.

It will be better to include testcase & crash information in commit
message.

> 
> This patch modifies in_task() check inside f2fs_read_end_io() to also
> check if interrupts are disabled. This ensures that pages are unmapped
> asynchronously in an interrupt handler.
> 
> Fixes: bff139b (f2fs: handle decompress only post processing in softirq)

./scripts/checkpatch.pl will output below warning message:

WARNING: Please use correct Fixes: style 'Fixes: <12+ chars of sha1> ("<title line>")' - ie: 'Fixes: bff139b49d9f ("f2fs: handle decompress only post processing in softirq")'

Please use this instead:

Fixes: bff139b49d9f ("f2fs: handle decompress only post processing in softirq")

> 
> Signed-off-by: Jan Prusakowski <jprusakowski@google.com>

Code part looks good to me, please feel free to add my RVB tag in next version:

Reviewed-by: Chao Yu <chao@kernel.org>

Thanks,

> ---
>   fs/f2fs/data.c | 2 +-
>   1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/fs/f2fs/data.c b/fs/f2fs/data.c
> index d1a2616d41be..0acc25f996b3 100644
> --- a/fs/f2fs/data.c
> +++ b/fs/f2fs/data.c
> @@ -280,7 +280,7 @@ static void f2fs_read_end_io(struct bio *bio)
>   {
>   	struct f2fs_sb_info *sbi = F2FS_F_SB(bio_first_folio_all(bio));
>   	struct bio_post_read_ctx *ctx;
> -	bool intask = in_task();
> +	bool intask = in_task() && !irqs_disabled();
>   
>   	iostat_update_and_unbind_ctx(bio);
>   	ctx = bio->bi_private;


      reply	other threads:[~2025-07-24 12:51 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-24 10:30 [PATCH] f2fs: vm_unmap_ram() may be called from an invalid context Jan Prusakowski
2025-07-24 12:51 ` Chao Yu [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=f3f1810b-667b-4b3a-a9fb-606a87097f86@kernel.org \
    --to=chao@kernel.org \
    --cc=jaegeuk@kernel.org \
    --cc=jprusakowski@google.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 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).