From: "Stephen C. Tweedie" <sct@redhat.com>
To: Andrew Morton <akpm@digeo.com>
Cc: ext3 users list <ext3-users@redhat.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
linux-fsdevel@vger.kernel.org, Stephen Tweedie <sct@redhat.com>
Subject: Re: [Patch] ext3_journal_stop inode access
Date: 20 Mar 2003 22:18:50 +0000 [thread overview]
Message-ID: <1048198730.2491.626.camel@sisko.scot.redhat.com> (raw)
In-Reply-To: <20030320161230.3c4e0f47.akpm@digeo.com>
Hi,On Fri, 2003-03-21 at 00:12, Andrew Morton wrote:
> > Well, there's still the
> > if (err)
> > __ext3_std_error(inode->i_sb, where, err);
> > case in ext3_journal_stop() to worry about
>
> We already have that.
Only if we fix the underlying problem --- I was only pointing out that
even if we drop the setting of s_dirt entirely, which was what we were
trying to fix, we can't avoid having to find the sb.
> But I'm not particularly fussed either way - it will only be 100-200 bytes of
> code saved.
Yep, but there are probably other places we can find where we can avoid
passing the sb around too if we have the back-pointer. I guess it makes
sense to go ahead with that.
> The journal and the superblock have a definite one-to-one relationship - I think the
> backpointer makes sense. But whatever - I'll let you flip that coin.
OK, go for it and I'll merge for 2.4.
Cheers,
Stephen
prev parent reply other threads:[~2003-03-20 22:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1048185825.2491.386.camel@sisko.scot.redhat.com>
2003-03-20 21:15 ` [Patch] ext3_journal_stop inode access Andrew Morton
2003-03-20 21:36 ` Stephen C. Tweedie
2003-03-21 0:12 ` Andrew Morton
2003-03-20 22:18 ` Stephen C. Tweedie [this message]
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=1048198730.2491.626.camel@sisko.scot.redhat.com \
--to=sct@redhat.com \
--cc=akpm@digeo.com \
--cc=ext3-users@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@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 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).