Date: Fri, 14 Jun 2013 09:26:49 +0800
From: majianpeng <majianpeng@gmail.com>
To: john <john@johnmccutchan.com>, rlove <rlove@rlove.org>,
        eparis <eparis@parisplace.org>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Reply-To: majianpeng <majianpeng@gmail.com>
Subject: [BUG] Using inotify on /proc/partitoins
Mime-Version: 1.0
Message-ID: <201306140926455537935@gmail.com>
Content-Type: text/plain;
	charset="gb2312"
Sender: linux-kernel-owner@vger.kernel.org
Content-Transfer-Encoding: 8bit
Content-Length: 1190
Lines: 38

Hi all,
     I wanted to monitor /proc/partitions using inotify.Although now i know it can't catch the event of write.
But for read,it can't catch. The code is:
int main()
{
	int fd = inotify_init();
	int wd;
	char buff[4096];
	int ret;
	if (fd < 0)
		perror("inotify_init error\n");

	wd = inotify_add_watch(fd, "/proc/partitions", IN_ACCESS);
	if (wd < 0)
		perror("inotify_add_watch error\n");

	
	ret = read(fd, buff, 4096);
	if (ret < 0)
		perror("read error\n");
	else
		printf("buff %s\n", buff);
	return 0;
}

But when i call 'cat /proc/partitions',the program can't return.
So i added some message in kernel in order to find the reason.
In procfs for some files, the inode used this method to alloc.
proc_lookup-->proc_lookup_de--->proc_get_inode-->new_inode_pseudo
In new_inode_pseudo, it will alloc new inode so every open-operation procfs will alloc new inode.
So inotify can't work.

I think it should add a flag which indicate file can't support inotify.Although  there are a few files in procfs.


Thanks!
Jianpeng
????{.n?+???????+%?????ݶ??w??{.n?+????{??G?????{ay?ʇڙ?,j??f???h?????????z_??(?階?ݢj"???m??????G????????????&???~???iO???z??v?^?m????????????I?