linux-kernel - Re: New filesystem for Linux kernel

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, 24 Feb 2009 22:57:40 +0900
From:	hooanon05@...oo.co.jp
To:	Tarkan Erimer <tarkan.erimer@...knet.net.tr>
Cc:	Miklos Szeredi <miklos@...redi.hu>, tomas@...x.org,
	akpm@...ux-foundation.org, linux-fsdevel@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: Re: New filesystem for Linux kernel 


Tarkan Erimer:
> I think there is a misunderstanding or confusion about merging the code 
> into the mainline. You needn't to drop some functionality/features to 
> make your code small and to make it reviewed by mergers. You have to 
> separate (Core FS functions, features etc.) your code into small pieces. 
> So that, mergers will look, for first, your core FS functionality code 
> to see that it *_breaks_* or *_touches_* any _*other areas of the 
> kernel*_. If everything goes well, your main Core FS functionality code 
> will be merged into the mainline. After that, you can send your 
> feature/functionality codes one by one.

Tarkan, thank you for your advise.
Actually I broke functions and files into small pieces. Additionally I
applied CONFIG_AUFS_* conditions in fs/aufs/Makefile. When you review
aufs source files, I'd suggest you to read in this order.

aufs-y := module.o sbinfo.o super.o branch.o xino.o sysaufs.o opts.o \
	wkq.o vfsub.o dcsub.o \
	cpup.o whout.o plink.o wbr_policy.o \
	dinfo.o dentry.o \
	finfo.o file.o f_op.o \
	dir.o vdir.o \
	iinfo.o inode.o i_op.o i_op_add.o i_op_del.o i_op_ren.o \
	ioctl.o
aufs-$(CONFIG_SYSFS) += sysfs.o
aufs-$(CONFIG_AUFS_BDEV_LOOP) += loop.o
aufs-$(CONFIG_AUFS_HINOTIFY) += hinotify.o
aufs-$(CONFIG_AUFS_DEBUG) += debug.o
aufs-$(CONFIG_AUFS_MAGIC_SYSRQ) += sysrq.o

If I am still misunderstanding, please let me know.

Thank you
J. R. Okajima
--
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/