All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+f2fs--- via Linux-f2fs-devel <linux-f2fs-devel@lists.sourceforge.net>
To: Matthew Wilcox <willy@infradead.org>
Cc: linux-fsdevel@vger.kernel.org, jaegeuk@kernel.org,
	syzbot+c0dc46208750f063d0e0@syzkaller.appspotmail.com,
	hch@lst.de, linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH] f2fs: Fix __write_node_folio() conversion
Date: Wed, 18 Jun 2025 21:40:05 +0000	[thread overview]
Message-ID: <175028280599.266369.3803881518609217106.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250601002709.4094344-1-willy@infradead.org>

Hello:

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

On Sun,  1 Jun 2025 01:26:54 +0100 you wrote:
> This conversion moved the folio_unlock() to inside __write_node_folio(),
> but missed one caller so we had a double-unlock on this path.
> 
> Cc: Christoph Hellwig <hch@lst.de>
> Cc: Chao Yu <chao@kernel.org>
> Cc: Jaegeuk Kim <jaegeuk@kernel.org>
> Reported-by: syzbot+c0dc46208750f063d0e0@syzkaller.appspotmail.com
> Fixes: 80f31d2a7e5f (f2fs: return bool from __write_node_folio)
> Signed-off-by: Matthew Wilcox (Oracle) <willy@infradead.org>
> 
> [...]

Here is the summary with links:
  - [f2fs-dev] f2fs: Fix __write_node_folio() conversion
    https://git.kernel.org/jaegeuk/f2fs/c/6dea74e454c2

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: Matthew Wilcox <willy@infradead.org>
Cc: linux-f2fs-devel@lists.sourceforge.net,
	linux-fsdevel@vger.kernel.org, jaegeuk@kernel.org, hch@lst.de,
	syzbot+c0dc46208750f063d0e0@syzkaller.appspotmail.com
Subject: Re: [f2fs-dev] [PATCH] f2fs: Fix __write_node_folio() conversion
Date: Wed, 18 Jun 2025 21:40:05 +0000	[thread overview]
Message-ID: <175028280599.266369.3803881518609217106.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250601002709.4094344-1-willy@infradead.org>

Hello:

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

On Sun,  1 Jun 2025 01:26:54 +0100 you wrote:
> This conversion moved the folio_unlock() to inside __write_node_folio(),
> but missed one caller so we had a double-unlock on this path.
> 
> Cc: Christoph Hellwig <hch@lst.de>
> Cc: Chao Yu <chao@kernel.org>
> Cc: Jaegeuk Kim <jaegeuk@kernel.org>
> Reported-by: syzbot+c0dc46208750f063d0e0@syzkaller.appspotmail.com
> Fixes: 80f31d2a7e5f (f2fs: return bool from __write_node_folio)
> Signed-off-by: Matthew Wilcox (Oracle) <willy@infradead.org>
> 
> [...]

Here is the summary with links:
  - [f2fs-dev] f2fs: Fix __write_node_folio() conversion
    https://git.kernel.org/jaegeuk/f2fs/c/6dea74e454c2

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



  parent reply	other threads:[~2025-06-18 21:39 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-01  0:26 [f2fs-dev] [PATCH] f2fs: Fix __write_node_folio() conversion Matthew Wilcox (Oracle)
2025-06-01  0:26 ` Matthew Wilcox (Oracle)
2025-06-02  5:00 ` [f2fs-dev] " Christoph Hellwig
2025-06-02  5:00   ` Christoph Hellwig
2025-06-03  6:31 ` [f2fs-dev] " Chao Yu via Linux-f2fs-devel
2025-06-03  6:31   ` Chao Yu
2025-06-18 21:40 ` patchwork-bot+f2fs--- via Linux-f2fs-devel [this message]
2025-06-18 21:40   ` [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=175028280599.266369.3803881518609217106.git-patchwork-notify@kernel.org \
    --to=linux-f2fs-devel@lists.sourceforge.net \
    --cc=hch@lst.de \
    --cc=jaegeuk@kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=patchwork-bot+f2fs@kernel.org \
    --cc=syzbot+c0dc46208750f063d0e0@syzkaller.appspotmail.com \
    --cc=willy@infradead.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.