All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Kara <jack@suse.cz>
To: Eric Sandeen <sandeen@sandeen.net>
Cc: Jan Kara <jack@suse.cz>,
	linux-nvdimm@lists.01.org, darrick.wong@oracle.com,
	Theodore Ts'o <tytso@mit.edu>, Ross Zwisler <zwisler@kernel.org>,
	linux-fsdevel <linux-fsdevel@vger.kernel.org>,
	lczerner@redhat.com, linux-ext4 <linux-ext4@vger.kernel.org>
Subject: Re: [PATCH v4 0/2] ext4: fix DAX dma vs truncate/hole-punch
Date: Tue, 11 Sep 2018 17:20:24 +0200	[thread overview]
Message-ID: <20180911152024.GE6104@quack2.suse.cz> (raw)
In-Reply-To: <20180911151421.GD6104@quack2.suse.cz>

On Tue 11-09-18 17:14:21, Jan Kara wrote:
> On Mon 10-09-18 17:18:49, Eric Sandeen wrote:
> > On 8/7/18 3:45 AM, Jan Kara wrote:
> > > 
> > > OK, this is a good catch and the patch looks good. You can add:
> > > 
> > > Reviewed-by: Jan Kara <jack@suse.cz>
> > > 
> > > Also please post this fix officially to Ted to include it in his tree (I
> > > can see that he has all your other patches queued for the merge window).
> > 
> > Did these ever get on Ted's radar?  I don't see it upstream yet.
> 
> Hum, it seems Ted never picked this patch up. I guess I'll gather the two
> fixes you pointed out and resend them to Ted.

Actually only one patch when looking into it now.

								Honza
-- 
Jan Kara <jack@suse.com>
SUSE Labs, CR
_______________________________________________
Linux-nvdimm mailing list
Linux-nvdimm@lists.01.org
https://lists.01.org/mailman/listinfo/linux-nvdimm

WARNING: multiple messages have this Message-ID (diff)
From: Jan Kara <jack@suse.cz>
To: Eric Sandeen <sandeen@sandeen.net>
Cc: Jan Kara <jack@suse.cz>, Ross Zwisler <zwisler@kernel.org>,
	linux-nvdimm@lists.01.org, darrick.wong@oracle.com,
	lczerner@redhat.com, linux-ext4 <linux-ext4@vger.kernel.org>,
	linux-fsdevel <linux-fsdevel@vger.kernel.org>,
	Theodore Ts'o <tytso@mit.edu>
Subject: Re: [PATCH v4 0/2] ext4: fix DAX dma vs truncate/hole-punch
Date: Tue, 11 Sep 2018 17:20:24 +0200	[thread overview]
Message-ID: <20180911152024.GE6104@quack2.suse.cz> (raw)
In-Reply-To: <20180911151421.GD6104@quack2.suse.cz>

On Tue 11-09-18 17:14:21, Jan Kara wrote:
> On Mon 10-09-18 17:18:49, Eric Sandeen wrote:
> > On 8/7/18 3:45 AM, Jan Kara wrote:
> > > 
> > > OK, this is a good catch and the patch looks good. You can add:
> > > 
> > > Reviewed-by: Jan Kara <jack@suse.cz>
> > > 
> > > Also please post this fix officially to Ted to include it in his tree (I
> > > can see that he has all your other patches queued for the merge window).
> > 
> > Did these ever get on Ted's radar?  I don't see it upstream yet.
> 
> Hum, it seems Ted never picked this patch up. I guess I'll gather the two
> fixes you pointed out and resend them to Ted.

Actually only one patch when looking into it now.

								Honza
-- 
Jan Kara <jack@suse.com>
SUSE Labs, CR

WARNING: multiple messages have this Message-ID (diff)
From: Jan Kara <jack-AlSwsSmVLrQ@public.gmane.org>
To: Eric Sandeen <sandeen-+82itfer+wXR7s880joybQ@public.gmane.org>
Cc: Jan Kara <jack-AlSwsSmVLrQ@public.gmane.org>,
	linux-nvdimm-hn68Rpc1hR1g9hUCZPvPmw@public.gmane.org,
	darrick.wong-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org,
	Theodore Ts'o <tytso-3s7WtUTddSA@public.gmane.org>,
	Ross Zwisler <zwisler-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
	linux-fsdevel
	<linux-fsdevel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
	lczerner-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org,
	linux-ext4 <linux-ext4-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: [PATCH v4 0/2] ext4: fix DAX dma vs truncate/hole-punch
Date: Tue, 11 Sep 2018 17:20:24 +0200	[thread overview]
Message-ID: <20180911152024.GE6104@quack2.suse.cz> (raw)
In-Reply-To: <20180911151421.GD6104-4I4JzKEfoa/jFM9bn6wA6Q@public.gmane.org>

On Tue 11-09-18 17:14:21, Jan Kara wrote:
> On Mon 10-09-18 17:18:49, Eric Sandeen wrote:
> > On 8/7/18 3:45 AM, Jan Kara wrote:
> > > 
> > > OK, this is a good catch and the patch looks good. You can add:
> > > 
> > > Reviewed-by: Jan Kara <jack-AlSwsSmVLrQ@public.gmane.org>
> > > 
> > > Also please post this fix officially to Ted to include it in his tree (I
> > > can see that he has all your other patches queued for the merge window).
> > 
> > Did these ever get on Ted's radar?  I don't see it upstream yet.
> 
> Hum, it seems Ted never picked this patch up. I guess I'll gather the two
> fixes you pointed out and resend them to Ted.

Actually only one patch when looking into it now.

								Honza
-- 
Jan Kara <jack-IBi9RG/b67k@public.gmane.org>
SUSE Labs, CR

  reply	other threads:[~2018-09-11 15:20 UTC|newest]

Thread overview: 58+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-10 19:10 [PATCH v4 0/2] ext4: fix DAX dma vs truncate/hole-punch Ross Zwisler
2018-07-10 19:10 ` Ross Zwisler
2018-07-10 19:10 ` [PATCH v4 1/2] dax: dax_layout_busy_page() warn on !exceptional Ross Zwisler
2018-07-10 19:10   ` Ross Zwisler
2018-08-10 19:52   ` Eric Sandeen
2018-08-10 19:52     ` Eric Sandeen
2018-08-10 20:33     ` Theodore Y. Ts'o
2018-08-10 20:33       ` Theodore Y. Ts'o
2018-08-11  2:10       ` Theodore Y. Ts'o
2018-08-11  2:10         ` Theodore Y. Ts'o
2018-08-13 10:12         ` Jan Kara
2018-08-13 10:12           ` Jan Kara
2018-08-13 12:46           ` Theodore Y. Ts'o
2018-08-13 12:46             ` Theodore Y. Ts'o
2018-08-24 15:44           ` Jan Kara
2018-08-24 15:44             ` Jan Kara
2018-08-27 16:09           ` Jan Kara
2018-08-27 16:09             ` Jan Kara
2018-07-10 19:10 ` [PATCH v4 2/2] ext4: handle layout changes to pinned DAX mappings Ross Zwisler
2018-07-10 19:10   ` Ross Zwisler
2018-07-11  8:17 ` [PATCH v4 0/2] ext4: fix DAX dma vs truncate/hole-punch Jan Kara
2018-07-11  8:17   ` Jan Kara
2018-07-11 15:41   ` Ross Zwisler
2018-07-11 15:41     ` Ross Zwisler
2018-07-25 22:28   ` Ross Zwisler
2018-07-25 22:28     ` Ross Zwisler
2018-07-27 16:28     ` Ross Zwisler
2018-07-27 16:28       ` Ross Zwisler
2018-07-27 16:28       ` Ross Zwisler
2018-08-06  3:55       ` Dave Chinner
2018-08-06  3:55         ` Dave Chinner
2018-08-06  3:55         ` Dave Chinner
2018-08-06 15:49         ` Christoph Hellwig
2018-08-06 15:49           ` Christoph Hellwig
2018-08-06 15:49           ` Christoph Hellwig
2018-08-06 22:25           ` Dave Chinner
2018-08-06 22:25             ` Dave Chinner
2018-08-06 22:25             ` Dave Chinner
2018-08-07  8:45       ` Jan Kara
2018-08-07  8:45         ` Jan Kara
2018-08-07  8:45         ` Jan Kara
2018-09-10 22:18         ` Eric Sandeen
2018-09-10 22:18           ` Eric Sandeen
2018-09-10 22:18           ` Eric Sandeen
2018-09-11 15:14           ` Jan Kara
2018-09-11 15:14             ` Jan Kara
2018-09-11 15:14             ` Jan Kara
2018-09-11 15:20             ` Jan Kara [this message]
2018-09-11 15:20               ` Jan Kara
2018-09-11 15:20               ` Jan Kara
2018-09-11 17:28               ` Theodore Y. Ts'o
2018-09-11 17:28                 ` Theodore Y. Ts'o
2018-09-11 17:28                 ` Theodore Y. Ts'o
2018-09-11 18:21                 ` Eric Sandeen
2018-09-11 18:21                   ` Eric Sandeen
2018-09-11 18:21                   ` Eric Sandeen
2018-07-31 19:44 ` Ross Zwisler
2018-07-31 19:44   ` 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=20180911152024.GE6104@quack2.suse.cz \
    --to=jack@suse.cz \
    --cc=darrick.wong@oracle.com \
    --cc=lczerner@redhat.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-nvdimm@lists.01.org \
    --cc=sandeen@sandeen.net \
    --cc=tytso@mit.edu \
    --cc=zwisler@kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.