linux-kernel - Re: [RFC PATCH v2 0/6] fsdax: introduce fs query to support reflink

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Tue, 15 Dec 2020 19:58:36 +0800
From:   Ruan Shiyang <ruansy.fnst@...fujitsu.com>
To:     Jane Chu <jane.chu@...cle.com>, <linux-kernel@...r.kernel.org>,
        <linux-xfs@...r.kernel.org>, <linux-nvdimm@...ts.01.org>,
        <linux-mm@...ck.org>
CC:     <linux-fsdevel@...r.kernel.org>, <linux-raid@...r.kernel.org>,
        <darrick.wong@...cle.com>, <dan.j.williams@...el.com>,
        <david@...morbit.com>, <hch@....de>, <song@...nel.org>,
        <rgoldwyn@...e.de>, <qi.fuli@...itsu.com>, <y-goto@...itsu.com>
Subject: Re: [RFC PATCH v2 0/6] fsdax: introduce fs query to support reflink

Hi Jane

On 2020/12/15 上午4:58, Jane Chu wrote:
> Hi, Shiyang,
> 
> On 11/22/2020 4:41 PM, Shiyang Ruan wrote:
>> This patchset is a try to resolve the problem of tracking shared page
>> for fsdax.
>>
>> Change from v1:
>>    - Intorduce ->block_lost() for block device
>>    - Support mapped device
>>    - Add 'not available' warning for realtime device in XFS
>>    - Rebased to v5.10-rc1
>>
>> This patchset moves owner tracking from dax_assocaite_entry() to pmem
>> device, by introducing an interface ->memory_failure() of struct
>> pagemap.  The interface is called by memory_failure() in mm, and
>> implemented by pmem device.  Then pmem device calls its ->block_lost()
>> to find the filesystem which the damaged page located in, and call
>> ->storage_lost() to track files or metadata assocaited with this page.
>> Finally we are able to try to fix the damaged data in filesystem and do
> 
> Does that mean clearing poison? if so, would you mind to elaborate 
> specifically which change does that?

Recovering data for filesystem (or pmem device) has not been done in 
this patchset...  I just triggered the handler for the files sharing the 
corrupted page here.


--
Thanks,
Ruan Shiyang.

> 
> Thanks!
> -jane
> 
>> other necessary processing, such as killing processes who are using the
>> files affected.
> 
>