linux-toradex.git/kernel/relay.c, branch v7.0-rc6

Convert 'alloc_obj' family to use the new default GFP_KERNEL argument

2026-02-22T01:09:51+00:00

This was done entirely with mindless brute force, using

    git grep -l '\

treewide: Replace kmalloc with kmalloc_obj for non-scalar types

2026-02-21T09:02:28+00:00

This is the result of running the Coccinelle script from
scripts/coccinelle/api/kmalloc_objs.cocci. The script is designed to
avoid scalar types (which need careful case-by-case checking), and
instead replace kmalloc-family calls that allocate struct or union
object instances:

Single allocations:	kmalloc(sizeof(TYPE), ...)
are replaced with:	kmalloc_obj(TYPE, ...)

Array allocations:	kmalloc_array(COUNT, sizeof(TYPE), ...)
are replaced with:	kmalloc_objs(TYPE, COUNT, ...)

Flex array allocations:	kmalloc(struct_size(PTR, FAM, COUNT), ...)
are replaced with:	kmalloc_flex(*PTR, FAM, COUNT, ...)

(where TYPE may also be *VAR)

The resulting allocations no longer return "void *", instead returning
"TYPE *".

Signed-off-by: Kees Cook

Merge tag 'mm-stable-2026-02-18-19-48' of git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm

2026-02-19T04:50:32+00:00

Pull more MM  updates from Andrew Morton:

 - "mm/vmscan: fix demotion targets checks in reclaim/demotion" fixes a
   couple of issues in the demotion code - pages were failed demotion
   and were finding themselves demoted into disallowed nodes (Bing Jiao)

 - "Remove XA_ZERO from error recovery of dup_mmap()" fixes a rare
   mapledtree race and performs a number of cleanups (Liam Howlett)

 - "mm: add bitmap VMA flag helpers and convert all mmap_prepare to use
   them" implements a lot of cleanups following on from the conversion
   of the VMA flags into a bitmap (Lorenzo Stoakes)

 - "support batch checking of references and unmapping for large folios"
   implements batching to greatly improve the performance of reclaiming
   clean file-backed large folios (Baolin Wang)

 - "selftests/mm: add memory failure selftests" does as claimed (Miaohe
   Lin)

* tag 'mm-stable-2026-02-18-19-48' of git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm: (36 commits)
  mm/page_alloc: clear page->private in free_pages_prepare()
  selftests/mm: add memory failure dirty pagecache test
  selftests/mm: add memory failure clean pagecache test
  selftests/mm: add memory failure anonymous page test
  mm: rmap: support batched unmapping for file large folios
  arm64: mm: implement the architecture-specific clear_flush_young_ptes()
  arm64: mm: support batch clearing of the young flag for large folios
  arm64: mm: factor out the address and ptep alignment into a new helper
  mm: rmap: support batched checks of the references for large folios
  tools/testing/vma: add VMA userland tests for VMA flag functions
  tools/testing/vma: separate out vma_internal.h into logical headers
  tools/testing/vma: separate VMA userland tests into separate files
  mm: make vm_area_desc utilise vma_flags_t only
  mm: update all remaining mmap_prepare users to use vma_flags_t
  mm: update shmem_[kernel]_file_*() functions to use vma_flags_t
  mm: update secretmem to use VMA flags on mmap_prepare
  mm: update hugetlbfs to use VMA flags on mmap_prepare
  mm: add basic VMA flag operation helper functions
  tools: bitmap: add missing bitmap_[subset(), andnot()]
  mm: add mk_vma_flags() bitmap flag macro helper
  ...

mm: update all remaining mmap_prepare users to use vma_flags_t

2026-02-12T23:42:58+00:00

We will be shortly removing the vm_flags_t field from vm_area_desc so we
need to update all mmap_prepare users to only use the dessc->vma_flags
field.

This patch achieves that and makes all ancillary changes required to make
this possible.

