From: Christoph Hellwig <hch@infradead.org>
To: Marek Szyprowski <march@staszic.waw.pl>
Cc: linux-fsdevel@vger.kernel.org,
Sven Luther <sven.luther@wanadoo.fr>,
Christoph Hellwig <hch@lst.de>
Subject: Re: [PATCH] ASFS filesystem driver, kernel 2.4.xx and 2.6.x
Date: Mon, 7 Jun 2004 10:56:25 +0100 [thread overview]
Message-ID: <20040607095625.GA18710@infradead.org> (raw)
In-Reply-To: <yam9651.1769.576891856@boss.staszic.waw.pl>
- asfs_fs.h, asfs_fs_i.h and asfs_fs_sb.h don't belong to include/linux
but fs/asfs (and get saner names while you're at it)
- there's a bunch of files completely under ifdef CONFIG_ASFS_RW, just
make them depend on that in the makefile instead using
asfs-y += dir.o ...
asfs-$(CONFIG_ASFS_RW) += adminspace.o bitfuncs.o ...
- names like setfreeblocks are a little too generic, please give them
asfs_ prefixes
- you probably want to replace the routines in bitfuncs.c with usage of
linux-native routines from bitops.h like find_first_bit(), etc wherever
possible
- asfs_parse_options should use lib/parser.c helpers
- in asfs_fill_super you're leaking if d_alloc_root fails
- you're using lock_super for a lot of internal synchronization, but you
should implement your own locking instead and document what each lock
protects.
- the filp->f_count checks in ->open and ->close are totally bogus
- asfs_file_release looks very fishy. Why do you set ->datemodified
on close, not on actual modification?
- the whole handling of ->modified and reading the object from disk
again when you want to write it back looks bogus. Why don't you
- ->create, ->mkdir and ->mknod seem to share most of them code, shouldn't
you use a common subroutine? Mayube dito for ->unlink and ->rmdir
- please call asfs_delete asfs_unlink to match the method name.
- this whole rececycled bin stuff makes me sick. Where is that handling
encoded in the ondisk format? Can't you just do normal unix-style unlinks?
next prev parent reply other threads:[~2004-06-07 9:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-04 9:39 [PATCH] ASFS filesystem driver, kernel 2.4.xx and 2.6.x Marek Szyprowski
2004-06-07 9:56 ` Christoph Hellwig [this message]
2004-06-07 20:42 ` Marek Szyprowski
2004-06-26 10:21 ` Marek Szyprowski
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=20040607095625.GA18710@infradead.org \
--to=hch@infradead.org \
--cc=hch@lst.de \
--cc=linux-fsdevel@vger.kernel.org \
--cc=march@staszic.waw.pl \
--cc=sven.luther@wanadoo.fr \
/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;
as well as URLs for NNTP newsgroup(s).