From: Jan Kara <jack@suse.cz>
To: Eric Whitney <enwlinux@gmail.com>
Cc: linux-ext4@vger.kernel.org, tytso@mit.edu
Subject: Re: [PATCH 1/2] ext4: create function to read journal inode
Date: Thu, 22 Sep 2016 17:03:53 +0200 [thread overview]
Message-ID: <20160922150353.GA19971@quack2.suse.cz> (raw)
In-Reply-To: <20160922011450.GB27216@localhost.localdomain>
On Wed 21-09-16 21:14:50, Eric Whitney wrote:
> Factor out the code used in ext4_get_journal() to read a valid journal
> inode from storage, enabling its reuse in other functions.
>
> Signed-off-by: Eric Whitney <enwlinux@gmail.com>
Looks good. You can add:
Reviewed-by: Jan Kara <jack@suse.cz>
BTW: I didn't see PATCH 2/2?
Honza
> ---
> fs/ext4/super.c | 32 +++++++++++++++++++++++---------
> 1 file changed, 23 insertions(+), 9 deletions(-)
>
> diff --git a/fs/ext4/super.c b/fs/ext4/super.c
> index 50912cc..4b0ca25 100644
> --- a/fs/ext4/super.c
> +++ b/fs/ext4/super.c
> @@ -78,6 +78,8 @@ static int ext4_feature_set_ok(struct super_block *sb, int readonly);
> static void ext4_destroy_lazyinit_thread(void);
> static void ext4_unregister_li_request(struct super_block *sb);
> static void ext4_clear_request_list(void);
> +static struct inode *ext4_get_journal_inode(struct super_block *sb,
> + unsigned int journal_inum);
>
> /*
> * Lock ordering
> @@ -4237,18 +4239,16 @@ static void ext4_init_journal_params(struct super_block *sb, journal_t *journal)
> write_unlock(&journal->j_state_lock);
> }
>
> -static journal_t *ext4_get_journal(struct super_block *sb,
> - unsigned int journal_inum)
> +static struct inode *ext4_get_journal_inode(struct super_block *sb,
> + unsigned int journal_inum)
> {
> struct inode *journal_inode;
> - journal_t *journal;
> -
> - BUG_ON(!ext4_has_feature_journal(sb));
> -
> - /* First, test for the existence of a valid inode on disk. Bad
> - * things happen if we iget() an unused inode, as the subsequent
> - * iput() will try to delete it. */
>
> + /*
> + * Test for the existence of a valid inode on disk. Bad things
> + * happen if we iget() an unused inode, as the subsequent iput()
> + * will try to delete it.
> + */
> journal_inode = ext4_iget(sb, journal_inum);
> if (IS_ERR(journal_inode)) {
> ext4_msg(sb, KERN_ERR, "no journal found");
> @@ -4268,6 +4268,20 @@ static journal_t *ext4_get_journal(struct super_block *sb,
> iput(journal_inode);
> return NULL;
> }
> + return journal_inode;
> +}
> +
> +static journal_t *ext4_get_journal(struct super_block *sb,
> + unsigned int journal_inum)
> +{
> + struct inode *journal_inode;
> + journal_t *journal;
> +
> + BUG_ON(!ext4_has_feature_journal(sb));
> +
> + journal_inode = ext4_get_journal_inode(sb, journal_inum);
> + if (!journal_inode)
> + return NULL;
>
> journal = jbd2_journal_init_inode(journal_inode);
> if (!journal) {
> --
> 2.1.4
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
--
Jan Kara <jack@suse.com>
SUSE Labs, CR
next prev parent reply other threads:[~2016-09-22 15:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-22 1:14 [PATCH 1/2] ext4: create function to read journal inode Eric Whitney
2016-09-22 15:03 ` Jan Kara [this message]
2016-09-22 16:38 ` Eric Whitney
2016-09-30 6:11 ` Theodore Ts'o
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=20160922150353.GA19971@quack2.suse.cz \
--to=jack@suse.cz \
--cc=enwlinux@gmail.com \
--cc=linux-ext4@vger.kernel.org \
--cc=tytso@mit.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;
as well as URLs for NNTP newsgroup(s).