[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAB=NE6X-RaP2Qbfi5J23EdsVDTUys6AuYT7g6QDtCt=d5-GZ9w@mail.gmail.com>
Date: Fri, 15 May 2020 19:39:53 -0600
From: Luis Chamberlain <mcgrof@...nel.org>
To: Bart Van Assche <bvanassche@....org>
Cc: Jens Axboe <axboe@...nel.dk>, Al Viro <viro@...iv.linux.org.uk>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Steven Rostedt <rostedt@...dmis.org>,
Ingo Molnar <mingo@...hat.com>, Jan Kara <jack@...e.cz>,
Ming Lei <ming.lei@...hat.com>,
Nicolai Stange <nstange@...e.de>,
Andrew Morton <akpm@...ux-foundation.org>,
Michal Hocko <mhocko@...e.com>, yu kuai <yukuai3@...wei.com>,
linux-block@...r.kernel.org,
Linux FS Devel <linux-fsdevel@...r.kernel.org>,
linux-mm <linux-mm@...ck.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v4 4/5] blktrace: break out of blktrace setup on
concurrent calls
On Mon, May 11, 2020 at 7:39 AM Luis Chamberlain <mcgrof@...nel.org> wrote:
>
> On Sat, May 09, 2020 at 06:09:38PM -0700, Bart Van Assche wrote:
> > How about using the block device name instead of the partition name in
> > the error message since the concurrency context is the block device and
> > not the partition?
>
> blk device argument can be NULL here. sg-generic is one case.
I'm going to add a comment about this, as it is easily forgotten.
Luis
Powered by blists - more mailing lists