From: Jan Kara <jack@suse.cz>
To: <linux-fsdevel@vger.kernel.org>
Cc: Shakeel Butt <shakeelb@google.com>,
Amir Goldstein <amir73il@gmail.com>, Jan Kara <jack@suse.cz>
Subject: [PATCH 0/2] fsnotify: Improve ENOMEM handling
Date: Wed, 21 Feb 2018 16:44:28 +0100 [thread overview]
Message-ID: <20180221154430.19195-1-jack@suse.cz> (raw)
Hello,
these two patches improve ENOMEM handling in fsnotify framework. In particular
we queue overflow event if we cannot report some event due to ENOMEM (currently
we just silently lose the event). We also make sure fanotify unlimited queues
cannot lose events due to ENOMEM. This series is prerequisite for memcg
charging of fsnotify events. Comments are welcome!
Honza
next reply other threads:[~2018-02-22 10:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-21 15:44 Jan Kara [this message]
2018-02-21 15:44 ` [PATCH 1/2] fanotify: Avoid lost events due to ENOMEM for unlimited queues Jan Kara
2018-02-22 16:04 ` Amir Goldstein
2018-02-22 16:22 ` Jan Kara
2018-02-22 18:34 ` Amir Goldstein
2018-02-26 13:06 ` Jan Kara
2018-02-26 13:17 ` Amir Goldstein
2018-02-21 15:44 ` [PATCH 2/2] fsnotify: Let userspace know about lost events due to ENOMEM Jan Kara
2018-02-22 16:06 ` 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=20180221154430.19195-1-jack@suse.cz \
--to=jack@suse.cz \
--cc=amir73il@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=shakeelb@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.