This lays the groundwork for future work to eliminate the use of
vm_flags_t in vm_area_desc altogether and more broadly throughout the
kernel.

While we're here, we take the opportunity to replace VM_REMAP_FLAGS with
VMA_REMAP_FLAGS, the vma_flags_t equivalent.

No functional changes intended.

Link: https://lkml.kernel.org/r/fb1f55323799f09fe6a36865b31550c9ec67c225.1769097829.git.lorenzo.stoakes@oracle.com
Signed-off-by: Lorenzo Stoakes 
Acked-by: Damien Le Moal 	[zonefs]
Acked-by: "Darrick J. Wong" 
Acked-by: Pedro Falcato 
Cc: Baolin Wang 
Cc: Barry Song 
Cc: David Hildenbrand 
Cc: Dev Jain 
Cc: Jason Gunthorpe 
Cc: Liam Howlett 
Cc: Suren Baghdasaryan 
Cc: Vlastimil Babka 
Cc: Zi Yan 
Cc: Jarkko Sakkinen 
Cc: Yury Norov 
Cc: Chris Mason 
Signed-off-by: Andrew Morton

kernel: add SPDX-License-Identifier lines

2026-01-16T14:32:16+00:00

Add SPDX-License-Identifier lines to some old kernel
files.

Signed-off-by: Tim Bird 
Acked-by: Karim Yaghmour 
Signed-off-by: Greg Kroah-Hartman

relay: update relay to use mmap_prepare

2025-11-17T01:28:11+00:00

It is relatively trivial to update this code to use the f_op->mmap_prepare
hook in favour of the deprecated f_op->mmap hook, so do so.

Link: https://lkml.kernel.org/r/7c9e82cdddf8b573ea3edb8cdb697363e3ccb5d7.1760959442.git.lorenzo.stoakes@oracle.com
Signed-off-by: Lorenzo Stoakes 
Reviewed-by: David Hildenbrand 
Reviewed-by: Jason Gunthorpe 
Reviewed-by: Pedro Falcato 
Cc: Alexander Gordeev 
Cc: Al Viro 
Cc: Andreas Larsson 
Cc: Andrey Konovalov 
Cc: Arnd Bergmann 
Cc: Baolin Wang 
Cc: Baoquan He 
Cc: Chatre, Reinette 
Cc: Christian Borntraeger 
Cc: Christian Brauner 
Cc: Dan Williams 
Cc: Dave Jiang 
Cc: Dave Martin 
Cc: Dave Young 
Cc: David S. Miller 
Cc: Dmitriy Vyukov 
Cc: Greg Kroah-Hartman 
Cc: Guo Ren 
Cc: Heiko Carstens 
Cc: Hugh Dickins 
Cc: James Morse 
Cc: Jan Kara 
Cc: Jann Horn 
Cc: Jonathan Corbet 
Cc: Kevin Tian 
Cc: Konstantin Komarov 
Cc: Liam Howlett 
Cc: "Luck, Tony" 
Cc: Matthew Wilcox (Oracle) 
Cc: Michal Hocko 
Cc: Mike Rapoport 
Cc: Muchun Song 
Cc: Nicolas Pitre 
Cc: Oscar Salvador 
Cc: Robin Murohy 
Cc: Sumanth Korikkar 
Cc: Suren Baghdasaryan 
Cc: Sven Schnelle 
Cc: Thomas Bogendoerfer 
Cc: "Uladzislau Rezki (Sony)" 
Cc: Vasily Gorbik 
Cc: Vishal Verma 
Cc: Vivek Goyal 
Cc: Vlastimil Babka 
Cc: Will Deacon 
Signed-off-by: Andrew Morton

relayfs: support a counter tracking if data is too big to write

2025-07-10T05:57:52+00:00

It really doesn't matter if the user/admin knows what the last too big
value is.  Record how many times this case is triggered would be helpful.

