linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: NeilBrown <neilb@suse.de>
To: Jes.Sorensen@redhat.com
Cc: linux-raid@vger.kernel.org, arnd@arndb.de, ralf@linux-mips.org
Subject: Re: [PATCH 1/1] Work around architectures having statfs.f_type defined as long
Date: Thu, 20 Mar 2014 09:24:56 +1100	[thread overview]
Message-ID: <20140320092456.5366169a@notabene.brown> (raw)
In-Reply-To: <1395235562-24672-2-git-send-email-Jes.Sorensen@redhat.com>

[-- Attachment #1: Type: text/plain, Size: 1296 bytes --]

On Wed, 19 Mar 2014 14:26:02 +0100 Jes.Sorensen@redhat.com wrote:

> From: Jes Sorensen <Jes.Sorensen@redhat.com>
> 
> Having RAMFS_MAGIC defined as 0x858458f6 causing problems when trying
> to compare it directly against statfs.f_type being cast from long to
> unsigned long.
> 
> This hack is extremly ugly, but it should at least do the right thing
> for every situation.
> 
> Thanks to Arnd Bergmann for suggesting the fix.
> 
> Signed-off-by: Jes Sorensen <Jes.Sorensen@redhat.com>
> ---
>  util.c | 6 +++++-
>  1 file changed, 5 insertions(+), 1 deletion(-)
> 
> diff --git a/util.c b/util.c
> index e32d97a..afb2bb1 100644
> --- a/util.c
> +++ b/util.c
> @@ -1946,9 +1946,13 @@ int in_initrd(void)
>  {
>  	/* This is based on similar function in systemd. */
>  	struct statfs s;
> +	/* statfs.f_type is signed long on s390x and MIPS, causing all
> +	   sorts of sign extension problems with RAMFS_MAGIC being
> +	   defined as 0x858458f6 */
>  	return  statfs("/", &s) >= 0 &&
>  		((unsigned long)s.f_type == TMPFS_MAGIC ||
> -		 (unsigned long)s.f_type == RAMFS_MAGIC);
> +		 ((unsigned long)s.f_type & 0xFFFFFFFFUL) ==
> +		 ((unsigned long)RAMFS_MAGIC & 0xFFFFFFFFUL));
>  }
>  
>  void reopen_mddev(int mdfd)


Applied, thanks.

NeilBrown


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 828 bytes --]

      parent reply	other threads:[~2014-03-19 22:24 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-19 13:26 [PATCH 0/1] Work around systems defining statfs.f_type as long Jes.Sorensen
2014-03-19 13:26 ` [PATCH 1/1] Work around architectures having statfs.f_type defined " Jes.Sorensen
2014-03-19 20:43   ` Arnd Bergmann
2014-03-19 22:24   ` NeilBrown [this message]

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=20140320092456.5366169a@notabene.brown \
    --to=neilb@suse.de \
    --cc=Jes.Sorensen@redhat.com \
    --cc=arnd@arndb.de \
    --cc=linux-raid@vger.kernel.org \
    --cc=ralf@linux-mips.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).