From: Jan Kara <jack@suse.cz>
To: linux-fsdevel@vger.kernel.org
Cc: poma <pomidorabelisima@gmail.com>,
Richard Weinberger <richard.weinberger@gmail.com>,
LKML <linux-kernel@vger.kernel.org>,
eparis@parisplace.org
Subject: [PATCH 0/3] fsnotify: Fix handling of overflow events
Date: Mon, 24 Feb 2014 10:31:04 +0100 [thread overview]
Message-ID: <1393234267-22937-1-git-send-email-jack@suse.cz> (raw)
Hello,
these three patches fix problems with overflow events in fanotify and
inotify frameworks. Part of that (patches 1 & 3) is a fallout of my
rewrite of fsnotify framework. I've implemented testing of generation of
overflow events for fanotify and inotify in LTP and with these patches
the tests pass. Please check whether the patches fix problems for you as
well. I plan to push these fixes to Linus soon...
Honza
next reply other threads:[~2014-02-24 9:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-24 9:31 Jan Kara [this message]
2014-02-24 9:31 ` [PATCH 1/3] fsnotify: Fix detection whether overflow event is queued Jan Kara
2014-02-24 9:31 ` [PATCH 2/3] fanotify: Handle overflow in case of permission events Jan Kara
2014-02-24 9:31 ` [PATCH 3/3] fsnotify: Allocate overflow events with proper type Jan Kara
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=1393234267-22937-1-git-send-email-jack@suse.cz \
--to=jack@suse.cz \
--cc=eparis@parisplace.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pomidorabelisima@gmail.com \
--cc=richard.weinberger@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®