From: "Vladimir 'φ-coder/phcoder' Serbinenko" <phcoder@gmail.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Automated FS tests. Plans about untested FS: AFS, SFS, Minix3
Date: Thu, 10 Nov 2011 22:33:45 +0100 [thread overview]
Message-ID: <4EBC4339.6090803@gmail.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1270 bytes --]
Some of you have probably noticed the series of commits fixing different
FS bugs limitations and missing features. The master of the ball was the
attached script in different slight modifications. UFS1 and UFS2 are
commented out since during the last test I had a kernel with only ro UFS
support but UFS and UFS2 were both tested. I hope some day to clean up
the script and commit it as e.g. "make fscheck", is anybody willing to
help? For 3 filesystems: AFS, SFS and Minix3 I couldn't find any driver
available under GNU/Linux. Considering the amount of fixes for other
FSes with similar usage, I except these FS have issues, especially SFS,
since unlike the 2 others which are minor modifications of BFS resp
minix2 it doesn't share any code with any other FS. The inability to
test those FS is a serious drawback especially if any changes affecting
all the filesystems need to be made. We all know that such condition can
lead to code quality degradation and eventual removal of concerned FS in
a long run. So could anyone supply the missing tests? They have to be
runnable under GNU/Linux. Supporting more platforms is a plus but not a
requirement since it's mainly quality insurance tool.
--
Regards
Vladimir 'φ-coder/phcoder' Serbinenko
[-- Attachment #1.2: fstest.sh --]
[-- Type: application/x-shellscript, Size: 16458 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 294 bytes --]
next reply other threads:[~2011-11-10 21:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-10 21:33 Vladimir 'φ-coder/phcoder' Serbinenko [this message]
2011-11-11 12:52 ` Automated FS tests. Plans about untested FS: AFS, SFS, Minix3 Vladimir 'φ-coder/phcoder' Serbinenko
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=4EBC4339.6090803@gmail.com \
--to=phcoder@gmail.com \
--cc=grub-devel@gnu.org \
/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).