From: Christoph Hellwig <hch@lst.de>
To: Shiyang Ruan <ruansy.fnst@cn.fujitsu.com>
Cc: y-goto@fujitsu.com, qi.fuli@fujitsu.com, snitzer@redhat.com,
linux-nvdimm@lists.01.org, rgoldwyn@suse.de,
darrick.wong@oracle.com, david@fromorbit.com,
linux-kernel@vger.kernel.org, linux-xfs@vger.kernel.org,
linux-mm@kvack.org, dm-devel@redhat.com,
linux-fsdevel@vger.kernel.org, dan.j.williams@intel.com,
hch@lst.de, agk@redhat.com
Subject: Re: [dm-devel] [PATCH v3 05/11] mm, fsdax: Refactor memory-failure handler for dax mapping
Date: Wed, 10 Feb 2021 14:33:47 +0100 [thread overview]
Message-ID: <20210210133347.GD30109@lst.de> (raw)
In-Reply-To: <20210208105530.3072869-6-ruansy.fnst@cn.fujitsu.com>
> +extern int mf_dax_mapping_kill_procs(struct address_space *mapping, pgoff_t index, int flags);
No nee for the extern, please avoid the overly long line.
> @@ -120,6 +121,13 @@ static int hwpoison_filter_dev(struct page *p)
> if (PageSlab(p))
> return -EINVAL;
>
> + if (pfn_valid(page_to_pfn(p))) {
> + if (is_device_fsdax_page(p))
> + return 0;
> + else
> + return -EINVAL;
> + }
> +
This looks odd. For one there is no need for an else after a return.
But more importantly page_mapping() as called below pretty much assumes
a valid PFN, so something is fishy in this function.
> + if (is_zone_device_page(p)) {
> + if (is_device_fsdax_page(p))
> + tk->addr = vma->vm_start +
> + ((pgoff - vma->vm_pgoff) << PAGE_SHIFT);
The arithmetics here scream for a common helper, I suspect there might
be other places that could use the same helper.
> +int mf_dax_mapping_kill_procs(struct address_space *mapping, pgoff_t index, int flags)
Overly long line. Also the naming scheme with the mf_ seems rather
unusual. Maybe dax_kill_mapping_procs? Also please add a kerneldoc
comment describing the function given that it exported.
--
dm-devel mailing list
dm-devel@redhat.com
https://www.redhat.com/mailman/listinfo/dm-devel
WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@lst.de>
To: Shiyang Ruan <ruansy.fnst@cn.fujitsu.com>
Cc: linux-kernel@vger.kernel.org, linux-xfs@vger.kernel.org,
linux-nvdimm@lists.01.org, linux-mm@kvack.org,
linux-fsdevel@vger.kernel.org, dm-devel@redhat.com,
darrick.wong@oracle.com, david@fromorbit.com, hch@lst.de,
agk@redhat.com, snitzer@redhat.com, rgoldwyn@suse.de,
qi.fuli@fujitsu.com, y-goto@fujitsu.com
Subject: Re: [PATCH v3 05/11] mm, fsdax: Refactor memory-failure handler for dax mapping
Date: Wed, 10 Feb 2021 14:33:47 +0100 [thread overview]
Message-ID: <20210210133347.GD30109@lst.de> (raw)
In-Reply-To: <20210208105530.3072869-6-ruansy.fnst@cn.fujitsu.com>
> +extern int mf_dax_mapping_kill_procs(struct address_space *mapping, pgoff_t index, int flags);
No nee for the extern, please avoid the overly long line.
> @@ -120,6 +121,13 @@ static int hwpoison_filter_dev(struct page *p)
> if (PageSlab(p))
> return -EINVAL;
>
> + if (pfn_valid(page_to_pfn(p))) {
> + if (is_device_fsdax_page(p))
> + return 0;
> + else
> + return -EINVAL;
> + }
> +
This looks odd. For one there is no need for an else after a return.
But more importantly page_mapping() as called below pretty much assumes
a valid PFN, so something is fishy in this function.
> + if (is_zone_device_page(p)) {
> + if (is_device_fsdax_page(p))
> + tk->addr = vma->vm_start +
> + ((pgoff - vma->vm_pgoff) << PAGE_SHIFT);
The arithmetics here scream for a common helper, I suspect there might
be other places that could use the same helper.
> +int mf_dax_mapping_kill_procs(struct address_space *mapping, pgoff_t index, int flags)
Overly long line. Also the naming scheme with the mf_ seems rather
unusual. Maybe dax_kill_mapping_procs? Also please add a kerneldoc
comment describing the function given that it exported.
_______________________________________________
Linux-nvdimm mailing list -- linux-nvdimm@lists.01.org
To unsubscribe send an email to linux-nvdimm-leave@lists.01.org
WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@lst.de>
To: Shiyang Ruan <ruansy.fnst@cn.fujitsu.com>
Cc: linux-kernel@vger.kernel.org, linux-xfs@vger.kernel.org,
linux-nvdimm@lists.01.org, linux-mm@kvack.org,
linux-fsdevel@vger.kernel.org, dm-devel@redhat.com,
darrick.wong@oracle.com, dan.j.williams@intel.com,
david@fromorbit.com, hch@lst.de, agk@redhat.com,
snitzer@redhat.com, rgoldwyn@suse.de, qi.fuli@fujitsu.com,
y-goto@fujitsu.com
Subject: Re: [PATCH v3 05/11] mm, fsdax: Refactor memory-failure handler for dax mapping
Date: Wed, 10 Feb 2021 14:33:47 +0100 [thread overview]
Message-ID: <20210210133347.GD30109@lst.de> (raw)
In-Reply-To: <20210208105530.3072869-6-ruansy.fnst@cn.fujitsu.com>
> +extern int mf_dax_mapping_kill_procs(struct address_space *mapping, pgoff_t index, int flags);
No nee for the extern, please avoid the overly long line.
> @@ -120,6 +121,13 @@ static int hwpoison_filter_dev(struct page *p)
> if (PageSlab(p))
> return -EINVAL;
>
> + if (pfn_valid(page_to_pfn(p))) {
> + if (is_device_fsdax_page(p))
> + return 0;
> + else
> + return -EINVAL;
> + }
> +
This looks odd. For one there is no need for an else after a return.
But more importantly page_mapping() as called below pretty much assumes
a valid PFN, so something is fishy in this function.
> + if (is_zone_device_page(p)) {
> + if (is_device_fsdax_page(p))
> + tk->addr = vma->vm_start +
> + ((pgoff - vma->vm_pgoff) << PAGE_SHIFT);
The arithmetics here scream for a common helper, I suspect there might
be other places that could use the same helper.
> +int mf_dax_mapping_kill_procs(struct address_space *mapping, pgoff_t index, int flags)
Overly long line. Also the naming scheme with the mf_ seems rather
unusual. Maybe dax_kill_mapping_procs? Also please add a kerneldoc
comment describing the function given that it exported.
next prev parent reply other threads:[~2021-02-10 13:34 UTC|newest]
Thread overview: 111+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-08 10:55 [dm-devel] [PATCH v3 00/11] fsdax: introduce fs query to support reflink Shiyang Ruan
2021-02-08 10:55 ` Shiyang Ruan
2021-02-08 10:55 ` Shiyang Ruan
2021-02-08 10:55 ` [dm-devel] [PATCH v3 01/11] pagemap: Introduce ->memory_failure() Shiyang Ruan
2021-02-08 10:55 ` Shiyang Ruan
2021-02-08 10:55 ` Shiyang Ruan
2021-02-10 13:20 ` [dm-devel] " Christoph Hellwig
2021-02-10 13:20 ` Christoph Hellwig
2021-02-10 13:20 ` Christoph Hellwig
2021-03-06 20:36 ` [dm-devel] " Dan Williams
2021-03-06 20:36 ` Dan Williams
2021-03-06 20:36 ` Dan Williams
2021-03-08 3:38 ` [dm-devel] " ruansy.fnst
2021-03-08 3:38 ` ruansy.fnst
2021-03-08 3:38 ` ruansy.fnst
2021-03-08 5:23 ` [dm-devel] " Dan Williams
2021-03-08 5:23 ` Dan Williams
2021-03-08 5:23 ` Dan Williams
2021-03-08 11:34 ` [dm-devel] " ruansy.fnst
2021-03-08 11:34 ` ruansy.fnst
2021-03-08 11:34 ` ruansy.fnst
2021-03-08 18:01 ` [dm-devel] " Dan Williams
2021-03-08 18:01 ` Dan Williams
2021-03-08 18:01 ` Dan Williams
2021-03-12 10:18 ` [dm-devel] " ruansy.fnst
2021-03-12 10:18 ` ruansy.fnst
2021-03-12 10:18 ` ruansy.fnst
2021-03-19 2:17 ` [dm-devel] " ruansy.fnst
2021-03-19 2:17 ` ruansy.fnst
2021-03-19 2:17 ` ruansy.fnst
2021-03-24 2:19 ` [dm-devel] " Dan Williams
2021-03-24 2:19 ` Dan Williams
2021-03-24 2:19 ` Dan Williams
2021-03-24 7:47 ` [dm-devel] " Christoph Hellwig
2021-03-24 7:47 ` Christoph Hellwig
2021-03-24 7:47 ` Christoph Hellwig
2021-03-24 16:37 ` [dm-devel] " Dan Williams
2021-03-24 16:37 ` Dan Williams
2021-03-24 16:37 ` Dan Williams
2021-03-24 17:39 ` [dm-devel] " Christoph Hellwig
2021-03-24 17:39 ` Christoph Hellwig
2021-03-24 17:39 ` Christoph Hellwig
2021-03-24 18:00 ` [dm-devel] " Dan Williams
2021-03-24 18:00 ` Dan Williams
2021-03-24 18:00 ` Dan Williams
2021-02-08 10:55 ` [dm-devel] [PATCH v3 02/11] blk: Introduce ->corrupted_range() for block device Shiyang Ruan
2021-02-08 10:55 ` Shiyang Ruan
2021-02-08 10:55 ` Shiyang Ruan
2021-02-10 13:21 ` [dm-devel] " Christoph Hellwig
2021-02-10 13:21 ` Christoph Hellwig
2021-02-10 13:21 ` Christoph Hellwig
2021-03-04 22:42 ` [dm-devel] " Darrick J. Wong
2021-03-04 22:42 ` Darrick J. Wong
2021-03-04 22:42 ` Darrick J. Wong
2021-03-05 6:10 ` [dm-devel] " Christoph Hellwig
2021-03-05 6:10 ` Christoph Hellwig
2021-03-05 6:10 ` Christoph Hellwig
2021-02-08 10:55 ` [dm-devel] [PATCH v3 03/11] fs: Introduce ->corrupted_range() for superblock Shiyang Ruan
2021-02-08 10:55 ` Shiyang Ruan
2021-02-08 10:55 ` Shiyang Ruan
2021-02-08 10:55 ` [dm-devel] [PATCH v3 04/11] block_dev: Introduce bd_corrupted_range() for block device Shiyang Ruan
2021-02-08 10:55 ` Shiyang Ruan
2021-02-08 10:55 ` Shiyang Ruan
2021-02-08 10:55 ` [dm-devel] [PATCH v3 05/11] mm, fsdax: Refactor memory-failure handler for dax mapping Shiyang Ruan
2021-02-08 10:55 ` Shiyang Ruan
2021-02-08 10:55 ` Shiyang Ruan
2021-02-10 13:33 ` Christoph Hellwig [this message]
2021-02-10 13:33 ` Christoph Hellwig
2021-02-10 13:33 ` Christoph Hellwig
2021-02-17 2:56 ` [dm-devel] " Ruan Shiyang
2021-02-17 2:56 ` Ruan Shiyang
2021-02-17 2:56 ` Ruan Shiyang
2021-02-18 8:32 ` [dm-devel] " Christoph Hellwig
2021-02-18 8:32 ` Christoph Hellwig
2021-02-18 8:32 ` Christoph Hellwig
2021-02-18 8:59 ` [dm-devel] " Ruan Shiyang
2021-02-18 8:59 ` Ruan Shiyang
2021-02-18 8:59 ` Ruan Shiyang
2021-03-16 3:21 ` [dm-devel] " zhong jiang
2021-03-16 3:21 ` zhong jiang
2021-03-16 3:21 ` zhong jiang
2021-03-17 3:46 ` [dm-devel] " ruansy.fnst
2021-03-17 3:46 ` ruansy.fnst
2021-03-17 3:46 ` ruansy.fnst
2021-02-08 10:55 ` [dm-devel] [PATCH v3 06/11] mm, pmem: Implement ->memory_failure() in pmem driver Shiyang Ruan
2021-02-08 10:55 ` Shiyang Ruan
2021-02-08 10:55 ` Shiyang Ruan
2021-02-10 13:41 ` [dm-devel] " Christoph Hellwig
2021-02-10 13:41 ` Christoph Hellwig
2021-02-10 13:41 ` Christoph Hellwig
2021-02-08 10:55 ` [dm-devel] [PATCH v3 07/11] pmem: Implement ->corrupted_range() for " Shiyang Ruan
2021-02-08 10:55 ` Shiyang Ruan
2021-02-08 10:55 ` Shiyang Ruan
2021-02-08 10:55 ` [dm-devel] [PATCH v3 08/11] dm: Introduce ->rmap() to find bdev offset Shiyang Ruan
2021-02-08 10:55 ` Shiyang Ruan
2021-02-08 10:55 ` Shiyang Ruan
2021-02-08 10:55 ` [dm-devel] [PATCH v3 09/11] md: Implement ->corrupted_range() Shiyang Ruan
2021-02-08 10:55 ` Shiyang Ruan
2021-02-08 10:55 ` Shiyang Ruan
2021-02-08 10:55 ` [dm-devel] [PATCH v3 10/11] xfs: Implement ->corrupted_range() for XFS Shiyang Ruan
2021-02-08 10:55 ` Shiyang Ruan
2021-02-08 10:55 ` Shiyang Ruan
2021-02-10 13:44 ` [dm-devel] " Christoph Hellwig
2021-02-10 13:44 ` Christoph Hellwig
2021-02-10 13:44 ` Christoph Hellwig
2021-02-08 10:55 ` [dm-devel] [PATCH v3 11/11] fs/dax: Remove useless functions Shiyang Ruan
2021-02-08 10:55 ` Shiyang Ruan
2021-02-08 10:55 ` Shiyang Ruan
2021-02-10 13:09 ` [dm-devel] " Christoph Hellwig
2021-02-10 13:09 ` Christoph Hellwig
2021-02-10 13:09 ` Christoph Hellwig
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210210133347.GD30109@lst.de \
--to=hch@lst.de \
--cc=agk@redhat.com \
--cc=dan.j.williams@intel.com \
--cc=darrick.wong@oracle.com \
--cc=david@fromorbit.com \
--cc=dm-devel@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-nvdimm@lists.01.org \
--cc=linux-xfs@vger.kernel.org \
--cc=qi.fuli@fujitsu.com \
--cc=rgoldwyn@suse.de \
--cc=ruansy.fnst@cn.fujitsu.com \
--cc=snitzer@redhat.com \
--cc=y-goto@fujitsu.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.