linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Theodore Ts'o <tytso@mit.edu>
To: Ross Zwisler <ross.zwisler@linux.intel.com>
Cc: linux-ext4@vger.kernel.org
Subject: Re: [PATCH 0/9 v4] ext4: Punch hole and DAX fixes
Date: Thu, 10 Dec 2015 11:26:42 -0500	[thread overview]
Message-ID: <20151210162642.GB8898@thunk.org> (raw)
In-Reply-To: <20151209235518.GA31235@linux.intel.com>

On Wed, Dec 09, 2015 at 04:55:18PM -0700, Ross Zwisler wrote:
> Hey Ted,
> 
> I'm working on some fsync/msync patches that I'm hoping to merge for v4.5 and
> my patches build upon the work done in this series by Jan.
> 
> I see Jan's patches in your dev branch - do you expect that branch to be part
> of a pull request (are the commit IDs stable)?  Or will patches from the dev
> branch get moved into another branch before you send the pull request to
> Linus?

Thanks for asking.  I assume your work is not just ext4 specific (in
which I could just manage it using patches in the ext4 patch queue).,
but where you want to start a git tree and then push to Linus
independently, yes?

> I'm just trying to figure out what I should use as a baseline for my changes
> since I need to build on Jan's patches but obviously don't want to include new
> ext4 code with my pull request (which I will send after you send yours). :)

Please use the "master" branch from the ext4 tree as your baseline.
Normally dev is a rewinding branch, but for these sorts of situations
I'll guarantee that everything between origin..master will be stable,
while commits between master..dev may be rewound or dropped to fix
bugs/regressions:

* dde86e3 - (HEAD -> guilt/origin, dev) ext4 crypto: add missing locking for keyring_key access (10 hours ago)
* 0969c39 - ext4 crypto: add ioctls to allow backup of encryption metadata (10 hours ago)
* 843848f - ext4 crypto: add ciphertext_access mount option (10 hours ago)
* ba5843f - (master) ext4: use pre-zeroed blocks for DAX page faults (3 days ago)
* c86d8db - ext4: implement allocation of pre-zeroed blocks (3 days ago)
* 53085fa - ext4: provide ext4_issue_zeroout() (3 days ago)
* 2dcba47 - ext4: get rid of EXT4_GET_BLOCKS_NO_LOCK flag (3 days ago)
* e74031f - ext4: document lock ordering (3 days ago)
* 0112784 - ext4: fix races of writeback with punch hole and zero range (3 days ago)
* 32ebffd - ext4: fix races between buffered IO and collapse / insert range (3 days ago)
* 17048e8 - ext4: move unlocked dio protection from ext4_alloc_file_blocks() (3 days ago)
* ea3d720 - ext4: fix races between page faults and hole punching (3 days ago)

Jan's patches have gone through multiple rounds of testing and I'm
quite confident there are no bugs or regressions that can't be dealt
with using follow up patches.

Cheers,

							- Ted

  parent reply	other threads:[~2015-12-10 16:26 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-10 19:50 [PATCH 0/9 v4] ext4: Punch hole and DAX fixes Jan Kara
2015-11-10 19:50 ` [PATCH 1/9] ext4: Fix races between page faults and hole punching Jan Kara
2015-11-10 19:50 ` [PATCH 2/9] ext4: Move unlocked dio protection from ext4_alloc_file_blocks() Jan Kara
2015-11-10 19:50 ` [PATCH 3/9] ext4: Fix races between buffered IO and collapse / insert range Jan Kara
2015-11-18  1:39   ` Elliott, Robert (Persistent Memory)
2015-11-18 15:16     ` Jan Kara
2015-11-10 19:50 ` [PATCH 4/9] ext4: Fix races of writeback with punch hole and zero range Jan Kara
2015-11-10 19:50 ` [PATCH 5/9] ext4: Document lock ordering Jan Kara
2015-11-10 19:50 ` [PATCH 6/9] ext4: Get rid of EXT4_GET_BLOCKS_NO_LOCK flag Jan Kara
2015-11-10 19:50 ` [PATCH 7/9] ext4: Provide ext4_issue_zeroout() Jan Kara
2015-11-10 19:50 ` [PATCH 8/9] ext4: Implement allocation of pre-zeroed blocks Jan Kara
2015-11-10 19:50 ` [PATCH 9/9] ext4: Use pre-zeroed blocks for DAX page faults Jan Kara
2015-11-17 17:41 ` [PATCH 0/9 v4] ext4: Punch hole and DAX fixes Boylston, Brian
2015-11-18 15:13   ` Jan Kara
2015-12-08  1:08 ` Theodore Ts'o
     [not found]   ` <20151209235518.GA31235@linux.intel.com>
2015-12-10 16:26     ` Theodore Ts'o [this message]
2015-12-10 17:10       ` Ross Zwisler

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=20151210162642.GB8898@thunk.org \
    --to=tytso@mit.edu \
    --cc=linux-ext4@vger.kernel.org \
    --cc=ross.zwisler@linux.intel.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).