Re: [PATCH v6 4/6] blktrace: annotate required lock on do_blk_trace_setup()

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

To: Luis Chamberlain <mcgrof@xxxxxxxxxx>
Subject: Re: [PATCH v6 4/6] blktrace: annotate required lock on do_blk_trace_setup()
From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
Date: Tue, 9 Jun 2020 07:18:32 -0700
Cc: axboe@xxxxxxxxx, viro@xxxxxxxxxxxxxxxxxx, bvanassche@xxxxxxx, gregkh@xxxxxxxxxxxxxxxxxxx, rostedt@xxxxxxxxxxx, mingo@xxxxxxxxxx, jack@xxxxxxx, ming.lei@xxxxxxxxxx, nstange@xxxxxxx, akpm@xxxxxxxxxxxxxxxxxxxx, mhocko@xxxxxxxx, yukuai3@xxxxxxxxxx, martin.petersen@xxxxxxxxxx, jejb@xxxxxxxxxxxxx, linux-block@xxxxxxxxxxxxxxx, linux-fsdevel@xxxxxxxxxxxxxxx, linux-mm@xxxxxxxxx, linux-kernel@xxxxxxxxxxxxxxx
In-reply-to: <20200608170127.20419-5-mcgrof@kernel.org>
References: <20200608170127.20419-1-mcgrof@kernel.org> <20200608170127.20419-5-mcgrof@kernel.org>

On Mon, Jun 08, 2020 at 05:01:24PM +0000, Luis Chamberlain wrote:
> Ensure it is clear which lock is required on do_blk_trace_setup().
> 
> Suggested-by: Bart Van Assche <bvanassche@xxxxxxx>
> Signed-off-by: Luis Chamberlain <mcgrof@xxxxxxxxxx>

Looks good,

Reviewed-by: Christoph Hellwig <hch@xxxxxx>

References:
- [PATCH v6 0/8] block: fix blktrace debugfs use after free
  - From: Luis Chamberlain
- [PATCH v6 4/6] blktrace: annotate required lock on do_blk_trace_setup()
  - From: Luis Chamberlain

Prev by Date: [RFC v3 01/10] mm/damon: Use vm-independent address range concept
Next by Date: [RFC v3 00/10] DAMON: Support Access Monitoring of Any Address Space Including Physical Memory
Previous by thread: [PATCH v6 4/6] blktrace: annotate required lock on do_blk_trace_setup()
Next by thread: Re: [PATCH v6 4/6] blktrace: annotate required lock on do_blk_trace_setup()
Index(es):
- Date
- Thread

[Index of Archives] [Linux ARM Kernel] [Linux ARM] [Linux Omap] [Fedora ARM] [IETF Annouce] [Bugtraq] [Linux OMAP] [Linux MIPS] [eCos] [Asterisk Internet PBX] [Linux API]