linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Chris Mason <chris.mason@fusionio.com>
To: Martin <m_btrfs@ml1.co.uk>, <linux-btrfs@vger.kernel.org>
Subject: Re: progs integration branch moved to master (new default leafsize)
Date: Thu, 21 Nov 2013 18:37:51 -0500	[thread overview]
Message-ID: <20131121233751.5312.13383@localhost.localdomain> (raw)
In-Reply-To: <l5jtgo$6q1$1@ger.gmane.org>

Quoting Martin (2013-11-08 18:53:06)
> On 08/11/13 22:01, Chris Mason wrote:
> > Hi everyone,
> > 
> > This patch is now the tip of the master branch for btrfs-progs, which
> > has been updated to include most of the backlogged progs patches.
> > Please take a look and give it a shake.  This was based on Dave's
> > integration tree (many thanks Dave!) minus the patches for online dedup.
> > I've pulled in the coverity fixes and a few others from the list as
> > well.
> > 
> > The patch below switches our default mkfs leafsize up to 16K.  This
> > should be a better choice in almost every workload, but now is your
> > chance to complain if it causes trouble.
> 
> Thanks for that and nicely timely!
> 
> Compiling on Gentoo (3.11.5-gentoo, sys-fs/btrfs-progs-9999) gives:
> 
> 
>  * QA Notice: Package triggers severe warnings which indicate that it
>  *            may exhibit random runtime failures.
>  * disk-io.c:91:5: warning: dereferencing type-punned pointer will break
> strict-aliasing rules [-Wstrict-aliasing]
>  * volumes.c:1930:5: warning: dereferencing type-punned pointer will
> break strict-aliasing rules [-Wstrict-aliasing]
>  * volumes.c:1931:6: warning: dereferencing type-punned pointer will
> break strict-aliasing rules [-Wstrict-aliasing]

I'm not seeing these warnings with the current master branch, could you
please rerun?

-chris


  reply	other threads:[~2013-11-21 23:38 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-08 22:01 progs integration branch moved to master (new default leafsize) Chris Mason
2013-11-08 23:53 ` Martin
2013-11-21 23:37   ` Chris Mason [this message]
2013-11-22  9:03     ` Martin
2013-11-22 13:40       ` Chris Mason
2013-11-22 19:50         ` Martin
2013-11-22 19:57           ` Chris Mason
2013-11-23  0:02             ` Martin
2013-11-22 22:05         ` Duncan
2013-11-14 12:41 ` David Sterba
  -- strict thread matches above, loose matches on Subject: below --
2013-11-14 17:28 Chris Mason

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=20131121233751.5312.13383@localhost.localdomain \
    --to=chris.mason@fusionio.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=m_btrfs@ml1.co.uk \
    /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).