public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Heinrich Schuchardt <xypron.glpk@gmx.de>
To: Justin Maggard <jmaggard10@gmail.com>
Cc: linux-kernel@vger.kernel.org, eparis@redhat.com,
	LinoSanfilippo@gmx.de, tzvetanc@commtouch.com
Subject: Re: fanotify: fix support of large files
Date: Mon, 22 Apr 2013 20:49:20 +0200	[thread overview]
Message-ID: <51758630.6000003@gmx.de> (raw)
In-Reply-To: <CAKgsxVT3_ge2vxcGWzy6NJYPEGwB1Wbw2eE7a=JtWWBb8o4XVg@mail.gmail.com>

Hello Justin,

I downloaded the example,
http://www.lanedo.com/~aleksander/fanotify/fanotify-example.c
compiled it without modification
$ gcc fanotify-example.c -o fanotify-example
and started the executable. In a separate windows I executed
truncate -s 2048m 2048m

This is the output of the first window:
$ sudo ./fanotify-example /home/user/temp/
Started monitoring directory '/home/user/temp/'...
Received event in path '/home/user/temp/2048m' pid=3659 (truncate):
         FAN_OPEN
Received event in path '/home/user/temp/2048m' pid=3659 (truncate):
         FAN_CLOSE_WRITE

$ uname -a
Linux family2 3.8.0 #1 SMP Fri Feb 22 22:07:58 CET 2013 i686 GNU/Linux

To reproduce your problem, could you, please, provide the Linux 
configuration file (look in your /boot directory) and a link to the 
source of the Linux kernel version you use. Then I can use your 
configuration file to compile that kernel version.

Best regards

Heinrich Schuchardt

On 19.04.2013 21:23, Justin Maggard wrote:
> On Sat, Apr 13, 2013 at 4:54 AM, Heinrich Schuchardt<xypron.glpk@gmx.de>  wrote:
>> Dear Justin,
>>
>> looking at the example at
>> http://www.lanedo.com/~aleksander/fanotify/fanotify-example.c
>> the large file support is enabled by passing O_LARGEFILE to fanotify_init:
>>
>>    if ((fanotify_fd = fanotify_init (FAN_CLOEXEC,
>>                                      O_RDONLY | O_CLOEXEC | O_LARGEFILE))<
>> 0)
>>
>> Could you, please, check if this solves your issue.
>>
>> (I am resending this message because HTML was rejected by
>> linux-kernel@vger.kernel.org).
>>
>> Best regards
>>
>> Heinrich Schuchardt
>>
>
> No, unfortunately that doesn't help.  I slightly modifed
> fanotify-example.c to call perror() when read() fails, and here's the
> output:
>
> jmaggard@jmaggard-W520:~/fanotify-test$ sudo ./fanotify-example .&
> [1] 7248
> jmaggard@jmaggard-W520:~/fanotify-test$ Started monitoring directory '.'...
> truncate -s 2047m 2047m
> Received event in path '/home/jmaggard/fanotify-test/2047m' pid=7250 (unknown):
> FAN_OPEN
> FAN_CLOSE_WRITE
> jmaggard@jmaggard-W520:~/fanotify-test$ truncate -s 2048m 2048m
> read: Value too large for defined data type
>
> -Justin
>


  reply	other threads:[~2013-04-22 18:49 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-14 17:29 [PATCH] fanotify: fix support of large files Justin Maggard
2013-04-13 11:54 ` Heinrich Schuchardt
2013-04-19 19:23   ` Justin Maggard
2013-04-22 18:49     ` Heinrich Schuchardt [this message]
2013-07-11 22:10       ` Justin Maggard

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=51758630.6000003@gmx.de \
    --to=xypron.glpk@gmx.de \
    --cc=LinoSanfilippo@gmx.de \
    --cc=eparis@redhat.com \
    --cc=jmaggard10@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tzvetanc@commtouch.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