Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.kernel > #1256435 > unrolled thread

[PATCH] blktrace: re-write setting q->blk_trace

Started byDavidlohr Bueso <dave@stgolabs.net>
First post2015-10-27 04:10 +0100
Last post2015-10-29 22:10 +0100
Articles 10 — 3 participants

Back to article view | Back to linux.kernel

Contents

  [PATCH] blktrace: re-write setting q->blk_trace Davidlohr Bueso <dave@stgolabs.net> - 2015-10-27 04:10 +0100
    [PATCH v2] blktrace: re-write setting q->blk_trace Davidlohr Bueso <dave@stgolabs.net> - 2015-10-27 04:20 +0100
      Re: [PATCH v2] blktrace: re-write setting q->blk_trace Jeff Moyer <jmoyer@redhat.com> - 2015-10-28 22:40 +0100
        Re: [PATCH v2] blktrace: re-write setting q->blk_trace Davidlohr Bueso <dave@stgolabs.net> - 2015-10-29 20:20 +0100
          Re: [PATCH v2] blktrace: re-write setting q->blk_trace Jeff Moyer <jmoyer@redhat.com> - 2015-10-29 20:40 +0100
          Re: [PATCH v2] blktrace: re-write setting q->blk_trace Jens Axboe <axboe@kernel.dk> - 2015-10-29 21:30 +0100
            Re: [PATCH v2] blktrace: re-write setting q->blk_trace Jens Axboe <axboe@kernel.dk> - 2015-10-29 21:50 +0100
              Re: [PATCH v2] blktrace: re-write setting q->blk_trace Jeff Moyer <jmoyer@redhat.com> - 2015-10-29 22:00 +0100
            Re: [PATCH v2] blktrace: re-write setting q->blk_trace Jeff Moyer <jmoyer@redhat.com> - 2015-10-29 21:50 +0100
            Re: [PATCH v2] blktrace: re-write setting q->blk_trace Davidlohr Bueso <dave@stgolabs.net> - 2015-10-29 22:10 +0100

#1256435 — [PATCH] blktrace: re-write setting q->blk_trace

FromDavidlohr Bueso <dave@stgolabs.net>
Date2015-10-27 04:10 +0100
Subject[PATCH] blktrace: re-write setting q->blk_trace
Message-ID<qo2O5-8hu-1@gated-at.bofh.it>
This is really about simplifying the double xchg patterns into
a single cmpxchg, with the same logic. Other than the immediate
cleanup, there are some subtleties this change deals with:

(i) While the load of the old bt is fully ordered wrt everything,
ie:

       old_bt = xchg(&q->blk_trace, bt);             [barrier]
       if (old_bt)
	     (void) xchg(&q->blk_trace, old_bt);    [barrier]

blk_trace could still be changed between the xchg and the old_bt
load. Note that this description is merely theoretical and afaict
very small, but doing everything in a single context with cmpxchg
closes this potential race.

(ii) Ordering guarantees are obviously kept with cmpxchg.

Signed-off-by: Davidlohr Bueso <dbueso@suse.de>
---
  kernel/trace/blktrace.c | 15 ++++-----------
  1 file changed, 4 insertions(+), 11 deletions(-)

