From: patchwork-bot+f2fs@kernel.org
To: Chao Yu <chao@kernel.org>
Cc: jaegeuk@kernel.org, linux-f2fs-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org, r.smirnov@omp.ru
Subject: Re: [f2fs-dev] [PATCH] f2fs: fix to detect inconsistent nat entry during truncation
Date: Sun, 14 Apr 2024 15:32:45 +0000 [thread overview]
Message-ID: <171310876541.3156.7562582983890566171.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240322145955.2959257-1-chao@kernel.org>
Hello:
This patch was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:
On Fri, 22 Mar 2024 22:59:55 +0800 you wrote:
> As Roman Smirnov reported as below:
>
> "
> There is a possible bug in f2fs_truncate_inode_blocks():
>
> if (err < 0 && err != -ENOENT)
> goto fail;
> ...
> offset[1] = 0;
> offset[0]++;
> nofs += err;
>
> [...]
Here is the summary with links:
- [f2fs-dev] f2fs: fix to detect inconsistent nat entry during truncation
https://git.kernel.org/jaegeuk/f2fs/c/92c556ed6318
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@kernel.org
To: Chao Yu <chao@kernel.org>
Cc: jaegeuk@kernel.org, r.smirnov@omp.ru,
linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH] f2fs: fix to detect inconsistent nat entry during truncation
Date: Sun, 14 Apr 2024 15:32:45 +0000 [thread overview]
Message-ID: <171310876541.3156.7562582983890566171.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240322145955.2959257-1-chao@kernel.org>
Hello:
This patch was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:
On Fri, 22 Mar 2024 22:59:55 +0800 you wrote:
> As Roman Smirnov reported as below:
>
> "
> There is a possible bug in f2fs_truncate_inode_blocks():
>
> if (err < 0 && err != -ENOENT)
> goto fail;
> ...
> offset[1] = 0;
> offset[0]++;
> nofs += err;
>
> [...]
Here is the summary with links:
- [f2fs-dev] f2fs: fix to detect inconsistent nat entry during truncation
https://git.kernel.org/jaegeuk/f2fs/c/92c556ed6318
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:[~2024-04-14 15:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-22 14:59 [f2fs-dev] [PATCH] f2fs: fix to detect inconsistent nat entry during truncation Chao Yu
2024-03-22 14:59 ` Chao Yu
2024-04-14 15:32 ` patchwork-bot+f2fs [this message]
2024-04-14 15:32 ` [f2fs-dev] " patchwork-bot+f2fs
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=171310876541.3156.7562582983890566171.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=r.smirnov@omp.ru \
/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.