All of lore.kernel.org
 help / color / mirror / Atom feed
From: akpm@linux-foundation.org
To: ulissesf@gmail.com, amy.griffis@hp.com, clem.taylor@gmail.com,
	rlove@google.com, stable@kernel.org, ttb@tentacle.dhs.org,
	mm-commits@vger.kernel.org
Subject: - inotify-fix-check-for-one-shot-watches-before-destroying-them.patch removed from -mm tree
Date: Fri, 08 Feb 2008 12:11:19 -0800	[thread overview]
Message-ID: <200802082011.m18KB1IP010084@imap1.linux-foundation.org> (raw)


The patch titled
     inotify: fix check for one-shot watches before destroying them
has been removed from the -mm tree.  Its filename was
     inotify-fix-check-for-one-shot-watches-before-destroying-them.patch

This patch was dropped because it was merged into mainline or a subsystem tree

The current -mm tree may be found at http://userweb.kernel.org/~akpm/mmotm/

------------------------------------------------------
Subject: inotify: fix check for one-shot watches before destroying them
From: Ulisses Furquim <ulissesf@gmail.com>

As the IN_ONESHOT bit is never set when an event is sent we must check it
in the watch's mask and not in the event's mask.

Signed-off-by: Ulisses Furquim <ulissesf@gmail.com>
Reported-by: "Clem Taylor" <clem.taylor@gmail.com>
Tested-by: "Clem Taylor" <clem.taylor@gmail.com>
Cc: Amy Griffis <amy.griffis@hp.com>
Cc: Robert Love <rlove@google.com>
Cc: John McCutchan <ttb@tentacle.dhs.org>
Cc: <stable@kernel.org>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---

 fs/inotify_user.c |    2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff -puN fs/inotify_user.c~inotify-fix-check-for-one-shot-watches-before-destroying-them fs/inotify_user.c
--- a/fs/inotify_user.c~inotify-fix-check-for-one-shot-watches-before-destroying-them
+++ a/fs/inotify_user.c
@@ -283,7 +283,7 @@ static void inotify_dev_queue_event(stru
 	/* we can safely put the watch as we don't reference it while
 	 * generating the event
 	 */
-	if (mask & IN_IGNORED || mask & IN_ONESHOT)
+	if (mask & IN_IGNORED || w->mask & IN_ONESHOT)
 		put_inotify_watch(w); /* final put */
 
 	/* coalescing: drop this event if it is a dupe of the previous */
_

Patches currently in -mm which might be from ulissesf@gmail.com are

origin.patch

                 reply	other threads:[~2008-02-08 20:12 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=200802082011.m18KB1IP010084@imap1.linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=amy.griffis@hp.com \
    --cc=clem.taylor@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mm-commits@vger.kernel.org \
    --cc=rlove@google.com \
    --cc=stable@kernel.org \
    --cc=ttb@tentacle.dhs.org \
    --cc=ulissesf@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 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.