From: Jeff Mahoney <jeffm@suse.com>
To: Edward Shishkin <edward.shishkin@gmail.com>
Cc: ReiserFS Mailing List <reiserfs-devel@vger.kernel.org>
Subject: Re: [PATCH] reiserfs: implement basic reiserfs 3.7
Date: Mon, 29 Nov 2010 15:10:39 -0500 [thread overview]
Message-ID: <4CF408BF.8080309@suse.com> (raw)
In-Reply-To: <4CF07C63.40408@gmail.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 11/26/2010 10:34 PM, Edward Shishkin wrote:
> Jeff Mahoney wrote:
>> This patch contains the basic implementation for reiserfs 3.7.
>> +int has_nonstandard_journal(struct reiserfs_super_block *rs)
>> +{
>> + return is_reiserfs_jr(rs) ||
>> + (is_reiserfs_3_7(rs) && rs->s_v1.s_journal.jp_journal_dev);
>> }
>>
>>
>
> Actually the function above is brain damaged.
> Journal is non-standard _iff_ it is "relocated" or has length (excluding
> journal
> header) different from 8192. So it can happen that a partition is "jr" (with
> REISER2FS_JR_SUPER_MAGIC_STRING), but has _standard_ journal.
Ok. I was under the impression that reiserfs_jr implied a nonstandard
journal. I guess that's mistaken. It seems to me that the only thing
wrong with the patch is the dev check and the name of the function.
Perhaps it should be may_have_nonstandard_journal(). The idea wasn't to
identify nonstandard journals but to extend the existing jr checks to
include 3.7 checks as well.
- -Jeff
- --
Jeff Mahoney
SUSE Labs
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.16 (GNU/Linux)
Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/
iEYEARECAAYFAkz0CL8ACgkQLPWxlyuTD7KpOgCdGkzb5GvbXXPEck1qx5AN1Qcg
xHgAn3KmHQGC/cxxoKrswuovhGR8Qq9f
=ZQMq
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2010-11-29 20:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-20 16:06 [PATCH] reiserfs: implement basic reiserfs 3.7 Jeff Mahoney
2010-11-27 3:34 ` Edward Shishkin
2010-11-29 20:10 ` Jeff Mahoney [this message]
2010-11-30 0:31 ` Edward Shishkin
2010-11-30 2:11 ` Edward Shishkin
2010-12-08 13:13 ` doiggl
2010-12-09 15:57 ` Jeff Mahoney
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=4CF408BF.8080309@suse.com \
--to=jeffm@suse.com \
--cc=edward.shishkin@gmail.com \
--cc=reiserfs-devel@vger.kernel.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 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.