From: Carlos Maiolino <cmaiolino@redhat.com>
To: linux-ext4@vger.kernel.org
Subject: Re: [PATCH] ext4: ext4_bread usage audit
Date: Wed, 26 Sep 2012 11:14:17 -0300 [thread overview]
Message-ID: <20120926141417.GA3485@andromeda.usersys.redhat.com> (raw)
In-Reply-To: <50627B01.6070306@redhat.com>
On Tue, Sep 25, 2012 at 10:48:17PM -0500, Eric Sandeen wrote:
> On 9/25/12 10:42 PM, Theodore Ts'o wrote:
> > On Mon, Sep 24, 2012 at 03:41:40PM -0300, Carlos Maiolino wrote:
> >>
> >> Some ext4_bread callers do not needed any changes either because they already
> >> had its own hole detector paths or because these are deprecaded (like
> >> dx_show_entries)
> >
> > BTW, dx_show entries isn't really deprecated; is debugging code which
> > is usually not compiled in, but it does get used from time to time by
> > developers who are debugging the directory hash tree code...
> >
> > So having it show the holes by printing a note that there _was_ a
> > whole is probably a good thing from a debugging point of view...
>
> I think what Carlos meant is that there are no callers in the tree...
> so even with debug options, it's not used. It takes a custom patch...
> Does it still work? :)
>
Yeah, that's what I meant, no callers of dx_show_entries() even with debug
enabled.
In regards to the coding style of if conditionals, I just followed the coding
style of most places in the code, I also changed some of the if conditionals to
match the rest of the code. i.e.:
if(!(bh = ext4_bread())) {
do_something();
}
if you take a look at the code, most if conditionals regarding the calls to
ext4_bread() are in the above coding style. I just followed it, but, I'm not
against change that to another one, but agree the above looks better and save
some code lines
> -Eric
>
> > - Ted
> > --
> > 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
> >
>
> --
> 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
--
--Carlos
next prev parent reply other threads:[~2012-09-26 14:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-24 18:41 [PATCH] ext4: ext4_bread usage audit Carlos Maiolino
2012-09-25 6:38 ` Andreas Dilger
2012-09-26 3:42 ` Theodore Ts'o
2012-09-26 3:48 ` Eric Sandeen
2012-09-26 14:14 ` Carlos Maiolino [this message]
2012-09-27 13:29 ` Andreas Dilger
2012-09-27 13:20 ` 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=20120926141417.GA3485@andromeda.usersys.redhat.com \
--to=cmaiolino@redhat.com \
--cc=linux-ext4@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.