diff --git a/kernel/trace/blktrace.c b/kernel/trace/blktrace.c
index 90e72a0..4a30229 100644
--- a/kernel/trace/blktrace.c
+++ b/kernel/trace/blktrace.c
@@ -437,7 +437,7 @@ int do_blk_trace_setup(struct request_queue *q, char *name, dev_t dev,
		       struct block_device *bdev,
		       struct blk_user_trace_setup *buts)
  {
-	struct blk_trace *old_bt, *bt = NULL;
+	struct blk_trace *bt = NULL;
	struct dentry *dir = NULL;
	int ret;

@@ -519,11 +519,8 @@ int do_blk_trace_setup(struct request_queue *q, char *name, dev_t dev,
	bt->trace_state = Blktrace_setup;

	ret = -EBUSY;
-	old_bt = xchg(&q->blk_trace, bt);
-	if (old_bt) {
-		(void) xchg(&q->blk_trace, old_bt);
+	if (cmpxchg(&q->blk_trace, NULL, bt))
		goto err;
-	}

	if (atomic_inc_return(&blk_probes_ref) == 1)
		blk_register_tracepoints();
@@ -1481,7 +1478,7 @@ static int blk_trace_remove_queue(struct request_queue *q)
  static int blk_trace_setup_queue(struct request_queue *q,
				 struct block_device *bdev)
  {
-	struct blk_trace *old_bt, *bt = NULL;
+	struct blk_trace *bt = NULL;
	int ret = -ENOMEM;

	bt = kzalloc(sizeof(*bt), GFP_KERNEL);
@@ -1497,12 +1494,8 @@ static int blk_trace_setup_queue(struct request_queue *q,

	blk_trace_setup_lba(bt, bdev);

-	old_bt = xchg(&q->blk_trace, bt);
-	if (old_bt != NULL) {
-		(void)xchg(&q->blk_trace, old_bt);
-		ret = -EBUSY;
+	if (cmpxchg(&q->blk_trace, NULL, bt))
		goto free_bt;
-	}

	if (atomic_inc_return(&blk_probes_ref) == 1)
		blk_register_tracepoints();
--
2.1.4
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[toc] | [next] | [standalone]

#1256438 — [PATCH v2] blktrace: re-write setting q->blk_trace

FromDavidlohr Bueso <dave@stgolabs.net>
Date2015-10-27 04:20 +0100
Subject[PATCH v2] blktrace: re-write setting q->blk_trace
Message-ID<qo2XL-8qJ-1@gated-at.bofh.it>
In reply to#1256435
This is really about simplifying the double xchg patterns into
a single cmpxchg, with the same logic. Other than the immediate
cleanup, there are some subtleties this change deals with:

(i) While the load of the old bt is fully ordered wrt everything,
ie:

       old_bt = xchg(&q->blk_trace, bt);             [barrier]
       if (old_bt)
	     (void) xchg(&q->blk_trace, old_bt);    [barrier]

blk_trace could still be changed between the xchg and the old_bt
load. Note that this description is merely theoretical and afaict
very small, but doing everything in a single context with cmpxchg
closes this potential race.

(ii) Ordering guarantees are obviously kept with cmpxchg.

Signed-off-by: Davidlohr Bueso <dbueso@suse.de>
---

v2: sorry I sent a stale version which didn't set EBUSY when the structure is
already initialized.

  kernel/trace/blktrace.c | 16 +++++-----------
  1 file changed, 5 insertions(+), 11 deletions(-)

diff --git a/kernel/trace/blktrace.c b/kernel/trace/blktrace.c
index 90e72a0..e3a2618 100644
--- a/kernel/trace/blktrace.c
+++ b/kernel/trace/blktrace.c
@@ -437,7 +437,7 @@ int do_blk_trace_setup(struct request_queue *q, char *name, dev_t dev,
  		       struct block_device *bdev,
  		       struct blk_user_trace_setup *buts)
  {
-	struct blk_trace *old_bt, *bt = NULL;
+	struct blk_trace *bt = NULL;
  	struct dentry *dir = NULL;
  	int ret;
  
@@ -519,11 +519,8 @@ int do_blk_trace_setup(struct request_queue *q, char *name, dev_t dev,
  	bt->trace_state = Blktrace_setup;
  
  	ret = -EBUSY;
-	old_bt = xchg(&q->blk_trace, bt);
-	if (old_bt) {
-		(void) xchg(&q->blk_trace, old_bt);
+	if (cmpxchg(&q->blk_trace, NULL, bt))
  		goto err;
-	}
  
  	if (atomic_inc_return(&blk_probes_ref) == 1)
  		blk_register_tracepoints();
@@ -1481,7 +1478,7 @@ static int blk_trace_remove_queue(struct request_queue *q)
  static int blk_trace_setup_queue(struct request_queue *q,
  				 struct block_device *bdev)
  {
-	struct blk_trace *old_bt, *bt = NULL;
+	struct blk_trace *bt = NULL;
  	int ret = -ENOMEM;
  
  	bt = kzalloc(sizeof(*bt), GFP_KERNEL);
@@ -1497,12 +1494,9 @@ static int blk_trace_setup_queue(struct request_queue *q,
  
  	blk_trace_setup_lba(bt, bdev);
  
-	old_bt = xchg(&q->blk_trace, bt);
-	if (old_bt != NULL) {
-		(void)xchg(&q->blk_trace, old_bt);
-		ret = -EBUSY;
+	ret = -EBUSY;
+	if (cmpxchg(&q->blk_trace, NULL, bt))
  		goto free_bt;
-	}
  
  	if (atomic_inc_return(&blk_probes_ref) == 1)
  		blk_register_tracepoints();
-- 
2.1.4

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[toc] | [prev] | [next] | [standalone]

#1258444 — Re: [PATCH v2] blktrace: re-write setting q->blk_trace

FromJeff Moyer <jmoyer@redhat.com>
Date2015-10-28 22:40 +0100
SubjectRe: [PATCH v2] blktrace: re-write setting q->blk_trace
Message-ID<qoGBP-84j-5@gated-at.bofh.it>
In reply to#1256438
Davidlohr Bueso <dave@stgolabs.net> writes:

> This is really about simplifying the double xchg patterns into
> a single cmpxchg, with the same logic. Other than the immediate
> cleanup, there are some subtleties this change deals with:
>
> (i) While the load of the old bt is fully ordered wrt everything,
> ie:
>
>       old_bt = xchg(&q->blk_trace, bt);             [barrier]
>       if (old_bt)
> 	     (void) xchg(&q->blk_trace, old_bt);    [barrier]
>
> blk_trace could still be changed between the xchg and the old_bt
> load. Note that this description is merely theoretical and afaict
> very small, but doing everything in a single context with cmpxchg
> closes this potential race.
>
> (ii) Ordering guarantees are obviously kept with cmpxchg.

Hi David,

The patch itself looks ok, but it doesn't seem to apply to a recent
kernel tree.  It appears as though it is white-space damaged.  Would you
mind re-sending it?

Thanks!
Jeff
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[toc] | [prev] | [next] | [standalone]

#1258959 — Re: [PATCH v2] blktrace: re-write setting q->blk_trace

FromDavidlohr Bueso <dave@stgolabs.net>
Date2015-10-29 20:20 +0100
SubjectRe: [PATCH v2] blktrace: re-write setting q->blk_trace
Message-ID<qp0TT-4iv-9@gated-at.bofh.it>
In reply to#1258444
>The patch itself looks ok, but it doesn't seem to apply to a recent
>kernel tree.  It appears as though it is white-space damaged.  Would you
>mind re-sending it?

Hmm sorry about that. I thought I had based it against that day's tip/master.
Anyway, here is v3 which is against tip/master as of 338e29ba93639138fafb9fb5ba946fd99a512aae.

Thanks,
Davidlohr

8<--------------------------------------------------------------------------------
From: Davidlohr Bueso <dave@stgolabs.net>
Date: Thu, 29 Oct 2015 12:13:24 -0700
Subject: [PATCH -tip v3] blktrace: re-write setting q->blk_trace

This is really about simplifying the double xchg patterns into
a single cmpxchg, with the same logic. Other than the immediate
cleanup, there are some subtleties this change deals with:

(i) While the load of the old bt is fully ordered wrt everything,
ie:

        old_bt = xchg(&q->blk_trace, bt);             [barrier]
        if (old_bt)
	     (void) xchg(&q->blk_trace, old_bt);    [barrier]

blk_trace could still be changed between the xchg and the old_bt
load. Note that this description is merely theoretical and afaict
very small, but doing everything in a single context with cmpxchg
closes this potential race.

(ii) Ordering guarantees are obviously kept with cmpxchg.

(iii) Gets rid of the hacky-by-nature (void)xchg pattern.

Signed-off-by: Davidlohr Bueso <dbueso@suse.de>
---
v3: rebased ontop of today's -tip.
     minor changelog addition.

  kernel/trace/blktrace.c | 16 +++++-----------
  1 file changed, 5 insertions(+), 11 deletions(-)

diff --git a/kernel/trace/blktrace.c b/kernel/trace/blktrace.c
index 90e72a0..e3a2618 100644
--- a/kernel/trace/blktrace.c
+++ b/kernel/trace/blktrace.c
@@ -437,7 +437,7 @@ int do_blk_trace_setup(struct request_queue *q, char *name, dev_t dev,
		       struct block_device *bdev,
		       struct blk_user_trace_setup *buts)
  {
-	struct blk_trace *old_bt, *bt = NULL;
+	struct blk_trace *bt = NULL;
	struct dentry *dir = NULL;
	int ret;

@@ -519,11 +519,8 @@ int do_blk_trace_setup(struct request_queue *q, char *name, dev_t dev,
	bt->trace_state = Blktrace_setup;

	ret = -EBUSY;
-	old_bt = xchg(&q->blk_trace, bt);
-	if (old_bt) {
-		(void) xchg(&q->blk_trace, old_bt);
+	if (cmpxchg(&q->blk_trace, NULL, bt))
		goto err;
-	}

	if (atomic_inc_return(&blk_probes_ref) == 1)
		blk_register_tracepoints();
@@ -1481,7 +1478,7 @@ static int blk_trace_remove_queue(struct request_queue *q)
  static int blk_trace_setup_queue(struct request_queue *q,
				 struct block_device *bdev)
  {
-	struct blk_trace *old_bt, *bt = NULL;
+	struct blk_trace *bt = NULL;
	int ret = -ENOMEM;

	bt = kzalloc(sizeof(*bt), GFP_KERNEL);
@@ -1497,12 +1494,9 @@ static int blk_trace_setup_queue(struct request_queue *q,

	blk_trace_setup_lba(bt, bdev);

-	old_bt = xchg(&q->blk_trace, bt);
-	if (old_bt != NULL) {
-		(void)xchg(&q->blk_trace, old_bt);
-		ret = -EBUSY;
+	ret = -EBUSY;
+	if (cmpxchg(&q->blk_trace, NULL, bt))
		goto free_bt;
-	}

	if (atomic_inc_return(&blk_probes_ref) == 1)
		blk_register_tracepoints();
--
2.1.4
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[toc] | [prev] | [next] | [standalone]

#1258964 — Re: [PATCH v2] blktrace: re-write setting q->blk_trace

FromJeff Moyer <jmoyer@redhat.com>
Date2015-10-29 20:40 +0100
SubjectRe: [PATCH v2] blktrace: re-write setting q->blk_trace
Message-ID<qp1dg-4pe-3@gated-at.bofh.it>
In reply to#1258959
Davidlohr Bueso <dave@stgolabs.net> writes:

>>The patch itself looks ok, but it doesn't seem to apply to a recent
>>kernel tree.  It appears as though it is white-space damaged.  Would you
>>mind re-sending it?
>
> Hmm sorry about that. I thought I had based it against that day's tip/master.
> Anyway, here is v3 which is against tip/master as of 338e29ba93639138fafb9fb5ba946fd99a512aae.

Thanks.

Reviewed-by: Jeff Moyer <jmoyer@redhat.com>


> 8<--------------------------------------------------------------------------------
> From: Davidlohr Bueso <dave@stgolabs.net>
> Date: Thu, 29 Oct 2015 12:13:24 -0700
> Subject: [PATCH -tip v3] blktrace: re-write setting q->blk_trace
>
> This is really about simplifying the double xchg patterns into
> a single cmpxchg, with the same logic. Other than the immediate
> cleanup, there are some subtleties this change deals with:
>
> (i) While the load of the old bt is fully ordered wrt everything,
> ie:
>
>        old_bt = xchg(&q->blk_trace, bt);             [barrier]
>        if (old_bt)
> 	     (void) xchg(&q->blk_trace, old_bt);    [barrier]
>
> blk_trace could still be changed between the xchg and the old_bt
> load. Note that this description is merely theoretical and afaict
> very small, but doing everything in a single context with cmpxchg
> closes this potential race.
>
> (ii) Ordering guarantees are obviously kept with cmpxchg.
>
> (iii) Gets rid of the hacky-by-nature (void)xchg pattern.
>
> Signed-off-by: Davidlohr Bueso <dbueso@suse.de>
> ---
> v3: rebased ontop of today's -tip.
>     minor changelog addition.
>
>  kernel/trace/blktrace.c | 16 +++++-----------
>  1 file changed, 5 insertions(+), 11 deletions(-)
>
> diff --git a/kernel/trace/blktrace.c b/kernel/trace/blktrace.c
> index 90e72a0..e3a2618 100644
> --- a/kernel/trace/blktrace.c
> +++ b/kernel/trace/blktrace.c
> @@ -437,7 +437,7 @@ int do_blk_trace_setup(struct request_queue *q, char *name, dev_t dev,
> 		       struct block_device *bdev,
> 		       struct blk_user_trace_setup *buts)
>  {
> -	struct blk_trace *old_bt, *bt = NULL;
> +	struct blk_trace *bt = NULL;
> 	struct dentry *dir = NULL;
> 	int ret;
>
> @@ -519,11 +519,8 @@ int do_blk_trace_setup(struct request_queue *q, char *name, dev_t dev,
> 	bt->trace_state = Blktrace_setup;
>
> 	ret = -EBUSY;
> -	old_bt = xchg(&q->blk_trace, bt);
> -	if (old_bt) {
> -		(void) xchg(&q->blk_trace, old_bt);
> +	if (cmpxchg(&q->blk_trace, NULL, bt))
> 		goto err;
> -	}
>
> 	if (atomic_inc_return(&blk_probes_ref) == 1)
> 		blk_register_tracepoints();
> @@ -1481,7 +1478,7 @@ static int blk_trace_remove_queue(struct request_queue *q)
>  static int blk_trace_setup_queue(struct request_queue *q,
> 				 struct block_device *bdev)
>  {
> -	struct blk_trace *old_bt, *bt = NULL;
> +	struct blk_trace *bt = NULL;
> 	int ret = -ENOMEM;
>
> 	bt = kzalloc(sizeof(*bt), GFP_KERNEL);
> @@ -1497,12 +1494,9 @@ static int blk_trace_setup_queue(struct request_queue *q,
>
> 	blk_trace_setup_lba(bt, bdev);
>
> -	old_bt = xchg(&q->blk_trace, bt);
> -	if (old_bt != NULL) {
> -		(void)xchg(&q->blk_trace, old_bt);
> -		ret = -EBUSY;
> +	ret = -EBUSY;
> +	if (cmpxchg(&q->blk_trace, NULL, bt))
> 		goto free_bt;
> -	}
>
> 	if (atomic_inc_return(&blk_probes_ref) == 1)
> 		blk_register_tracepoints();
> --
> 2.1.4
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[toc] | [prev] | [next] | [standalone]

#1258985 — Re: [PATCH v2] blktrace: re-write setting q->blk_trace

FromJens Axboe <axboe@kernel.dk>
Date2015-10-29 21:30 +0100
SubjectRe: [PATCH v2] blktrace: re-write setting q->blk_trace
Message-ID<qp1ZD-4UY-5@gated-at.bofh.it>
In reply to#1258959
On 10/30/2015 04:19 AM, Davidlohr Bueso wrote:
>
>> The patch itself looks ok, but it doesn't seem to apply to a recent
>> kernel tree.  It appears as though it is white-space damaged.  Would you
>> mind re-sending it?
>
> Hmm sorry about that. I thought I had based it against that day's
> tip/master.
> Anyway, here is v3 which is against tip/master as of
> 338e29ba93639138fafb9fb5ba946fd99a512aae.

Thanks, this is definitely cleaner. Your patch is still pretty mangled, 
though. I had to hand apply it. Please check the result:

http://git.kernel.dk/cgit/linux-block/commit/?h=for-4.4/core&id=cdea01b2bf98affb7e9c44530108a4a28535eee8

-- 
Jens Axboe

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[toc] | [prev] | [next] | [standalone]

#1258993 — Re: [PATCH v2] blktrace: re-write setting q->blk_trace

FromJens Axboe <axboe@kernel.dk>
Date2015-10-29 21:50 +0100
SubjectRe: [PATCH v2] blktrace: re-write setting q->blk_trace
Message-ID<qp2j0-51p-5@gated-at.bofh.it>
In reply to#1258985
On 10/30/2015 05:46 AM, Jeff Moyer wrote:
> Jens Axboe <axboe@kernel.dk> writes:
>
>> On 10/30/2015 04:19 AM, Davidlohr Bueso wrote:
>>>
>>>> The patch itself looks ok, but it doesn't seem to apply to a recent
>>>> kernel tree.  It appears as though it is white-space damaged.  Would you
>>>> mind re-sending it?
>>>
>>> Hmm sorry about that. I thought I had based it against that day's
>>> tip/master.
>>> Anyway, here is v3 which is against tip/master as of
>>> 338e29ba93639138fafb9fb5ba946fd99a512aae.
>>
>> Thanks, this is definitely cleaner. Your patch is still pretty
>> mangled, though. I had to hand apply it. Please check the result:
>
> Heh, and here I just assumed the problem was on my end.
>
>> http://git.kernel.dk/cgit/linux-block/commit/?h=for-4.4/core&id=cdea01b2bf98affb7e9c44530108a4a28535eee8
>
> That looks fine, except you're missing the 'R' in Reviewed-by.

e-viewed. Electronically viewed by jeff?

-- 
Jens Axboe

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[toc] | [prev] | [next] | [standalone]

#1259002 — Re: [PATCH v2] blktrace: re-write setting q->blk_trace

FromJeff Moyer <jmoyer@redhat.com>
Date2015-10-29 22:00 +0100
SubjectRe: [PATCH v2] blktrace: re-write setting q->blk_trace
Message-ID<qp2sG-567-15@gated-at.bofh.it>
In reply to#1258993
Jens Axboe <axboe@kernel.dk> writes:

> On 10/30/2015 05:46 AM, Jeff Moyer wrote:
>> Jens Axboe <axboe@kernel.dk> writes:
>>
>>> On 10/30/2015 04:19 AM, Davidlohr Bueso wrote:
>>>>
>>>>> The patch itself looks ok, but it doesn't seem to apply to a recent
>>>>> kernel tree.  It appears as though it is white-space damaged.  Would you
>>>>> mind re-sending it?
>>>>
>>>> Hmm sorry about that. I thought I had based it against that day's
>>>> tip/master.
>>>> Anyway, here is v3 which is against tip/master as of
>>>> 338e29ba93639138fafb9fb5ba946fd99a512aae.
>>>
>>> Thanks, this is definitely cleaner. Your patch is still pretty
>>> mangled, though. I had to hand apply it. Please check the result:
>>
>> Heh, and here I just assumed the problem was on my end.
>>
>>> http://git.kernel.dk/cgit/linux-block/commit/?h=for-4.4/core&id=cdea01b2bf98affb7e9c44530108a4a28535eee8
>>
>> That looks fine, except you're missing the 'R' in Reviewed-by.
>
> e-viewed. Electronically viewed by jeff?

Heh.  Well, that's not wrong!  ;-)
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[toc] | [prev] | [next] | [standalone]

#1258994 — Re: [PATCH v2] blktrace: re-write setting q->blk_trace

FromJeff Moyer <jmoyer@redhat.com>
Date2015-10-29 21:50 +0100
SubjectRe: [PATCH v2] blktrace: re-write setting q->blk_trace
Message-ID<qp2j0-51p-7@gated-at.bofh.it>
In reply to#1258985
Jens Axboe <axboe@kernel.dk> writes:

> On 10/30/2015 04:19 AM, Davidlohr Bueso wrote:
>>
>>> The patch itself looks ok, but it doesn't seem to apply to a recent
>>> kernel tree.  It appears as though it is white-space damaged.  Would you
>>> mind re-sending it?
>>
>> Hmm sorry about that. I thought I had based it against that day's
>> tip/master.
>> Anyway, here is v3 which is against tip/master as of
>> 338e29ba93639138fafb9fb5ba946fd99a512aae.
>
> Thanks, this is definitely cleaner. Your patch is still pretty
> mangled, though. I had to hand apply it. Please check the result:

Heh, and here I just assumed the problem was on my end.

> http://git.kernel.dk/cgit/linux-block/commit/?h=for-4.4/core&id=cdea01b2bf98affb7e9c44530108a4a28535eee8

That looks fine, except you're missing the 'R' in Reviewed-by.

Cheers,
Jeff
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[toc] | [prev] | [next] | [standalone]

#1259007 — Re: [PATCH v2] blktrace: re-write setting q->blk_trace

FromDavidlohr Bueso <dave@stgolabs.net>
Date2015-10-29 22:10 +0100
SubjectRe: [PATCH v2] blktrace: re-write setting q->blk_trace
Message-ID<qp2Cm-5oO-9@gated-at.bofh.it>
In reply to#1258985
On Fri, 30 Oct 2015, Jens Axboe wrote:

>Thanks, this is definitely cleaner. Your patch is still pretty 
>mangled, though. I had to hand apply it. Please check the result:
>
>http://git.kernel.dk/cgit/linux-block/commit/?h=for-4.4/core&id=cdea01b2bf98affb7e9c44530108a4a28535eee8

Hmm I'm not sure what I'm doing wrong with the patch. This is the way
I always send them through emacs... Sorry for the trouble, the commit
above looks good (except the already mentioned eviewed tag :).

Thanks,
Davidlohr
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[toc] | [prev] | [standalone]

Back to top | Article view | linux.kernel

csiph-web