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-prev] [thread-next>] [day] [month] [year] [list]
Date:	Tue, 23 Oct 2012 12:21:23 +0900
From:	Jaegeuk Kim <jaegeuk.kim@...sung.com>
To:	'Greg KH' <gregkh@...uxfoundation.org>
Cc:	linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org,
	viro@...iv.linux.org.uk, arnd@...db.de, tytso@....edu,
	chur.lee@...sung.com, cm224.lee@...sung.com,
	jooyoung.hwang@...sung.com
Subject: RE: [PATCH 16/16 v2] f2fs: update Kconfig and Makefile

> On Tue, Oct 23, 2012 at 11:33:28AM +0900, Jaegeuk Kim wrote:
> > +config F2FS_STAT_FS
> > +	bool "F2FS Status Information"
> > +	depends on F2FS_FS
> > +	default y
> > +	help
> > +	  /proc/fs/f2fs/ contains information about partitions mounted as f2fs.
> > +	  For each partition, a corresponding directory, named as its device
> > +	  name, is provided with the following proc entries.
> > +
> > +	  f2fs_stat	major file system information managed by f2fs currently
> > +	  f2fs_sit_stat	average SIT information about whole segments
> > +	  f2fs_mem_stat	current memory footprint consumed by f2fs
> > +
> > +	  e.g., in /proc/fs/f2fs/sdb1/
> 
> Again, I will point out that this should either be in debugfs, or in
> /sys/fs/ but it should NOT be in /proc/ at all.
> 
> If you need help, I will be glad to do this conversion, just let me know
> and I'll send you a patch on top of this series that moves these entries
> into debugfs, which is where I think they really belong.

Ok, please. :)
I really appreciate your kindness.

> 
> thanks,
> 
> greg k-h

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