public inbox for ltp@lists.linux.it
 help / color / mirror / Atom feed
From: Chao Yu via ltp <ltp@lists.linux.it>
To: Mateusz Guzik <mjguzik@gmail.com>, brauner@kernel.org
Cc: chao@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: Thu, 9 Oct 2025 11:34:31 +0800	[thread overview]
Message-ID: <e6feb193-0d3d-4cbc-857b-7576db25e929@kernel.org> (raw)
In-Reply-To: <20250930232957.14361-1-mjguzik@gmail.com>

On 10/1/2025 7:29 AM, Mateusz Guzik 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.
> 
> Fixes: bc986b1d756482a ("fs: stop accessing ->i_count directly in f2fs and gfs2")
> Reported-by: kernel test robot <oliver.sang@intel.com>
> Closes: https://lore.kernel.org/oe-lkp/202509301450.138b448f-lkp@intel.com
> Signed-off-by: Mateusz Guzik <mjguzik@gmail.com>

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

Thanks,

-- 
Mailing list info: https://lists.linux.it/listinfo/ltp

      parent reply	other threads:[~2025-10-13 11:07 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-30  6:41 [LTP] [linus:master] [fs] bc986b1d75: Kernel_panic-not_syncing:softlockup:hung_tasks kernel test robot
2025-09-30 23:29 ` [LTP] [PATCH] f2fs: don't call iput() from f2fs_drop_inode() Mateusz Guzik
2025-10-01 15:39   ` Jaegeuk Kim via ltp
2025-10-06 18:00   ` [LTP] [f2fs-dev] " patchwork-bot+f2fs--- via ltp
2025-10-09  3:34   ` Chao Yu via ltp [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=e6feb193-0d3d-4cbc-857b-7576db25e929@kernel.org \
    --to=ltp@lists.linux.it \
    --cc=brauner@kernel.org \
    --cc=chao@kernel.org \
    --cc=josef@toxicpanda.com \
    --cc=linux-f2fs-devel@lists.sourceforge.net \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mjguzik@gmail.com \
    --cc=oe-lkp@lists.linux.dev \
    --cc=oliver.sang@intel.com \
    /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