The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: patchwork-bot+f2fs@kernel.org
To: Chao Yu <chao@kernel.org>
Cc: jaegeuk@kernel.org, piergiorgio.sartor@nexgo.de,
	linux-kernel@vger.kernel.org, stable@vger.kernel.org,
	linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH] f2fs: fix to drop all discards after creating snapshot on lvm device
Date: Sat, 23 Nov 2024 15:50:40 +0000	[thread overview]
Message-ID: <173237704074.3018181.13969811981387299887.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20241121141716.3018855-1-chao@kernel.org>

Hello:

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

On Thu, 21 Nov 2024 22:17:16 +0800 you wrote:
> Piergiorgio reported a bug in bugzilla as below:
> 
> ------------[ cut here ]------------
> WARNING: CPU: 2 PID: 969 at fs/f2fs/segment.c:1330
> RIP: 0010:__submit_discard_cmd+0x27d/0x400 [f2fs]
> Call Trace:
>  __issue_discard_cmd+0x1ca/0x350 [f2fs]
>  issue_discard_thread+0x191/0x480 [f2fs]
>  kthread+0xcf/0x100
>  ret_from_fork+0x31/0x50
>  ret_from_fork_asm+0x1a/0x30
> 
> [...]

Here is the summary with links:
  - [f2fs-dev] f2fs: fix to drop all discards after creating snapshot on lvm device
    https://git.kernel.org/jaegeuk/f2fs/c/bc8aeb04fd80

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



      reply	other threads:[~2024-11-23 15:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-21 14:17 [PATCH] f2fs: fix to drop all discards after creating snapshot on lvm device Chao Yu
2024-11-23 15:50 ` 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=173237704074.3018181.13969811981387299887.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+f2fs@kernel.org \
    --cc=chao@kernel.org \
    --cc=jaegeuk@kernel.org \
    --cc=linux-f2fs-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=piergiorgio.sartor@nexgo.de \
    --cc=stable@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