public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Jones <davej@redhat.com>
To: "Theodore Ts'o" <tytso@mit.edu>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: ext4: cache all of an extent tree's leaf block upon reading
Date: Thu, 5 Sep 2013 11:14:57 -0400	[thread overview]
Message-ID: <20130905151457.GA24177@redhat.com> (raw)
In-Reply-To: <20130905145334.GB23661@thunk.org>

On Thu, Sep 05, 2013 at 10:53:34AM -0400, Theodore Ts'o wrote:

 > > ext4_es_store_pblock or's the pblk with the existing contents of the struct member.
 > > (albeit masked with ES_MASK)
 > > 
 > > Should there be a 
 > > 
 > > 	newes.es_pblk = 0;
 > > 
 > > up there too ?
 > 
 > The next line after ext4_es_store_pblock() is:
 > 
 >         ext4_es_store_status(&newes, status);
 > 
 > This will set remaining ES_WRITTEN | ES_UNWRITTEN... bits.
 > 
 > So the only reason to add a line explicitly setting es_pblk to zero
 > would be to suppress a warning from some insufficiently smart static
 > code analysis tool.  I didn't see a warning from gcc, but it's
 > possible that this is something which is causing Coverity or some
 > other code scanner heartburn.

Yep, that's what picked it up.  I'll add a 'not a bug' annotation to stop
it getting flagged again.  This was the only ext* issue that Coverity
picked up from yesterdays merge btw, which I guess is good news ;)

	Dave


  reply	other threads:[~2013-09-05 15:15 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20130905013848.42DD7660EE1@gitolite.kernel.org>
2013-09-05 14:37 ` ext4: cache all of an extent tree's leaf block upon reading Dave Jones
2013-09-05 14:53   ` Theodore Ts'o
2013-09-05 15:14     ` Dave Jones [this message]
2013-09-05 19:08       ` 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=20130905151457.GA24177@redhat.com \
    --to=davej@redhat.com \
    --cc=linux-kernel@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