From: Greg KH <greg@kroah.com>
To: Robert Love <rml@novell.com>
Cc: John McCutchan <ttb@tentacle.dhs.org>, linux-kernel@vger.kernel.org
Subject: Re: [patch] inotify: add FIONREAD support
Date: Fri, 5 Nov 2004 16:47:57 -0800 [thread overview]
Message-ID: <20041106004755.GA23981@kroah.com> (raw)
In-Reply-To: <1099696444.6034.266.camel@localhost>
On Fri, Nov 05, 2004 at 06:14:04PM -0500, Robert Love wrote:
> John,
>
> There are a handful of "standard" file ioctl's (FIBMAP, FIONREAD,
> FIGETBSZ, etc.). We don't have to implement any of them, but FIONREAD
> is actually pretty useful: It tells you how many bytes are available on
> the fd.
Nice idea.
> + case FIONREAD:
> + bytes = dev->event_count * sizeof (struct inotify_event);
> + return put_user(bytes, (int *) p);
But sparse will spit out warnings with code like this :(
Actually, the whole inotify patch probably isn't sparse clean...
thanks,
greg k-h
next prev parent reply other threads:[~2004-11-06 0:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-05 23:14 [patch] inotify: add FIONREAD support Robert Love
2004-11-06 0:47 ` Greg KH [this message]
2004-11-06 0:57 ` Robert Love
2004-11-06 1:00 ` Robert Love
2004-11-07 23:41 ` John McCutchan
2004-11-06 1:00 ` Greg KH
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=20041106004755.GA23981@kroah.com \
--to=greg@kroah.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox