lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Date:	Wed, 28 Nov 2012 02:55:30 +0000
From:	"Yangbin (Robin)" <robin.yb@...wei.com>
To:	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"linux-fs@...r.kernel.org" <linux-fs@...r.kernel.org>
Subject: A question about proc file system

Hi all:

	I write a kernel module which make a dir and create a file in proc file system. 
I use proc_mkdir() and create_proc_entry() in init and use remove_proc_entry() in exit.
Now I got a problem during my test:
1. open terminal A, insmod and cd into the dir the module created in proc
2. open terminal B. rmmod and insmod angain.
Then I cannot see the file which should be created by the module, unless terminal A quit the dir.

This will be ok with regale file system like ext3, one teminal's operation will not affert others.
Is this a bug or not?

Regards
Robin

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