From: Jaegeuk Kim <jaegeuk@kernel.org>
To: linux-kernel@vger.kernel.org, linux-f2fs-devel@lists.sourceforge.net
Cc: Jaegeuk Kim <jaegeuk@kernel.org>
Subject: [PATCH 1/5] f2fs: stop allocating pinned sections if EAGAIN happens
Date: Fri, 6 May 2022 16:20:28 -0700 [thread overview]
Message-ID: <20220506232032.1264078-1-jaegeuk@kernel.org> (raw)
EAGAIN doesn't guarantee to have a free section. Let's report it.
Signed-off-by: Jaegeuk Kim <jaegeuk@kernel.org>
---
fs/f2fs/file.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/fs/f2fs/file.c b/fs/f2fs/file.c
index e4cf8b7b23aa..b307d96a0a7c 100644
--- a/fs/f2fs/file.c
+++ b/fs/f2fs/file.c
@@ -1685,7 +1685,7 @@ static int expand_inode_data(struct inode *inode, loff_t offset,
GET_SEC_FROM_SEG(sbi, overprovision_segments(sbi)))) {
f2fs_down_write(&sbi->gc_lock);
err = f2fs_gc(sbi, true, false, false, NULL_SEGNO);
- if (err && err != -ENODATA && err != -EAGAIN)
+ if (err && err != -ENODATA)
goto out_err;
}
--
2.36.0.512.ge40c2bad7a-goog
next reply other threads:[~2022-05-06 23:20 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-06 23:20 Jaegeuk Kim [this message]
2022-05-06 23:20 ` [PATCH 2/5] f2fs: introduce f2fs_gc_control to consolidate f2fs_gc parameters Jaegeuk Kim
2022-05-08 14:27 ` [f2fs-dev] " Chao Yu
2022-05-09 16:46 ` Jaegeuk Kim
2022-05-09 16:47 ` [PATCH 2/5 v2] " Jaegeuk Kim
2022-05-11 3:16 ` [f2fs-dev] " Chao Yu
2022-05-11 3:30 ` Jaegeuk Kim
2022-05-11 3:30 ` Jaegeuk Kim
2022-05-11 8:54 ` Chao Yu
2022-05-12 20:51 ` Jaegeuk Kim
2022-05-06 23:20 ` [PATCH 3/5] f2fs: keep wait_ms if EAGAIN happens Jaegeuk Kim
2022-05-08 14:41 ` [f2fs-dev] " Chao Yu
2022-05-08 15:22 ` Chao Yu
2022-05-06 23:20 ` [PATCH 4/5] f2fs: do not stop GC when requiring a free section Jaegeuk Kim
2022-05-07 3:33 ` [f2fs-dev] " Chao Yu
2022-05-09 16:58 ` Jaegeuk Kim
2022-05-08 15:25 ` Chao Yu
2022-05-09 16:55 ` Jaegeuk Kim
2022-05-11 8:53 ` Chao Yu
2022-05-11 16:47 ` Jaegeuk Kim
2022-05-12 2:04 ` Chao Yu
2022-05-12 21:05 ` Jaegeuk Kim
2022-05-12 20:50 ` [PATCH 4/5 v2] " Jaegeuk Kim
2022-05-12 21:54 ` [f2fs-dev] " Jaegeuk Kim
2022-05-15 14:26 ` Chao Yu
2022-05-16 17:29 ` Jaegeuk Kim
2022-05-17 2:19 ` Chao Yu
2022-05-06 23:20 ` [PATCH 5/5] f2fs: don't need inode lock for system hidden quota Jaegeuk Kim
2022-05-08 13:56 ` [f2fs-dev] [PATCH 1/5] f2fs: stop allocating pinned sections if EAGAIN happens Chao Yu
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=20220506232032.1264078-1-jaegeuk@kernel.org \
--to=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@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
Powered by JetHome