Solve the existing issue where relay_reset() doesn't restore the value.

Store the counter in the per-cpu buffer structure instead of the global
buffer structure.  It also solves the racy condition which is likely to
happen when a few of per-cpu buffers encounter the too big data case and
then access the global field last_toobig without lock protection.

Remove the printk in relay_close() since kernel module can directly call
relay_stats() as they want.

Link: https://lkml.kernel.org/r/20250612061201.34272-6-kerneljasonxing@gmail.com
Signed-off-by: Jason Xing 
Reviewed-by: Yushan Zhou 
Reviewed-by: Masami Hiramatsu (Google) 
Cc: Jens Axboe 
Cc: Mathieu Desnoyers 
Cc: Steven Rostedt 
Signed-off-by: Andrew Morton

relayfs: introduce getting relayfs statistics function

2025-07-10T05:57:51+00:00

In this version, only support getting the counter for buffer full and
implement the framework of how it works.

Users can pass certain flag to fetch what field/statistics they expect to
know.  Each time it only returns one result.  So do not pass multiple
flags.

Link: https://lkml.kernel.org/r/20250612061201.34272-4-kerneljasonxing@gmail.com
Signed-off-by: Jason Xing 
Reviewed-by: Yushan Zhou 
Reviewed-by: Masami Hiramatsu (Google) 
Cc: Jens Axboe 
Cc: Mathieu Desnoyers 
Cc: Steven Rostedt 
Signed-off-by: Andrew Morton

relayfs: support a counter tracking if per-cpu buffers is full

2025-07-10T05:57:51+00:00

When using relay mechanism, we often encounter the case where new data are
lost or old unconsumed data are overwritten because of slow reader.

Add 'full' field in per-cpu buffer structure to detect if the above case
is happening.  Relay has two modes: 1) non-overwrite mode, 2) overwrite
mode.  So buffer being full here respectively means: 1) relayfs doesn't
intend to accept new data and then simply drop them, or 2) relayfs is
going to start over again and overwrite old unread data with new data.

Note: this counter doesn't need any explicit lock to protect from being
modified by different threads for the better performance consideration. 
Writers calling __relay_write/relay_write should consider how to use the
lock and ensure it performs under the lock protection, thus it's not
necessary to add a new small lock here.

Link: https://lkml.kernel.org/r/20250612061201.34272-3-kerneljasonxing@gmail.com
Signed-off-by: Jason Xing 
Reviewed-by: Yushan Zhou 
Reviewed-by: Jens Axboe 
Reviewed-by: Masami Hiramatsu (Google) 
Cc: Mathieu Desnoyers 
Cc: Steven Rostedt 
Signed-off-by: Andrew Morton

relayfs: abolish prev_padding

2025-07-10T05:57:51+00:00

Patch series "relayfs: misc changes", v5.

The series mostly focuses on the error counters which helps every user
debug their own kernel module.


This patch (of 5):

prev_padding represents the unused space of certain subbuffer.  If the
content of a call of relay_write() exceeds the limit of the remainder of
this subbuffer, it will skip storing in the rest space and record the
start point as buf->prev_padding in relay_switch_subbuf().  Since the buf
is a per-cpu big buffer, the point of prev_padding as a global value for
the whole buffer instead of a single subbuffer (whose padding info is
stored in buf->padding[]) seems meaningless from the real use cases, so we
don't bother to record it any more.

Link: https://lkml.kernel.org/r/20250612061201.34272-1-kerneljasonxing@gmail.com
Link: https://lkml.kernel.org/r/20250612061201.34272-2-kerneljasonxing@gmail.com
Signed-off-by: Jason Xing 
Reviewed-by: Yushan Zhou 
Reviewed-by: Masami Hiramatsu (Google) 
Cc: Jens Axboe 
Cc: Mathieu Desnoyers 
Cc: Steven Rostedt 
Signed-off-by: Andrew Morton