[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <YUxZZ/UHyRTt83pW@kroah.com>
Date: Thu, 23 Sep 2021 12:39:35 +0200
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: NeilBrown <neilb@...e.de>
Cc: Coly Li <colyli@...e.de>, linux-kernel@...r.kernel.org,
linux-block@...r.kernel.org, linux-raid@...r.kernel.org,
nvdimm@...ts.linux.dev, antlists@...ngman.org.uk,
Dan Williams <dan.j.williams@...el.com>,
Hannes Reinecke <hare@...e.de>, Jens Axboe <axboe@...nel.dk>,
Richard Fan <richard.fan@...e.com>,
Vishal L Verma <vishal.l.verma@...el.com>, rafael@...nel.org
Subject: Re: Too large badblocks sysfs file (was: [PATCH v3 0/7] badblocks
improvement for multiple bad block ranges)
On Thu, Sep 23, 2021 at 08:09:21PM +1000, NeilBrown wrote:
> On Thu, 23 Sep 2021, Coly Li wrote:
> > Hi all the kernel gurus, and folks in mailing lists,
> >
> > This is a question about exporting 4KB+ text information via sysfs
> > interface. I need advice on how to handle the problem.
>
> Why do you think there is a problem?
> As documented in Documentation/admin-guide/md.rst, the truncation at 1
> page is expected and by design.
Ah, shouldn't that info also be in Documentation/ABI/ so that others can
easily find it?
thanks,
greg k-h
Powered by blists - more mailing lists