linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Theodore Ts'o" <tytso@mit.edu>
To: Miklos Szeredi <miklos@szeredi.hu>
Cc: Jan Kara <jack@suse.cz>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	"linux-ext4@vger.kernel.org" <linux-ext4@vger.kernel.org>,
	Al Viro <viro@zeniv.linux.org.uk>
Subject: Re: [GIT PULL] ext4 changes for 3.15
Date: Fri, 4 Apr 2014 19:43:58 -0400	[thread overview]
Message-ID: <20140404234358.GE10275@thunk.org> (raw)
In-Reply-To: <CAJfpegsJd9d8NTmwozJ+u_ZS-SnUwAQFwAne6P1KqG=VZeZSTA@mail.gmail.com>

On Fri, Apr 04, 2014 at 07:16:25PM +0200, Miklos Szeredi wrote:
> 
> http://marc.info/?l=linux-kernel&m=139523745403081&w=2

I tried applying this patch on top of xfstests commit 3948694eb1, but
running on ext4.git's test branch, which has the your cross-rename
patches applied:

http://git.kernel.org/cgit/linux/kernel/git/tytso/ext4.git/commit/?h=test&id=b7bcc46d4f80139930c2e6bd04ff8ebbff121bc9

I see the following:

BEGIN TEST: Ext4 4k block Fri Apr  4 23:21:50 UTC 2014
Device: /dev/vdb
mk2fs options: -q
mount options: -o block_validity
FSTYP         -- ext4
PLATFORM      -- Linux/i686 candygram 3.14.0-00061-gb7bcc46
MKFS_OPTIONS  -- -q /dev/vdc
MOUNT_OPTIONS -- -o acl,user_xattr -o block_validity /dev/vdc /vdc

generic/323		[23:22:03] [23:22:04] [not run]
	generic/323 -- kernel doesn't support renameat2 syscall
generic/324		[23:22:04] [23:22:05] [not run]
	generic/324 -- kernel doesn't support renameat2 syscall
generic/325		[23:22:05] [23:22:06] [not run]
	generic/325 -- kernel doesn't support renameat2 syscall
Not run: generic/323 generic/324 generic/325

Is there anything obvious that I might be doing wrong?

Thanks,

							- Ted

  parent reply	other threads:[~2014-04-04 23:44 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-03 19:15 [GIT PULL] ext4 changes for 3.15 Theodore Ts'o
2014-04-03 19:39 ` Linus Torvalds
2014-04-04  3:53   ` Theodore Ts'o
2014-04-04 13:44     ` Jan Kara
2014-04-04 17:16       ` Miklos Szeredi
2014-04-04 20:23         ` Theodore Ts'o
2014-04-08 10:47           ` Dave Chinner
2014-04-04 23:43         ` Theodore Ts'o [this message]
2014-04-07 13:15           ` Miklos Szeredi
2014-04-07 14:07             ` Theodore Ts'o
2014-04-07 20:25               ` Geert Uytterhoeven
2014-04-08 11:25                 ` Heiko Carstens
2014-04-08 16:25                   ` Linus Torvalds
2014-04-08 13:47                 ` Theodore Ts'o
2014-04-09 16:40                   ` Geert Uytterhoeven
2014-04-09 16:55                     ` H. Peter Anvin
2014-04-09 17:48                       ` Geert Uytterhoeven
2014-04-09 18:23                         ` Theodore Ts'o
2014-04-09 19:19                           ` H. Peter Anvin
2014-06-24 22:03 ` Maciej W. Rozycki
2014-06-24 22:39   ` Thavatchai Makphaibulchoke
2014-06-24 23:25     ` Maciej W. Rozycki
2014-06-25 17:08     ` Linus Torvalds
2014-06-25 22:37       ` Theodore Ts'o

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=20140404234358.GE10275@thunk.org \
    --to=tytso@mit.edu \
    --cc=jack@suse.cz \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=miklos@szeredi.hu \
    --cc=torvalds@linux-foundation.org \
    --cc=viro@zeniv.linux.org.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).