mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: patchwork-bot+f2fs@kernel.org
To: Jan Prusakowski <jprusakowski@google.com>
Cc: jaegeuk@kernel.org, linux-kernel@vger.kernel.org,
	linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH v2] f2fs: vm_unmap_ram() may be called from an invalid context
Date: Thu, 24 Jul 2025 20:30:14 +0000	[thread overview]
Message-ID: <175338901449.2519964.11721744043840464584.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250724153115.125311-1-jprusakowski@google.com>

Hello:

This patch was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:

On Thu, 24 Jul 2025 17:31:15 +0200 you 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. Example trace from
> f2fs/007 test:
> 
> f2fs/007 5s ...  [12:59:38][    8.902525] run fstests f2fs/007
> [   11.468026] BUG: sleeping function called from invalid context at mm/vmalloc.c:2978
> [   11.471849] in_atomic(): 1, irqs_disabled(): 1, non_block: 0, pid: 68, name: irq/22-ufshcd
> [   11.475357] preempt_count: 1, expected: 0
> [   11.476970] RCU nest depth: 0, expected: 0
> [   11.478531] CPU: 0 UID: 0 PID: 68 Comm: irq/22-ufshcd Tainted: G        W           6.16.0-rc5-xfstests-ufs-g40f92e79b0aa #9 PREEMPT(none)
> [   11.478535] Tainted: [W]=WARN
> [   11.478536] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2 04/01/2014
> [   11.478537] Call Trace:
> [   11.478543]  <TASK>
> [   11.478545]  dump_stack_lvl+0x4e/0x70
> [   11.478554]  __might_resched.cold+0xaf/0xbe
> [   11.478557]  vm_unmap_ram+0x21/0xb0
> [   11.478560]  f2fs_release_decomp_mem+0x59/0x80
> [   11.478563]  f2fs_free_dic+0x18/0x1a0
> [   11.478565]  f2fs_finish_read_bio+0xd7/0x290
> [   11.478570]  blk_update_request+0xec/0x3b0
> [   11.478574]  ? sbitmap_queue_clear+0x3b/0x60
> [   11.478576]  scsi_end_request+0x27/0x1a0
> [   11.478582]  scsi_io_completion+0x40/0x300
> [   11.478583]  ufshcd_mcq_poll_cqe_lock+0xa3/0xe0
> [   11.478588]  ufshcd_sl_intr+0x194/0x1f0
> [   11.478592]  ufshcd_threaded_intr+0x68/0xb0
> [   11.478594]  ? __pfx_irq_thread_fn+0x10/0x10
> [   11.478599]  irq_thread_fn+0x20/0x60
> [   11.478602]  ? __pfx_irq_thread_fn+0x10/0x10
> [   11.478603]  irq_thread+0xb9/0x180
> [   11.478605]  ? __pfx_irq_thread_dtor+0x10/0x10
> [   11.478607]  ? __pfx_irq_thread+0x10/0x10
> [   11.478609]  kthread+0x10a/0x230
> [   11.478614]  ? __pfx_kthread+0x10/0x10
> [   11.478615]  ret_from_fork+0x7e/0xd0
> [   11.478619]  ? __pfx_kthread+0x10/0x10
> [   11.478621]  ret_from_fork_asm+0x1a/0x30
> [   11.478623]  </TASK>
> 
> [...]

Here is the summary with links:
  - [f2fs-dev,v2] f2fs: vm_unmap_ram() may be called from an invalid context
    https://git.kernel.org/jaegeuk/f2fs/c/08a7efc5b02a

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      reply	other threads:[~2025-07-24 20:29 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-24 15:31 Jan Prusakowski
2025-07-24 20:30 ` patchwork-bot+f2fs [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=175338901449.2519964.11721744043840464584.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+f2fs@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

all inboxes | Powered by JetHome®