From: fabbione@sourceware.org <fabbione@sourceware.org>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] Cluster Project branch, master, updated. gfs-kernel_0_1_22-168-g4aa023e
Date: 15 Apr 2008 03:49:10 -0000 [thread overview]
Message-ID: <20080415034910.32741.qmail@sourceware.org> (raw)
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "Cluster Project".
http://sources.redhat.com/git/gitweb.cgi?p=cluster.git;a=commitdiff;h=4aa023e390abb5b466ddeb0e55e2acd7b45aa6df
The branch, master has been updated
via 4aa023e390abb5b466ddeb0e55e2acd7b45aa6df (commit)
from f3dea8c306d68a8ae7a136374cdebb98b97bb06c (commit)
Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.
- Log -----------------------------------------------------------------
commit 4aa023e390abb5b466ddeb0e55e2acd7b45aa6df
Author: Andrew Price <andy@andrewprice.me.uk>
Date: Tue Apr 15 05:48:12 2008 +0200
[GFS2] gfs2_fsck: Fix operation on 'ptr' may be undefined warnings
Occurrences of *ptr++ in fs_recovery.c made gcc throw up "operation on 'ptr'
may be undefined" warnings. This patch disambiguates those occurrences.
Signed-off-by: Andrew Price <andy@andrewprice.me.uk>
Signed-off-by: Fabio M. Di Nitto <fabbione@fabbione.net>
-----------------------------------------------------------------------
Summary of changes:
gfs2/fsck/fs_recovery.c | 9 ++++++---
1 files changed, 6 insertions(+), 3 deletions(-)
diff --git a/gfs2/fsck/fs_recovery.c b/gfs2/fsck/fs_recovery.c
index 3b25dc6..3e4094b 100644
--- a/gfs2/fsck/fs_recovery.c
+++ b/gfs2/fsck/fs_recovery.c
@@ -125,7 +125,8 @@ static int buf_lo_scan_elements(struct gfs2_inode *ip, unsigned int start,
sd_found_metablocks++;
- blkno = be64_to_cpu(*ptr++);
+ blkno = be64_to_cpu(*ptr);
+ ptr++;
if (gfs2_revoke_check(sdp, blkno, start))
continue;
@@ -218,8 +219,10 @@ static int databuf_lo_scan_elements(struct gfs2_inode *ip, unsigned int start,
gfs2_replay_incr_blk(ip, &start);
for (; blks; gfs2_replay_incr_blk(ip, &start), blks--) {
- blkno = be64_to_cpu(*ptr++);
- esc = be64_to_cpu(*ptr++);
+ blkno = be64_to_cpu(*ptr);
+ ptr++;
+ esc = be64_to_cpu(*ptr);
+ ptr++;
sd_found_jblocks++;
hooks/post-receive
--
Cluster Project
reply other threads:[~2008-04-15 3:49 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20080415034910.32741.qmail@sourceware.org \
--to=fabbione@sourceware.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.