From: patchwork-bot+f2fs--- via Linux-f2fs-devel <linux-f2fs-devel@lists.sourceforge.net>
To: Mateusz Guzik <mjguzik@gmail.com>
Cc: brauner@kernel.org, linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net,
linux-fsdevel@vger.kernel.org, oliver.sang@intel.com,
oe-lkp@lists.linux.dev, josef@toxicpanda.com, ltp@lists.linux.it
Subject: Re: [f2fs-dev] [PATCH] f2fs: don't call iput() from f2fs_drop_inode()
Date: Mon, 06 Oct 2025 18:00:06 +0000 [thread overview]
Message-ID: <175977360652.1498132.2436692293138075252.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250930232957.14361-1-mjguzik@gmail.com>
Hello:
This patch was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:
On Wed, 1 Oct 2025 01:29:57 +0200 you wrote:
> iput() calls the problematic routine, which does a ->i_count inc/dec
> cycle. Undoing it with iput() recurses into the problem.
>
> Note f2fs should not be playing games with the refcount to begin with,
> but that will be handled later. Right now solve the immediate
> regression.
>
> [...]
Here is the summary with links:
- [f2fs-dev] f2fs: don't call iput() from f2fs_drop_inode()
https://git.kernel.org/jaegeuk/f2fs/c/8ec5fc1ff77e
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
WARNING: multiple messages have this Message-ID (diff)
From: patchwork-bot+f2fs--- via ltp <ltp@lists.linux.it>
To: Mateusz Guzik <mjguzik@gmail.com>
Cc: brauner@kernel.org, linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net,
linux-fsdevel@vger.kernel.org, oliver.sang@intel.com,
oe-lkp@lists.linux.dev, josef@toxicpanda.com, ltp@lists.linux.it
Subject: Re: [LTP] [f2fs-dev] [PATCH] f2fs: don't call iput() from f2fs_drop_inode()
Date: Mon, 06 Oct 2025 18:00:06 +0000 [thread overview]
Message-ID: <175977360652.1498132.2436692293138075252.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250930232957.14361-1-mjguzik@gmail.com>
Hello:
This patch was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:
On Wed, 1 Oct 2025 01:29:57 +0200 you wrote:
> iput() calls the problematic routine, which does a ->i_count inc/dec
> cycle. Undoing it with iput() recurses into the problem.
>
> Note f2fs should not be playing games with the refcount to begin with,
> but that will be handled later. Right now solve the immediate
> regression.
>
> [...]
Here is the summary with links:
- [f2fs-dev] f2fs: don't call iput() from f2fs_drop_inode()
https://git.kernel.org/jaegeuk/f2fs/c/8ec5fc1ff77e
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
--
Mailing list info: https://lists.linux.it/listinfo/ltp
WARNING: multiple messages have this Message-ID (diff)
From: patchwork-bot+f2fs@kernel.org
To: Mateusz Guzik <mjguzik@gmail.com>
Cc: brauner@kernel.org, linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net, oe-lkp@lists.linux.dev,
oliver.sang@intel.com, linux-fsdevel@vger.kernel.org,
josef@toxicpanda.com, ltp@lists.linux.it
Subject: Re: [f2fs-dev] [PATCH] f2fs: don't call iput() from f2fs_drop_inode()
Date: Mon, 06 Oct 2025 18:00:06 +0000 [thread overview]
Message-ID: <175977360652.1498132.2436692293138075252.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250930232957.14361-1-mjguzik@gmail.com>
Hello:
This patch was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:
On Wed, 1 Oct 2025 01:29:57 +0200 you wrote:
> iput() calls the problematic routine, which does a ->i_count inc/dec
> cycle. Undoing it with iput() recurses into the problem.
>
> Note f2fs should not be playing games with the refcount to begin with,
> but that will be handled later. Right now solve the immediate
> regression.
>
> [...]
Here is the summary with links:
- [f2fs-dev] f2fs: don't call iput() from f2fs_drop_inode()
https://git.kernel.org/jaegeuk/f2fs/c/8ec5fc1ff77e
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2025-10-06 18:00 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-30 6:41 [linus:master] [fs] bc986b1d75: Kernel_panic-not_syncing:softlockup:hung_tasks kernel test robot
2025-09-30 6:41 ` [LTP] " kernel test robot
2025-09-30 6:41 ` [f2fs-dev] " kernel test robot
2025-09-30 23:29 ` [f2fs-dev] [PATCH] f2fs: don't call iput() from f2fs_drop_inode() Mateusz Guzik
2025-09-30 23:29 ` Mateusz Guzik
2025-09-30 23:29 ` [LTP] " Mateusz Guzik
2025-10-01 15:39 ` [f2fs-dev] " Jaegeuk Kim via Linux-f2fs-devel
2025-10-01 15:39 ` Jaegeuk Kim
2025-10-01 15:39 ` [LTP] " Jaegeuk Kim via ltp
2025-10-06 18:00 ` patchwork-bot+f2fs--- via Linux-f2fs-devel [this message]
2025-10-06 18:00 ` [f2fs-dev] " patchwork-bot+f2fs
2025-10-06 18:00 ` [LTP] " patchwork-bot+f2fs--- via ltp
2025-10-09 3:34 ` Chao Yu via Linux-f2fs-devel
2025-10-09 3:34 ` Chao Yu
2025-10-09 3:34 ` [LTP] " Chao Yu via ltp
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=175977360652.1498132.2436692293138075252.git-patchwork-notify@kernel.org \
--to=linux-f2fs-devel@lists.sourceforge.net \
--cc=brauner@kernel.org \
--cc=josef@toxicpanda.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ltp@lists.linux.it \
--cc=mjguzik@gmail.com \
--cc=oe-lkp@lists.linux.dev \
--cc=oliver.sang@intel.com \
--cc=patchwork-bot+f2fs@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.