linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Gene Czarcinski <gene@czarc.net>
To: linux-btrfs <linux-btrfs@vger.kernel.org>
Cc: chris.mason@fusionio.com, sandeen@redhat.com
Subject: Re: [PATCH 2/6] Fedora 18 - build-fixes.patch
Date: Tue, 22 Jan 2013 16:25:44 -0500	[thread overview]
Message-ID: <50FF03D8.3040009@czarc.net> (raw)
In-Reply-To: <1358618781-26629-3-git-send-email-gene@czarc.net>

I believe that this if the likely source of this patch:
http://article.gmane.org/gmane.comp.file-systems.btrfs/4547

I do wonder how much this is still applicable.  However, it has been in 
the btrfs-progs package for Fedora 15, 16, 17, and 18 plus likely some 
versions of RHEL.

On 01/19/2013 01:06 PM, Gene Czarcinski wrote:
> Signed-off-by: Gene Czarcinski <gene@czarc.net>
> ---
>   btrfsck.c | 2 ++
>   mkfs.c    | 4 ++--
>   2 files changed, 4 insertions(+), 2 deletions(-)
>
> diff --git a/btrfsck.c b/btrfsck.c
> index a851008..6274ff7 100644
> --- a/btrfsck.c
> +++ b/btrfsck.c
> @@ -22,7 +22,9 @@
>   #include <stdlib.h>
>   #include <unistd.h>
>   #include <fcntl.h>
> +#include <sys/types.h>
>   #include <sys/stat.h>
> +#include <unistd.h>
>   #include <getopt.h>
>   #include "kerncompat.h"
>   #include "ctree.h"
> diff --git a/mkfs.c b/mkfs.c
> index fbf8319..d123d5f 100644
> --- a/mkfs.c
> +++ b/mkfs.c
> @@ -1206,7 +1206,7 @@ int main(int ac, char **av)
>   	u64 alloc_start = 0;
>   	u64 metadata_profile = 0;
>   	u64 data_profile = 0;
> -	u32 leafsize = getpagesize();
> +	u32 leafsize = sysconf(_SC_PAGESIZE);
>   	u32 sectorsize = 4096;
>   	u32 nodesize = leafsize;
>   	u32 stripesize = 4096;
> @@ -1282,7 +1282,7 @@ int main(int ac, char **av)
>   				print_usage();
>   		}
>   	}
> -	sectorsize = max(sectorsize, (u32)getpagesize());
> +	sectorsize = max(sectorsize, (u32)sysconf(_SC_PAGESIZE));
>   	if (check_leaf_or_node_size(leafsize, sectorsize))
>   		exit(1);
>   	if (check_leaf_or_node_size(nodesize, sectorsize))


  reply	other threads:[~2013-01-22 21:25 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-19 18:06 [PATCH 0/6] patches from Fedora 18 (resubmitted) Gene Czarcinski
2013-01-19 18:06 ` [PATCH 1/6] Fedora 18 - btrfs-init-dev-list.patch Gene Czarcinski
2013-01-22 21:56   ` Gene Czarcinski
2013-01-19 18:06 ` [PATCH 2/6] Fedora 18 - build-fixes.patch Gene Czarcinski
2013-01-22 21:25   ` Gene Czarcinski [this message]
2013-01-23 18:12     ` David Sterba
2013-01-19 18:06 ` [PATCH 3/6] Fedora 18 - fix-labels.patch Gene Czarcinski
2013-01-22 21:45   ` Gene Czarcinski
2013-01-19 18:06 ` [PATCH 4/6] Fedora 18 - modified valgrind.patch Gene Czarcinski
2013-01-22 21:53   ` Gene Czarcinski
2013-01-23 19:40   ` Eric Sandeen
2013-01-19 18:06 ` [PATCH 5/6] Btrfs-progs: add btrfs device ready command Gene Czarcinski
2013-01-19 18:06 ` [PATCH 6/6] Btrfs-progs: detect if the disk we are formatting is a ssd Gene Czarcinski
2013-01-19 21:14   ` Brendan Hide
2013-01-21 13:01     ` David Sterba
2013-01-23  2:35     ` Chris Samuel

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=50FF03D8.3040009@czarc.net \
    --to=gene@czarc.net \
    --cc=chris.mason@fusionio.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=sandeen@redhat.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 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).