On 03/12/2020 17:15, Coly Li wrote:
This patch is an initial effort to improve badblocks_set() for setting
bad blocks range when it covers multiple already set bad ranges in the
bad blocks table, and to do it as fast as possible.
Is this your patch, or submitted as part of the bug report?
On Fri, Dec 18, 2020 at 11:46 PM Leizhen (ThunderTown)
wrote:
>
>
>
> On 2020/12/19 10:41, Dan Williams wrote:
> > There are multiple locations that open-code the release of the last
> > range in a device-dax instance. Consolidate this into a new
> > dev_dax_trim_range() helper.
> >
> > This also
On 12/9/20 10:59 AM, Joao Martins wrote:
> On 12/8/20 7:29 PM, Jason Gunthorpe wrote:
>> On Tue, Dec 08, 2020 at 05:29:00PM +, Joao Martins wrote:
>>
>>> static void __ib_umem_release(struct ib_device *dev, struct ib_umem *umem,
>>> int dirty)
>>> {
>>> + bool make_dirty = umem->writable
On 12/19/20 2:06 AM, John Hubbard wrote:
> On 12/17/20 12:05 PM, Jason Gunthorpe wrote:
>> On Thu, Dec 17, 2020 at 07:05:37PM +, Joao Martins wrote:
No reason not to fix set_page_dirty_lock() too while you are here.
>>>
>>> The wack of atomics you mentioned earlier you referred to, I
A new ndctl release is available[1].
Highlights include support for the new device-dax subdivision
functionality added in Linux in v5.10, including ways to create smaller
devdax devices using daxctl/libdaxctl, as well as creating, listing, and
restoring from a config dump, 'mappings' on these
Commit 14eacf0d694a ("Rework license identification") reworked license
identification, making the files listed in ndctl.spec.in for %license
obsolete. This updates those sections in the RPM spec to match the
current layout of license files.
Fixes: 14eacf0d694a ("Rework license identification")
On Fri, 2020-12-18 at 02:14 +, Joao Martins wrote:
> Hey,
>
> This series adds support for:
>
> 1) Listing mappings when passing -M to ´daxctl list´. These are ommited
> by default.
>
> 2) Iteration APIs for the mappings.
>
> 3) Allow passing an input JSON file with the manually
Swap the calling sequence of krealloc() and __request_region(), call the
latter first. In this way, the value of dev_dax->nr_range does not need to
be considered when __request_region() failed.
Signed-off-by: Zhen Lei
---
drivers/dax/bus.c | 20 ++--
1 file changed, 6
v1 --> v2:
In v1, I use the "goto" statement to merge two identical __release_region()
calls.
However, the new patch https://lkml.org/lkml/2020/12/18/735 deletes one of
them, the
"goto" becomes worthless. So when krealloc() failed, directly call
__release_region()
and return error code.
Zhen
