From: Dave Chinner <david@fromorbit.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
xfs@oss.sgi.com
Subject: Re: [GIT PULL] xfs: fixes for 3.15-rc5
Date: Fri, 9 May 2014 10:47:08 +1000 [thread overview]
Message-ID: <20140509004708.GH26353@dastard> (raw)
In-Reply-To: <CA+55aFy9B=OcqfniMiq+EhDa_rzc0-owcmbUck1FmBOU+Q-Dvw@mail.gmail.com>
On Thu, May 08, 2014 at 04:13:00PM -0700, Linus Torvalds wrote:
> On Thu, May 8, 2014 at 2:12 PM, Dave Chinner <david@fromorbit.com> wrote:
> >
> > BTW, will GPG signing these pull requests cause you problems?
>
> Nope. But I won't be checking email signatures. GPG email signing is
> so badly done that afaik only one or two email clients support it.
>
> > I've
> > been signing everything "official" I send as the XFS maintainer
> > (e.g. notifications of tree updates) and I figured that pull
> > requests are about as "official" as it gets. The tag is signed, so
> > I'm not particularly worried either way...
>
> .. what tag? You point me at
>
> > git://oss.sgi.com/xfs/xfs.git xfs-fixes-for-3.15-rc5
>
> and that is definitely not a tag.
Hmmm, I didn't notice the output of the pull request command I ran
converted the tag to a branch. Checking my command history, it looks
like I ran request-pull before I pushed the tag. Sure be nice to get
a "tag doesn't exist upstream" error, but I'll make sure I don't do
that again.
> Did you *mean* to point me at refs/tags/xfs-for-linus-3.15-rc5, perhaps?
Yup, updated request below.
-Dave.
The following changes since commit 330033d697ed8d296fa52b5303db9d802ad901cc:
xfs: fix tmpfile/selinux deadlock and initialize security (2014-04-17 08:15:30 +1000)
are available in the git repository at:
git://oss.sgi.com/xfs/xfs.git tags/xfs-for-linus-3.15-rc5
for you to fetch changes up to 8275cdd0e7ac550dcce2b3ef6d2fb3b808c1ae59:
xfs: remote attribute overwrite causes transaction overrun (2014-05-06 07:37:31 +1000)
----------------------------------------------------------------
Fixes for 3.15-rc5:
- fix a remote attribute size calculation bug that leads to a
transaction overrun
- add default ACLs to O_TMPFILE files
- Remove the EXPERIMENTAL tag from filesystems with metadata CRC
support
----------------------------------------------------------------
Brian Foster (1):
xfs: initialize default acls for ->tmpfile()
Dave Chinner (2):
xfs: fully support v5 format filesystems
xfs: remote attribute overwrite causes transaction overrun
fs/xfs/xfs_attr.c | 24 +++++++++++++++++++-
fs/xfs/xfs_attr_leaf.c | 21 +++++++++---------
fs/xfs/xfs_attr_list.c | 1 +
fs/xfs/xfs_attr_remote.c | 8 ++++---
fs/xfs/xfs_da_btree.h | 2 ++
fs/xfs/xfs_iops.c | 55 ++++++++++++++++++++++++----------------------
fs/xfs/xfs_log.c | 10 +++++----
fs/xfs/xfs_mount.c | 2 --
fs/xfs/xfs_sb.c | 4 ----
9 files changed, 77 insertions(+), 50 deletions(-)
--
Dave Chinner
david@fromorbit.com
prev parent reply other threads:[~2014-05-09 0:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-08 21:12 [GIT PULL] xfs: fixes for 3.15-rc5 Dave Chinner
2014-05-08 23:13 ` Linus Torvalds
2014-05-09 0:47 ` Dave Chinner [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=20140509004708.GH26353@dastard \
--to=david@fromorbit.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--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