From: Andrew Morton <akpm@linux-foundation.org>
To: mm-commits@vger.kernel.org, brauner@kernel.org,
colin.i.king@gmail.com, akpm@linux-foundation.org
Subject: [merged mm-nonmm-stable] fs-hfsplus-make-extend-error-rate-limited.patch removed from -mm tree
Date: Sat, 12 Aug 2023 15:05:43 -0700 [thread overview]
Message-ID: <20230812220544.01981C433C8@smtp.kernel.org> (raw)
The quilt patch titled
Subject: fs: hfsplus: make extend error rate limited
has been removed from the -mm tree. Its filename was
fs-hfsplus-make-extend-error-rate-limited.patch
This patch was dropped because it was merged into the mm-nonmm-stable branch
of git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm
------------------------------------------------------
From: Colin Ian King <colin.i.king@gmail.com>
Subject: fs: hfsplus: make extend error rate limited
Date: Wed, 19 Jul 2023 13:17:35 +0100
Extending a file where there is not enough free space can trigger frequent
extend alloc file error messages and this can easily spam the kernel log.
Make the error message rate limited.
Link: https://lkml.kernel.org/r/20230719121735.2831164-1-colin.i.king@gmail.com
Signed-off-by: Colin Ian King <colin.i.king@gmail.com>
Cc: Christian Brauner <brauner@kernel.org>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---
fs/hfsplus/extents.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
--- a/fs/hfsplus/extents.c~fs-hfsplus-make-extend-error-rate-limited
+++ a/fs/hfsplus/extents.c
@@ -448,9 +448,9 @@ int hfsplus_file_extend(struct inode *in
if (sbi->alloc_file->i_size * 8 <
sbi->total_blocks - sbi->free_blocks + 8) {
/* extend alloc file */
- pr_err("extend alloc file! (%llu,%u,%u)\n",
- sbi->alloc_file->i_size * 8,
- sbi->total_blocks, sbi->free_blocks);
+ pr_err_ratelimited("extend alloc file! (%llu,%u,%u)\n",
+ sbi->alloc_file->i_size * 8,
+ sbi->total_blocks, sbi->free_blocks);
return -ENOSPC;
}
_
Patches currently in -mm which might be from colin.i.king@gmail.com are
reply other threads:[~2023-08-12 22:06 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20230812220544.01981C433C8@smtp.kernel.org \
--to=akpm@linux-foundation.org \
--cc=brauner@kernel.org \
--cc=colin.i.king@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mm-commits@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 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.