linux-kernel - xfs: compiler implementation dependent behavior?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <1460747340.19090.42.camel@perches.com>
Date:	Fri, 15 Apr 2016 12:09:00 -0700
From:	Joe Perches <joe@...ches.com>
To:	Dave Chinner <david@...morbit.com>
Cc:	xfs@....sgi.com, LKML <linux-kernel@...r.kernel.org>
Subject: xfs: compiler implementation dependent behavior?

The value stored in *cycle in xlog_crack_grant_head_val
in xfs_log_priv.h is compiler implementation dependent.

Does it matter?

static inline void
xlog_crack_grant_head_val(int64_t val, int *cycle, int *space)
{
	*cycle = val >> 32;
	*space = val & 0xffffffff;
}