From: hooanon05@yahoo.co.jp
To: ttb@tentacle.dhs.org, rml@novell.com
Cc: linux-kernel@vger.kernel.org
Subject: lock free inotify_ioctl()?
Date: Wed, 22 Oct 2008 22:39:30 +0900 [thread overview]
Message-ID: <7353.1224682770@jrobl> (raw)
Hello John McCutchan and Robert Love,
I have a question about inotify_ioctl().
I am investigating if a user process misses the inotify event or gets
wrong event by ioctl(fd, FIONREAD, &pending) in linux-2.6.27, and found
it doesn't acquire dev->ev_mutex lock before accessing dev->queue_size.
In SMP system, is it safe and sure too?
Is the mutex lock unnecessary?
Junjiro R. Okajima
reply other threads:[~2008-10-22 13:39 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=7353.1224682770@jrobl \
--to=hooanon05@yahoo.co.jp \
--cc=linux-kernel@vger.kernel.org \
--cc=rml@novell.com \
--cc=ttb@tentacle.dhs.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.