All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dan Carpenter <dan.carpenter@oracle.com>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] ocfs2: fix sparse file & data ordering issue in direct io
Date: Wed, 9 Mar 2016 13:25:05 +0300	[thread overview]
Message-ID: <20160309102505.GA15030@mwanda> (raw)

Hello Ryan Ding,

The patch fbe25fb91af5: "ocfs2: fix sparse file & data ordering issue
in direct io" from Feb 25, 2016, leads to the following static
checker warning:

	fs/ocfs2/aops.c:2242 ocfs2_dio_get_block()
	error: potentially dereferencing uninitialized 'wc'.

fs/ocfs2/aops.c
  2235  
  2236          ret = ocfs2_write_begin_nolock(inode->i_mapping, pos, len,
  2237                                         OCFS2_WRITE_DIRECT, NULL,
  2238                                         (void **)&wc, di_bh, NULL);
                                               ^^^^^^^^^^^^

See commit 5cffff9e2986 ('ocfs2: Fix ocfs2_page_mkwrite()') for an
explanation why a zero return here does not imply that "wc" has been
initialized.

  2239          if (ret) {
  2240                  mlog_errno(ret);
  2241                  goto unlock;
  2242          }
  2243  
  2244          desc = &wc->w_desc[0];
  2245  
  2246          p_blkno = ocfs2_clusters_to_blocks(inode->i_sb, desc->c_phys);

regards,
dan carpenter

             reply	other threads:[~2016-03-09 10:25 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-09 10:25 Dan Carpenter [this message]
2016-11-15 10:33 ` [Ocfs2-devel] ocfs2: fix sparse file & data ordering issue in direct io Dan Carpenter
2016-11-15 10:36   ` Dan Carpenter
2016-11-16  2:33     ` Eric Ren
2016-11-16 10:45       ` Dan Carpenter
2016-11-17  3:08         ` Eric Ren
2016-11-17 10:03           ` Dan Carpenter
2016-11-22  2:29             ` Junxiao Bi
2016-11-24 14:21               ` Dan Carpenter
2016-11-17 11:58 ` piaojun
2016-11-19  3:49   ` piaojun

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=20160309102505.GA15030@mwanda \
    --to=dan.carpenter@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.