From: Theodore Tso <tytso@MIT.EDU>
To: Alexey Zaytsev <alexey.zaytsev@gmail.com>
Cc: linux-ext4@vger.kernel.org, linux-fsdev@vger.kernel.org,
Rik van Riel <riel@surriel.com>
Subject: Re: Mentor for a GSoC application wanted (Online ext2/3 filesystem checker)
Date: Fri, 18 Apr 2008 21:29:52 -0400 [thread overview]
Message-ID: <20080419012952.GE25797@mit.edu> (raw)
In-Reply-To: <f19298770804180720w2e72b821j95b709c1dd1b1c25@mail.gmail.com>
On Fri, Apr 18, 2008 at 06:20:14PM +0400, Alexey Zaytsev wrote:
> Hello, guys.
>
> It seems like the Linux-fountation was not able to find a mentor for
> my project. If somebody is willing to mentor this project through the
> Google Summer of Code, please contact Rik and me now, as little
> time is left.
>
> A link to the application:
> http://rom.etherboot.org/share/xl0/gsoc2008/application-linux-foundation.txt
Hi Alexey,
I really don't think your project is likely to be successful given the
3 month timeframe of a GSoC. At least not without a mentor spending
vast amounts of time educating you about how things works within ext2
and e2fsck. Even given some broad hints about problems that you need
to address, you still have not addressed how you will solve
fundamental race conditions resulting from trying to read the multiple
blocks scattered all over the disk which comprise allocation bitmap
blocks while allocations might be taking place, for example.
Your approach of monitoring writes to the buffer cache for metadata
writes is completely busted; suppose the kernel modifies block #12345
in the filesystem; how do you know what that means? Could that be an
indirect block? If so, to which inode does it belong? If all you are
doing is monitoring metadata blocks, you would have no idea! The fact
that it apparently didn't even occur to you that this might be a
show-stopping problem scares the heck out of me. It leads me to
believe that this project is very likely to fail, and/or will require
vast amounts of time from the mentor. Unfortunately, the former is
something that I just don't have this summer.
Regards,
- Ted
next prev parent reply other threads:[~2008-04-19 1:31 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-18 14:20 Mentor for a GSoC application wanted (Online ext2/3 filesystem checker) Alexey Zaytsev
2008-04-19 1:29 ` Theodore Tso [this message]
2008-04-19 9:44 ` Alexey Zaytsev
2008-04-19 18:56 ` Theodore Tso
2008-04-19 19:07 ` Eric Sandeen
2008-04-19 22:04 ` Theodore Tso
2008-04-20 1:24 ` Eric Sandeen
2008-04-20 23:30 ` Andi Kleen
2008-04-20 23:42 ` Jamie Lokier
2008-04-21 8:01 ` Andi Kleen
2008-04-21 8:01 ` Andi Kleen
2008-04-21 11:51 ` Jamie Lokier
2008-04-21 17:29 ` Ricardo M. Correia
2008-04-21 17:40 ` Andi Kleen
2008-04-21 18:27 ` Ricardo M. Correia
2008-04-22 14:48 ` Jamie Lokier
2008-04-21 18:15 ` Ric Wheeler
2008-04-21 18:25 ` Eric Sandeen
2008-04-21 18:44 ` Ric Wheeler
2008-04-21 18:58 ` Matthew Wilcox
2008-04-21 19:11 ` Ric Wheeler
2008-04-21 0:27 ` Alexey Zaytsev
2008-04-21 9:45 ` Andi Kleen
2008-04-22 16:54 ` Peter Teoh
2008-04-22 17:02 ` Eric Sandeen
2008-04-22 23:37 ` Andreas Dilger
2008-04-23 0:52 ` Eric Sandeen
[not found] ` <480E4950.1090300@oracle.com>
[not found] ` <804dabb00804221633g1f61029dh7b27737134fc0b7a@mail.gmail.com>
[not found] ` <480E7954.9090408@oracle.com>
2008-04-23 1:02 ` Peter Teoh
2008-04-20 23:37 ` Andi Kleen
2008-04-21 2:33 ` Theodore Tso
2008-04-21 14:43 ` Andi Kleen
2008-04-21 0:23 ` Alexey Zaytsev
2008-04-21 12:53 ` Theodore Tso
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=20080419012952.GE25797@mit.edu \
--to=tytso@mit.edu \
--cc=alexey.zaytsev@gmail.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdev@vger.kernel.org \
--cc=riel@surriel.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.