From: Dave Chinner <david@fromorbit.com>
To: Brian Foster <bfoster@redhat.com>
Cc: xfs@oss.sgi.com
Subject: Re: [ANNOUNCE] xfs: for-next branch updated to 4a91310
Date: Tue, 9 Feb 2016 06:52:53 +1100 [thread overview]
Message-ID: <20160208195253.GI27429@dastard> (raw)
In-Reply-To: <20160208153720.GG19597@bfoster.bfoster>
On Mon, Feb 08, 2016 at 10:37:20AM -0500, Brian Foster wrote:
> On Mon, Feb 08, 2016 at 05:07:51PM +1100, Dave Chinner wrote:
> > Hi folks,
> >
> > The for-next branch of the xfs kernel repository at
> >
> > git://git.kernel.org/pub/scm/linux/kernel/git/dgc/linux-xfs.git
> >
> > has just been updated. I've pushed this out with both generic quota
> > and direct Io modifications in it, so if they end up going into
> > another tree expect a rebase of the for-next branch to occur to pull
> > them in from the appropriate trees.
> >
> > There is still a lot of changes pending review to go into this
> > for-next tree, and I'm hoping to get the first part of the
> > rmap/reflink work into it as well, so there's plenty of work still
> > to be done in this cycle....
> >
> > The new head of the for-next branch is commit:
> >
> > 4a91310 Merge branch 'xfs-misc-fixes-4.6' into for-next
> >
> > New Commits:
> >
> > Brian Foster (2):
> > [60630fe] xfs: clean up unwritten buffers on write failure
> > [af055e3] xfs: fix xfs_log_ticket leak in xfs_end_io() after fs shutdown
> >
> > Carlos Maiolino (1):
> > [be60794] xfs: Split default quota limits by quota type
> >
> > Christoph Hellwig (6):
> > [187372a] direct-io: always call ->end_io if non-NULL
> > [273dda7] xfs: don't use ioends for direct write completions
> > [c19b104] xfs: fold xfs_vm_do_dio into xfs_vm_direct_IO
> > [196328e] xfs: handle errors from ->free_blocks in xfs_btree_kill_iroot
> > [c46ee8a] xfs: factor btree block freeing into a helper
> > [edfd9dd] xfs: move buffer invalidation to xfs_btree_free_block
> >
> > Darrick J. Wong (2):
> > [8e0bd49] xfs: fix endianness error when checking log block crc on big endian platforms
> > [244efea] xfs: move struct xfs_attr_shortform to xfs_da_format.h
> >
> > Dave Chinner (7):
> > [4b680af] xfs: lock rt summary inode on allocation
> > [a204d07] xfs: RT bitmap and summary buffers are not typed
> > [ca4de5c] xfs: RT bitmap and summary buffers need verifiers
>
> FYI, this one ^ leads to compile failures when CONFIG_XFS_RT is not
> enabled. xfs_rtbuf_ops is defined in the conditionally compiled
> xfs_rtbitmap.c file and used unconditionally in xfs_log_recover.c.
Ah, ok. I didn't test that - there's way too many different ways to
build kernels.... :/
I guess log recovery now needs #ifdef CONFIG_XFS_RT bits in it.
I'll spin up a patch later today.
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2016-02-08 19:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-08 6:07 [ANNOUNCE] xfs: for-next branch updated to 4a91310 Dave Chinner
2016-02-08 15:37 ` Brian Foster
2016-02-08 19:52 ` Dave Chinner [this message]
2016-02-08 23:33 ` [PATCH] xfs: log recovery needs to be aware of CONFIG_XFS_RT now Dave Chinner
2016-02-09 2:06 ` Eric Sandeen
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=20160208195253.GI27429@dastard \
--to=david@fromorbit.com \
--cc=bfoster@redhat.com \
--cc=xfs@oss.sgi.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