nmap'ed file as input:
pfnmap -r pfnmap.madvise_disallowed -- randfile.txt
TAP version 13
1..1
# Starting 1 tests from 1 test cases.
# RUN pfnmap.madvise_disallowed ...
# SKIP Invalid file: 'randfile.txt'. Not pfnmap'ed
Signe
test_prctl_fork(void)
child_pid = fork();
if (!child_pid) {
+ init_global_file_handles();
Would this leave fd in parent as orphan?
Probably yes, but only until the child quits, so likely we don't care.
--
Cheers,
David / dhildenb
can factor it into vm_util.h and use it here.
That sounds reasonable to me.
--
Cheers,
David / dhildenb
ething unrelated, like the vdso or
something odd like that)
We have a helper in vm_util.c that might be useful: __get_smap_entry()
We also have a check_vmflag_io() in there. So likely you want to add a
helper check_vmflag_pfnmap().
Nothing else jumped at me, except that phys_addr might be better called
something like "offset" now.
--
Cheers,
David / dhildenb
Linus
>
--
-Open up your eyes, open up your mind, open up your code ---
/ Dr. David Alan Gilbert| Running GNU/Linux | Happy \
\dave @ treblig.org | | In Hex /
\ _|_ http://www.treblig.org |___/
dev/mem. That doesn't make any sense with what you are doing here.
If we are not provided /dev/mem, you should probably try mapping offset
0 of the file.
--
Cheers,
David / dhildenb
Connolly
Signed-off-by: David Heidelberg
---
drivers/input/rmi4/rmi_f01.c | 14 ++
1 file changed, 14 insertions(+)
diff --git a/drivers/input/rmi4/rmi_f01.c b/drivers/input/rmi4/rmi_f01.c
index
47be64284b25ede8103ada86d6b58fd3a26976bb..2278e9b6a920774b07ec9dd3e452cedc69469be8
100644
unaligned address.
Signed-off-by: Kaustabh Chakraborty
Signed-off-by: Caleb Connolly
Signed-off-by: David Heidelberg
---
drivers/input/rmi4/rmi_driver.c | 20 +---
1 file changed, 13 insertions(+), 7 deletions(-)
diff --git a/drivers/input/rmi4/rmi_driver.c b/drivers/input/rmi4
nolly
Signed-off-by: David Heidelberg
---
drivers/input/rmi4/rmi_f55.c | 5 +
1 file changed, 5 insertions(+)
diff --git a/drivers/input/rmi4/rmi_f55.c b/drivers/input/rmi4/rmi_f55.c
index
488adaca4dd00482cd1106d813b32871092c83a0..776c915b82e72b8a6eb5ec701cce9059c87089c4
100644
--- a/drivers/
IC)
rmi4_i2c 12-0020: read 6 bytes at 0x00e3: 0 (2c 23 0d 06 00 00)
Signed-off-by: Kaustabh Chakraborty
[codeflow adjustments, checkpatch fixes, wording]
Signed-off-by: Caleb Connolly
Co-developed-by: David Heidelberg
Signed-off-by: David Heidelberg
---
drivers/input/rmi4/rmi_driver.c | 62
t, so these fallback values are offered as an alternative to the error
path when register descriptors aren't available.
Signed-off-by: Kaustabh Chakraborty
[changes for readability / codeflow, checkpatch fixes]
Signed-off-by: Caleb Connolly
Signed-off-by: David Heidelberg
---
drivers/
v1:
https://lore.kernel.org/r/20230929-caleb-rmi4-quirks-v1-0-cc3c703f0...@linaro.org
---
Caleb Connolly (1):
Input: synaptics-rmi4 - handle duplicate/unknown PDT entries
David Heidelberg (1):
dt-bindings: input: syna,rmi4: Document syna,rmi4-s3706b
Kaustabh Chakraborty (5):
In
From: David Heidelberg
Mostly irrelevant for authentic Synaptics touchscreens, but very important
for applying workarounds to cheap TS knockoffs.
These knockoffs work well with the downstream driver, and since the user
has no way to distinguish them, later in this patch set, we introduce
us 6T (original parts):
manufacturer: Synaptics, product: S3706B, fw id: 2852315
Co-developed-by: Kaustabh Chakraborty
Signed-off-by: Kaustabh Chakraborty
Signed-off-by: Caleb Connolly
Co-developed-by: David Heidelberg
Signed-off-by: David Heidelberg
---
drivers/input/rmi4/rmi_driver.c
g/kunit/kunit.py run` should function
out-of-the-box on most non-x86 architectures, assuming qemu is installed.
Signed-off-by: David Gow
---
tools/testing/kunit/kunit.py | 2 +-
tools/testing/kunit/kunit_kernel.py| 43 --
tools/testing/kunit/kunit_tool_te
esent. Instead, have kunit.py
look for a check_dependencies function, and call it if present only when
the architecture config is being used.
This is necessary for future changes which enumerate or automatically
select an architecture.
Signed-off-by: David Gow
---
tools/testing/kunit/kunit_kern
On 18.07.25 14:43, Lorenzo Stoakes wrote:
On Thu, Jul 17, 2025 at 10:03:44PM +0200, David Hildenbrand wrote:
On 17.07.25 21:55, Lorenzo Stoakes wrote:
On Thu, Jul 17, 2025 at 08:51:51PM +0100, Lorenzo Stoakes wrote:
@@ -721,37 +772,21 @@ struct page *vm_normal_page_pmd(struct vm_area_struct
I can never remember whether --raw_output takes 'all' or 'full'. No
reason we can't support both.
For the record, 'all' is the recommended, documented option.
Signed-off-by: David Gow
---
tools/testing/kunit/kunit.py | 4 ++--
1 file changed, 2 insertions(+),
BVgOS=AKHSfifp0S68K3jgNZAkALBr=7iFb=niryg5wdxj...@mail.gmail.com/
> [1]
> Signed-off-by: Miguel Ojeda
> ---
With my (biased) KUnit hat on, this looks good to me.
_Maybe_ it's worth updating Documentation/rust/testing.rst, though it
already says these are "mostly used for testin
On 23.07.25 11:50, Colin Ian King wrote:
There is a spelling mistake in ksft_test_result_fail messages. Fix them.
Signed-off-by: Colin Ian King
---
Acked-by: David Hildenbrand
--
Cheers,
David / dhildenb
On 23.07.25 01:07, Sean Christopherson wrote:
On Tue, Jul 22, 2025, David Hildenbrand wrote:
On 22.07.25 16:45, Sean Christopherson wrote:
On Tue, Jul 22, 2025, David Hildenbrand wrote:
Just to clarify: this is based on Fuad's stage 1 and should probably still be
tagged "RFC" u
On 22.07.25 16:45, Sean Christopherson wrote:
On Tue, Jul 22, 2025, David Hildenbrand wrote:
Just to clarify: this is based on Fuad's stage 1 and should probably still be
tagged "RFC" until stage-1 is finally upstream.
(I was hoping stage-1 would go upstream in 6.17, but I am
, which are not supported for guest_memfd as it is unmovable.
Suggested-by: David Hildenbrand
Signed-off-by: Shivank Garg
---
Acked-by: David Hildenbrand
--
Cheers,
David / dhildenb
eviewed-by: David Hildenbrand
--
Cheers,
David / dhildenb
cated NUMA policy specified by VMM.
All existing users pass NULL maintaining current behavior.
Reviewed-by: Pankaj Gupta
Reviewed-by: Vlastimil Babka
Signed-off-by: Matthew Wilcox (Oracle)
Signed-off-by: Shivank Garg
---
Reviewed-by: David Hildenbrand
--
Cheers,
David / dhildenb
+&kvm_gmem_fops);
+ if (IS_ERR(file)) {
+ err = PTR_ERR(file);
+ goto err_put_inode;
+ }
+
+ file->f_flags |= O_LARGEFILE;
+ file->private_data = priv;
+
Nothing else jumped at me.
--
Cheers,
David / dhildenb
2025 +
fs: export anon_inode_make_secure_inode() and fix secretmem LSM bypass
was merged with the kvm export
EXPORT_SYMBOL_GPL_FOR_MODULES(anon_inode_make_secure_inode, "kvm");
I thought I commented that this is something to done separately and not really
"fix&quo
if (unlikely(!ok))
Do you even need 'ok' at all, just:
if (unlikely(!__cvdso_clock_gettime_common(vd, clock, &ts)))
> return clock_gettime32_fallback(clock, res);
>
> - /* For ret == 0 */
> + /* For ok == true */
> res->tv_sec = ts.tv_sec;
> res->tv_nsec = ts.tv_nsec;
>
> - return ret;
> + return 0;
> }
>
> static __maybe_unused int
David
ts of 'buffer' to/from 'void *' are fine (and not needed),
casts to/from 'integer_type *' are definitely problematic.
And 'random' casts of integer values could easily hide real bugs
and most just aren't needed.
Although you might want the compiler to make the result of
'u64_var & 0xffu' 'unsigned int'.
David
t; typeof(*__pu_ptr) __pu_val = (typeof(*__pu_ptr))(x);\
You need to align the \
Plausibly possible by post-processing the diffs.
David
On 18.07.25 12:47, Lorenzo Stoakes wrote:
On Thu, Jul 17, 2025 at 10:14:33PM +0200, David Hildenbrand wrote:
On 17.07.25 22:03, Lorenzo Stoakes wrote:
On Thu, Jul 17, 2025 at 01:52:11PM +0200, David Hildenbrand wrote:
Let's introduce vm_normal_page_pud(), which ends up being fairly s
In a MIXEDMAP that will get refcounted. Not sure if there are users that
use VM_IO in a MIXEDMAP, I would assume so but didn't check.
So VM_IO doesn't really interact with vm_normal_page(), really. It's all
about PFNMAP and MIXEDMAP.
--
Cheers,
David / dhildenb
On 18.07.25 12:41, Lorenzo Stoakes wrote:
On Thu, Jul 17, 2025 at 10:31:28PM +0200, David Hildenbrand wrote:
On 17.07.25 20:29, Lorenzo Stoakes wrote:
On Thu, Jul 17, 2025 at 01:52:08PM +0200, David Hildenbrand wrote:
The huge zero folio is refcounted (+mapcounted -- is that a word
On 18.07.25 09:59, Demi Marie Obenour wrote:
On 7/18/25 03:44, David Hildenbrand wrote:
On 18.07.25 00:06, Demi Marie Obenour wrote:
On 7/17/25 07:52, David Hildenbrand wrote:
print_bad_pte() looks like something that should actually be a WARN
or similar, but historically it apparently has
On 18.07.25 00:06, Demi Marie Obenour wrote:
On 7/17/25 07:52, David Hildenbrand wrote:
print_bad_pte() looks like something that should actually be a WARN
or similar, but historically it apparently has proven to be useful to
detect corruption of page tables even on production systems -- report
On 18.07.25 04:41, Ye Liu wrote:
From: Ye Liu
Replace repeated (20 - PAGE_SHIFT) calculations with standard macros:
- MB_TO_PAGES(mb)converts MB to page count
- PAGES_TO_MB(pages) converts pages to MB
No functional change.
Signed-off-by: Ye Liu
---
Acked-by: David Hildenbrand
On 17.07.25 20:29, Lorenzo Stoakes wrote:
On Thu, Jul 17, 2025 at 01:52:08PM +0200, David Hildenbrand wrote:
The huge zero folio is refcounted (+mapcounted -- is that a word?)
differently than "normal" folios, similarly (but different) to the ordinary
shared zeropage.
Yeah, I sort
On 17.07.25 22:03, Lorenzo Stoakes wrote:
On Thu, Jul 17, 2025 at 01:52:11PM +0200, David Hildenbrand wrote:
Let's introduce vm_normal_page_pud(), which ends up being fairly simple
because of our new common helpers and there not being a PUD-sized zero
folio.
Use vm_normal_page_pud
pte: The PTE.
+ *
+ * Get the "struct folio" associated with a PTE. See vm_normal_page_pfn()
+ * for details.
+ *
+ * Return: Returns the "struct folio" if this is a "normal" mapping. Returns
+ *NULL if this is a "special" mapping.
+ */
Nice to add a comment, but again feels weird to have the whole explanation in
vm_normal_page_pfn() but then to invoke vm_normal_page()..
You want people to do pointer chasing to find what they are looking for? :)
--
Cheers,
David / dhildenb
ould have to provide a "level" argument, and did not
convince myself yet that that is a good idea at this point.
--
Cheers,
David / dhildenb
that apparently
it can be useful in the real world.
Signed-off-by: David Hildenbrand
---
mm/memory.c | 120
1 file changed, 94 insertions(+), 26 deletions(-)
diff --git a/mm/memory.c b/mm/memory.c
index 173eb6267e0ac..08d16ed7b4cc7 1
mentation, and add a comment in the code where XEN ends
up performing the pte_mkspecial() through a hypercall. More details can
be found in commit 923b2919e2c3 ("xen/gntdev: mark userspace PTEs as
special on x86 PV guests").
Cc: David Vrabel
Reviewed-by: Oscar Salvador
Signed-off-by
().
Add kerneldoc for all involved functions.
No functional change intended.
Reviewed-by: Oscar Salvador
Signed-off-by: David Hildenbrand
---
mm/memory.c | 183 +++-
1 file changed, 109 insertions(+), 74 deletions(-)
diff --git a/mm/memory.
ucing vm_normal_folio_pud() until really used.
Reviewed-by: Oscar Salvador
Signed-off-by: David Hildenbrand
---
include/linux/mm.h | 2 ++
mm/memory.c| 27 +++
mm/pagewalk.c | 20 ++--
3 files changed, 39 insertions(+), 10 deletions(-)
diff --git a/in
01233f5867
[ 77.944077] addr:7fd84bb1c000 vm_flags:08100071 anon_vma: ...
[ 77.945186] pgd:10a89f067 p4d:10a89f067 pud:10e5a2067 pmd:105327067
Not using pgdp_get(), because that does not work properly on some arm
configs where pgd_t is an array. Note that we are dumping all levels
even
vm_normal_page().
While at it, update the doc regarding the shared zero folios.
Reviewed-by: Oscar Salvador
Signed-off-by: David Hildenbrand
---
mm/huge_memory.c | 5 -
mm/memory.c | 14 +-
2 files changed, 13 insertions(+), 6 deletions(-)
diff --git a/mm/huge_memory.c b/m
ng to insert a PMD
mapping a folio through dax_fault_iter()->vmf_insert_folio_pmd().
So, it sounds reasonable to not handle huge zero folios differently
to inserting PMDs mapping folios when there already is something mapped.
Reviewed-by: Alistair Popple
Signed-off-by: David Hildenbran
shared zeropage.
For now, the huge zero folio is not marked as special yet, although
vm_normal_page_pmd() really wants to treat it as special. We'll change
that next.
Reviewed-by: Oscar Salvador
Signed-off-by: David Hildenbrand
---
mm/huge_memory.c | 8 +---
1 file changed, 5 inser
Let's clean it all further up.
No functional change intended.
Reviewed-by: Oscar Salvador
Reviewed-by: Alistair Popple
Signed-off-by: David Hildenbrand
---
mm/huge_memory.c | 36 +---
1 file changed, 13 insertions(+), 23 deletions(-)
diff --git
Let's clean it all further up.
No functional change intended.
Reviewed-by: Oscar Salvador
Reviewed-by: Alistair Popple
Signed-off-by: David Hildenbrand
---
mm/huge_memory.c | 72
1 file changed, 24 insertions(+), 48 deletions(-)
diff --
l Hocko
Cc: Zi Yan
Cc: Baolin Wang
Cc: Nico Pache
Cc: Ryan Roberts
Cc: Dev Jain
Cc: Barry Song
Cc: Jann Horn
Cc: Pedro Falcato
Cc: Hugh Dickins
Cc: Oscar Salvador
Cc: Lance Yang
David Hildenbrand (9):
mm/huge_memory: move more common code into insert_pmd()
mm/huge_memory: mov
On 17.07.25 10:38, Alistair Popple wrote:
On Tue, Jul 15, 2025 at 03:23:45PM +0200, David Hildenbrand wrote:
Let's convert to vmf_insert_folio_pmd().
There is a theoretical change in behavior: in the unlikely case there is
already something mapped, we'll now still call trace_dax_pmd
On 17.07.25 00:27, Andrew Morton wrote:
On Wed, 16 Jul 2025 10:47:29 +0200 David Hildenbrand wrote:
However the series rejects due to the is_huge_zero_pmd ->
is_huge_zero_pfn changes in Luiz's "mm: introduce snapshot_page() v3"
series, so could we please have a redo agai
Example Command: proc-maps-race -d 10
Signed-off-by: Suren Baghdasaryan
Why is this selftest not making use of any kselftest framework?
I'm sure there is a very good reason :)
Reading assert() feels very weird compared to other selftests.
--
Cheers,
David / dhildenb
ed-by: Vlastimil Babka
---
Acked-by: David Hildenbrand
--
Cheers,
David / dhildenb
dy in.
--
Cheers,
David / dhildenb
On 16.07.25 01:31, Andrew Morton wrote:
On Tue, 15 Jul 2025 15:23:41 +0200 David Hildenbrand wrote:
Based on mm/mm-new. I dropped the CoW PFNMAP changes for now, still
working on a better way to sort all that out cleanly.
Cleanup and unify vm_normal_page_*() handling, also marking the
huge
On 15.07.25 15:23, David Hildenbrand wrote:
print_bad_pte() looks like something that should actually be a WARN
or similar, but historically it apparently has proven to be useful to
detect corruption of page tables even on production systems -- report
the issue and keep the system running to
01233f5867
[ 77.944077] addr:7fd84bb1c000 vm_flags:08100071 anon_vma: ...
[ 77.945186] pgd:10a89f067 p4d:10a89f067 pud:10e5a2067 pmd:105327067
Signed-off-by: David Hildenbrand
---
mm/memory.c | 120
1 file changed, 94 insertions(+), 2
Let's clean it all further up.
No functional change intended.
Reviewed-by: Oscar Salvador
Reviewed-by: Alistair Popple
Signed-off-by: David Hildenbrand
---
mm/huge_memory.c | 72
1 file changed, 24 insertions(+), 48 deletions(-)
diff --
().
Add kerneldoc for all involved functions.
No functional change intended.
Signed-off-by: David Hildenbrand
---
mm/memory.c | 183 +++-
1 file changed, 109 insertions(+), 74 deletions(-)
diff --git a/mm/memory.c b/mm/memory.c
index 00ee0df020503..d5f
ucing vm_normal_folio_pud() until really used.
Signed-off-by: David Hildenbrand
---
include/linux/mm.h | 2 ++
mm/memory.c| 27 +++
mm/pagewalk.c | 20 ++--
3 files changed, 39 insertions(+), 10 deletions(-)
diff --git a/include/linux/mm.h b/include/
vm_normal_page().
While at it, update the doc regarding the shared zero folios.
Reviewed-by: Oscar Salvador
Signed-off-by: David Hildenbrand
---
mm/huge_memory.c | 5 -
mm/memory.c | 14 +-
2 files changed, 13 insertions(+), 6 deletions(-)
diff --git a/mm/huge_memory.c b/m
ng to insert a PMD
mapping a folio through dax_fault_iter()->vmf_insert_folio_pmd().
So, it sounds reasonable to not handle huge zero folios differently
to inserting PMDs mapping folios when there already is something mapped.
Signed-off-by: David Hildenbran
mentation, and add a comment in the code where XEN ends
up performing the pte_mkspecial() through a hypercall. More details can
be found in commit 923b2919e2c3 ("xen/gntdev: mark userspace PTEs as
special on x86 PV guests").
Cc: David Vrabel
Signed-off-by: David Hildenbrand
---
drivers
shared zeropage.
For now, the huge zero folio is not marked as special yet, although
vm_normal_page_pmd() really wants to treat it as special. We'll change
that next.
Reviewed-by: Oscar Salvador
Signed-off-by: David Hildenbrand
---
mm/huge_memory.c | 8 +---
1 file changed, 5 inser
Let's clean it all further up.
No functional change intended.
Reviewed-by: Oscar Salvador
Reviewed-by: Alistair Popple
Signed-off-by: David Hildenbrand
---
mm/huge_memory.c | 36 +---
1 file changed, 13 insertions(+), 23 deletions(-)
diff --git
a
Cc: Mike Rapoport
Cc: Suren Baghdasaryan
Cc: Michal Hocko
Cc: Zi Yan
Cc: Baolin Wang
Cc: Nico Pache
Cc: Ryan Roberts
Cc: Dev Jain
Cc: Barry Song
Cc: Jann Horn
Cc: Pedro Falcato
Cc: Hugh Dickins
Cc: Oscar Salvador
Cc: Lance Yang
David Hildenbrand (9):
mm/huge_memory: move mor
unaligned address.
Signed-off-by: Kaustabh Chakraborty
Signed-off-by: Caleb Connolly
Signed-off-by: David Heidelberg
---
drivers/input/rmi4/rmi_driver.c | 20 +---
1 file changed, 13 insertions(+), 7 deletions(-)
diff --git a/drivers/input/rmi4/rmi_driver.c b/drivers/input/rmi4
t, so these fallback values are offered as an alternative to the error
path when register descriptors aren't available.
Signed-off-by: Kaustabh Chakraborty
[changes for readability / codeflow, checkpatch fixes]
Signed-off-by: Caleb Connolly
Signed-off-by: David Heidelberg
---
drivers/
nolly
Signed-off-by: David Heidelberg
---
drivers/input/rmi4/rmi_f55.c | 5 +
1 file changed, 5 insertions(+)
diff --git a/drivers/input/rmi4/rmi_f55.c b/drivers/input/rmi4/rmi_f55.c
index
488adaca4dd00482cd1106d813b32871092c83a0..776c915b82e72b8a6eb5ec701cce9059c87089c4
100644
--- a/drivers/
IC)
rmi4_i2c 12-0020: read 6 bytes at 0x00e3: 0 (2c 23 0d 06 00 00)
Signed-off-by: Kaustabh Chakraborty
[codeflow adjustments, checkpatch fixes, wording]
Signed-off-by: Caleb Connolly
Co-developed-by: David Heidelberg
Signed-off-by: David Heidelberg
---
drivers/input/rmi4/rmi_driver.c | 62
Connolly
Signed-off-by: David Heidelberg
---
drivers/input/rmi4/rmi_f01.c | 14 ++
1 file changed, 14 insertions(+)
diff --git a/drivers/input/rmi4/rmi_f01.c b/drivers/input/rmi4/rmi_f01.c
index
47be64284b25ede8103ada86d6b58fd3a26976bb..2278e9b6a920774b07ec9dd3e452cedc69469be8
100644
us 6T (original parts):
manufacturer: Synaptics, product: S3706B, fw id: 2852315
Co-developed-by: Kaustabh Chakraborty
Signed-off-by: Kaustabh Chakraborty
Signed-off-by: Caleb Connolly
Co-developed-by: David Heidelberg
Signed-off-by: David Heidelberg
---
drivers/input/rmi4/rmi_driver.c
From: David Heidelberg
Mostly irrelevant for authentic Synaptics touchscreens, but very important
for applying workarounds to cheap TS knockoffs.
These knockoffs work well with the downstream driver, and since the user
has no way to distinguish them, later in this patch set, we introduce
v1:
https://lore.kernel.org/r/20230929-caleb-rmi4-quirks-v1-0-cc3c703f0...@linaro.org
---
Caleb Connolly (1):
Input: synaptics-rmi4 - handle duplicate/unknown PDT entries
David Heidelberg (1):
dt-bindings: input: syna,rmi4: Document syna,rmi4-s3706b
Kaustabh Chakraborty (5):
In
ring "why are we
even caring about PROCMAP_QUERY that in the context of this patch series".
Maybe that helps :)
--
Cheers,
David / dhildenb
On 25.06.25 11:34, Oscar Salvador wrote:
On Tue, Jun 17, 2025 at 05:43:45PM +0200, David Hildenbrand wrote:
... and hide it behind a kconfig option. There is really no need for
any !xen code to perform this check.
The naming is a bit off: we want to find the "normal" page when a PTE
to be fixed as well, but your fix
is good.
The FORCE_READ() could be factored out separately, and as part of the
same patch, replace the "asm volatile("" : "+r" (XXX));" usage in
* cow.c
* hugetlb-madvise.c
* migration.c
* pagemap_ioctl.c
* split_huge_page_test.c
--
Cheers,
David / dhildenb
On 25.06.25 10:32, Oscar Salvador wrote:
On Tue, Jun 17, 2025 at 05:43:39PM +0200, David Hildenbrand wrote:
The huge zero folio is refcounted (+mapcounted -- is that a word?)
differently than "normal" folios, similarly (but different) to the ordinary
shared zeropage.
For this
On 11.07.25 20:49, Hugh Dickins wrote:
On Fri, 11 Jul 2025, David Hildenbrand wrote:
On 08.07.25 04:52, Hugh Dickins wrote:
Of course it's limited in what it can catch (and won't even get called
if the present bit was not set - a more complete patch might unify with
those various
On 08.07.25 04:52, Hugh Dickins wrote:
On Mon, 7 Jul 2025, David Hildenbrand wrote:
On 07.07.25 08:31, Hugh Dickins wrote:
On Fri, 4 Jul 2025, David Hildenbrand wrote:
On 03.07.25 16:44, Lance Yang wrote:
On 2025/7/3 20:39, David Hildenbrand wrote:
On 03.07.25 14:34, Lance Yang wrote:
On
l passed. Would there be a way to have made
them fail? (IOW, detect that the wrong kind-of split was performed)
Acked-by: David Hildenbrand
--
Cheers,
David / dhildenb
Hello Dmitry,
I hope you're doing well. Just a gentle reminder about the patch series
I sent earlier. Please let me know if there's anything I can do to help
move it forward.
Thank you for your time and consideration.
Best regards,
David
On 11/06/2025 10:10, David Heidelberg wro
ensures the test behaves correctly across a wider range of kernel
versions and configurations, while preserving the intended behavior on
kernels that support UFFD-WP.
Suggestted-by: David Hildenbrand
Skimming over this once again ... sorry.
Nit:
"Suggested-by:"
Likely Andrew can
On 07.07.25 08:31, Hugh Dickins wrote:
On Fri, 4 Jul 2025, David Hildenbrand wrote:
On 03.07.25 16:44, Lance Yang wrote:
On 2025/7/3 20:39, David Hildenbrand wrote:
On 03.07.25 14:34, Lance Yang wrote:
On Mon, Jun 23, 2025 at 10:04 PM David Hildenbrand
wrote:
On 20.06.25 14:50, Oscar
On 25.06.25 11:03, David Hildenbrand wrote:
On 24.06.25 03:16, Alistair Popple wrote:
On Tue, Jun 17, 2025 at 05:43:38PM +0200, David Hildenbrand wrote:
Let's convert to vmf_insert_folio_pmd().
In the unlikely case there is already something mapped, we'll now
On 03.07.25 16:44, Lance Yang wrote:
On 2025/7/3 20:39, David Hildenbrand wrote:
On 03.07.25 14:34, Lance Yang wrote:
On Mon, Jun 23, 2025 at 10:04 PM David Hildenbrand
wrote:
On 20.06.25 14:50, Oscar Salvador wrote:
On Tue, Jun 17, 2025 at 05:43:32PM +0200, David Hildenbrand wrote:
In
On 02.07.25 16:20, Muhammad Usama Anjum wrote:
Add test cases to test the correctness of PFN ZERO flag of pagemap_scan
ioctl. Test with normal pages backed memory and huge pages backed
memory.
Cc: David Hildenbrand
Signed-off-by: Muhammad Usama Anjum
---
The bug has been fixed [1].
[1] https
On 03.07.25 14:34, Lance Yang wrote:
On Mon, Jun 23, 2025 at 10:04 PM David Hildenbrand wrote:
On 20.06.25 14:50, Oscar Salvador wrote:
On Tue, Jun 17, 2025 at 05:43:32PM +0200, David Hildenbrand wrote:
In 2009, we converted a VM_BUG_ON(!pfn_valid(pfn)) to the current
highest_memmap_pfn
On 03.07.25 10:51, Donet Tom wrote:
Hi David
On 7/3/25 2:03 PM, David Hildenbrand wrote:
On 03.07.25 08:06, Aboorva Devarajan wrote:
In ksm_functional_tests, test_child_ksm() returned negative values
to indicate errors. However, when passed to exit(), these were
interpreted as large unsigned
ksft_exit_skip("userfaultfd is not supported/not
enabled.\n");
+ break;
Note that we have in tools/testing/selftests/mm/config
CONFIG_USERFAULTFD=y
But I don't have anything about making the test more versatile.
Acked-by: David Hildenbrand
--
Cheers,
David / dhildenb
e-gen ~ SKIP
Acked-by: David Hildenbrand
--
Cheers,
David / dhildenb
MORY_MERGE value is inherited
# [RUN] test_prctl_unmerge
ok 9 Pages were unmerged
# Totals: pass:9 fail:0 xfail:0 xpass:0 skip:0 error:0
^ huh, what now?
--
Cheers,
David / dhildenb
failed
- Totals: pass:7 fail:2 xfail:0 xpass:0 skip:0 error:0
Fixes: 6c47de3be3a0 ("selftest/mm: ksm_functional_tests: extend test case for ksm
fork/exec")
Signed-off-by: Aboorva Devarajan
Surprising, but seems to be the right thing to do.
Acked-by: David Hildenbrand
--
Cheers,
David / dhildenb
lt; max_order; i++)
for (offset = 0;
offset < pmd_pagesize / pagesize;
offset += MAX(pmd_pagesize / pagesize / 4, 1 << i))
--
Cheers,
David / dhildenb
_LOW NR_CHUNKS_128TB
+#define NR_CHUNKS_HIGH NR_CHUNKS_3968TB
#else
#define HIGH_ADDR_MARK ADDR_MARK_128TB
#define HIGH_ADDR_SHIFT 48
Acked-by: David Hildenbrand
--
Cheers,
David / dhildenb
MAP_FAILED)
break;
- mark_range(ptr[i], MAP_CHUNK_SIZE);
+ mark_range(hptr[i], MAP_CHUNK_SIZE);
validate_addr(hptr[i], 1);
}
hchunks = i;
Acked-by: David Hildenbrand
--
Cheers,
David / dhildenb
On 02.07.25 09:39, Muhammad Usama Anjum wrote:
On 7/1/25 7:51 PM, David Hildenbrand wrote:
On 30.06.25 12:24, Muhammad Usama Anjum wrote:
Add test cases to test the correctness of PFN ZERO flag of pagemap_scan
ioctl. Test with normal pages backed memory and huge pages backed
memory.
Just to
v2:
> * Added tested-by tag
> ---
This looks great, thanks.
One small request: could we split the change to expose
kunit_attach_mm() into a separate commit? That'd make it easier for
people to backport independently of binder changes if other tests want
to use this, too.
Cheers
1 - 100 of 19843 matches
Mail list logo
