From: Mark Fasheh <mark.fasheh@oracle.com>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] [PATCH]2.6 fixes in journal.c
Date: Mon Mar 1 16:06:54 2004 [thread overview]
Message-ID: <20040301220643.GT1421@ca-server1.us.oracle.com> (raw)
In-Reply-To: <20040301165447.GA16000@penguin.co.intel.com>
On Mon, Mar 01, 2004 at 08:54:47AM -0800, Rusty Lynch wrote:
> Here is the same patch cut against the new svn tree.
>
>
> Index: src/journal.c
> ===================================================================
> --- src/journal.c (revision 738)
> +++ src/journal.c (working copy)
> @@ -656,7 +656,7 @@
> break;
>
> case OCFS_JOURNAL_ACCESS_WRITE:
> - status = journal_get_write_access(handle->k_handle, bh);
> + status = journal_get_write_access(handle->k_handle, bh, NULL);
> break;
Can we put an #if LINUX_VERSION_CODE around that one please? Passing NULL in
2.6 for the credits argument is fine.
>
> default:
> @@ -899,7 +899,7 @@
> OCFS_BH_PUT_DATA(bh);
> fe = NULL;
> #if LINUX_VERSION_CODE >= KERNEL_VERSION(2,6,0)
> - inode = ocfs_iget (sb, &args);
> + inode = ocfs_iget (osb->sb, &args);
> #else
> inode = ocfs_get_inode_from_offset(osb, args.offset, bh);
> #endif
> @@ -935,9 +935,13 @@
>
> LOG_TRACE_STR("Returned from journal_init_inode");
> LOG_TRACE_ARGS("k_journal->j_maxlen = %u\n", k_journal->j_maxlen);
> +#if LINUX_VERSION_CODE >= KERNEL_VERSION(2,6,0)
> + k_journal->j_commit_interval = OCFS_DEFAULT_COMMIT_INTERVAL;
> +#else
> lock_journal(k_journal);
> k_journal->j_commit_interval = OCFS_DEFAULT_COMMIT_INTERVAL;
> unlock_journal(k_journal);
> +#endif
Ok, you can actually just remove that lock_journal/unlock_journal pair. At
that point in the JBD init cycle, we don't have to worry about protecting
that variable.
The rest of the patch looks good, so if you could just fix those two things,
I'll commit.
--Mark
--
Mark Fasheh
Software Developer, Oracle Corp
mark.fasheh@oracle.com
next prev parent reply other threads:[~2004-03-01 16:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-26 20:16 [Ocfs2-devel] [PATCH]2.6 fixes in journal.c Rusty Lynch
2004-03-01 10:54 ` Rusty Lynch
2004-03-01 16:06 ` Mark Fasheh [this message]
2004-03-01 16:36 ` Rusty Lynch
2004-03-01 17:43 ` Mark Fasheh
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=20040301220643.GT1421@ca-server1.us.oracle.com \
--to=mark.fasheh@oracle.com \
--cc=ocfs2-devel@oss.oracle.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.