From: Gabriel Krisman Bertazi <krisman@collabora.com>
To: hughd@google.com, akpm@linux-foundation.org
Cc: linux-mm@kvack.org, jack@suse.com, amir73il@gmail.com,
repnop@google.com, khazhy@google.com,
Gabriel Krisman Bertazi <krisman@collabora.com>,
kernel@collabora.com
Subject: [PATCH 0/2] shmem: Notify user space when file system is full
Date: Tue, 16 Nov 2021 17:07:40 -0500 [thread overview]
Message-ID: <20211116220742.584975-1-krisman@collabora.com> (raw)
FS_ERROR is a fsnotify event type used by monitoring tools to detect
conditions that might require intervention from a recovery tool or from
sysadmins. This patch series enables tmpfs to report an event when an
operation fails because the file system is full.
It attempts to only report events when the filesystem is really full,
instead of errors caused by memory pressure. The first patch prepares
the terrain by detecting these two different conditions, and the second
patch actually adds the event triggers.
Gabriel Krisman Bertazi (2):
shmem: Differentiate cause of blk account error due to lack of space
shmem: Trigger FS_ERROR notification when file system is full
mm/shmem.c | 39 ++++++++++++++++++++++++++-------------
1 file changed, 26 insertions(+), 13 deletions(-)
--
2.33.0
next reply other threads:[~2021-11-16 22:08 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-16 22:07 Gabriel Krisman Bertazi [this message]
2021-11-16 22:07 ` [PATCH 1/2] shmem: Differentiate cause of blk account error due to lack of space Gabriel Krisman Bertazi
2021-11-16 22:07 ` [PATCH 2/2] shmem: Trigger FS_ERROR notification when file system is full Gabriel Krisman Bertazi
2021-11-17 9:00 ` [PATCH 0/2] shmem: Notify user space " Amir Goldstein
2022-01-11 1:57 ` Gabriel Krisman Bertazi
2022-01-11 7:50 ` Amir Goldstein
2022-01-12 3:19 ` Gabriel Krisman Bertazi
2022-01-12 5:59 ` Amir Goldstein
2022-01-14 20:17 ` Gabriel Krisman Bertazi
2022-01-14 22:16 ` Khazhy Kumykov
2022-01-15 11:30 ` Amir Goldstein
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=20211116220742.584975-1-krisman@collabora.com \
--to=krisman@collabora.com \
--cc=akpm@linux-foundation.org \
--cc=amir73il@gmail.com \
--cc=hughd@google.com \
--cc=jack@suse.com \
--cc=kernel@collabora.com \
--cc=khazhy@google.com \
--cc=linux-mm@kvack.org \
--cc=repnop@google.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 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.