From: "Theodore Y. Ts'o" <tytso@MIT.EDU>
To: Alexander Viro <viro@math.psu.edu>
Cc: linux-kernel@vger.kernel.org, "Theodore Y. Ts'o" <tytso@MIT.EDU>
Subject: Re: [CFT][RFC] ext2_new_inode() fixes and cleanup
Date: Thu, 30 Nov 2000 18:18:20 -0500 [thread overview]
Message-ID: <200011302318.SAA17390@tsx-prime.MIT.EDU> (raw)
In-Reply-To: Alexander Viro's message of Thu, 30 Nov 2000 17:13:27 -0500 (EST), <Pine.GSO.4.21.0011301652130.21891-100000@weyl.math.psu.edu>
Date: Thu, 30 Nov 2000 17:13:27 -0500 (EST)
From: Alexander Viro <viro@math.psu.edu>
* search for appropriate cylinder group had been taken out of the
ext2_new_inode() into helper functions - find_cg_dir(sb, parent_group) and
find_cg_other(sb, parent_group). Bug caught by Daniel (wrong bh being
dirtied when we update the free inodes counter) - fixed.
* ext2_new_inode() returns error values via ERR_PTR(). Callers
updated, the third argument gone.
* load_inode_bitmap() returns bh of the bitmap instead of the slot
number. Callers updated.
* code in ext2_new_inode() straightened up. Nothing spectacular,
but it became more readable now...
* all callers of ext2_new_inode() in namei.c are passing correct
mode (including ext2_mkdir(), etc.) instead of setting ->i_mode by hands
afterwards.
It's _not_ likely that the whole thing will go into 2.4.0. Moreover,
if it ever will go, it will go in pieces. I will post the splitup for
review, indeed. Right now I'm just asking to help with testing the
thing and with reading the resulting code. Hopefully, it's easier to
read than it used to be.
The code is definitely more readable with these changes. For 2.4.0 at
this point my bias is towards a simple 1-2 line fix for Daniel's bug,
and save the cleanups for post 2.4.
Ted, if you could look through the code and comment on it... I would
be extremely grateful. I can send you a splitup of the patch if that will be
more convenient for you - just tell.
If you could send me the split up, I'd appreciate it, as it'll make it
easier to find any subtle bugs. I certainly like the general way you've
cleaned up the interfaces and factored out the code.
Many thanks,
- Ted
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2000-11-30 23:49 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-30 22:13 Alexander Viro
2000-11-30 23:18 ` Theodore Y. Ts'o [this message]
2000-12-01 12:55 ` Alexander Viro
2000-12-01 8:27 ` Andreas Dilger
2000-12-01 11:28 ` Alexander Viro
2001-01-02 23:33 ` [RFC] ext2_new_block() behaviour Alexander Viro
2001-01-03 1:47 ` Andreas Dilger
2001-01-03 3:37 ` Alexander Viro
2001-01-03 12:16 ` [Ext2-devel] " Stephen C. Tweedie
2001-01-03 16:12 ` Alexander Viro
2001-01-04 4:42 ` Oliver Xymoron
2001-01-04 5:06 ` Alexander Viro
2001-01-04 5:15 ` Oliver Xymoron
2001-01-04 22:04 ` Stephen C. Tweedie
2001-01-04 22:31 ` Alexander Viro
2001-01-04 20:48 ` -bird tree " Marcelo Tosatti
2001-01-04 23:25 ` Stephen C. Tweedie
2001-01-05 7:06 ` Andreas Dilger
2001-01-05 11:29 ` Stephen C. Tweedie
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=200011302318.SAA17390@tsx-prime.MIT.EDU \
--to=tytso@mit.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@math.psu.edu \
/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
all inboxes | Powered by JetHome®