From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Vlastimil Babka <vbabka@suse.cz>
Cc: Christian Brauner <brauner@kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: duplicate patches in the slab tree
Date: Mon, 9 Sep 2024 19:28:00 +1000 [thread overview]
Message-ID: <20240909192800.4d60b754@canb.auug.org.au> (raw)
In-Reply-To: <bde596e3-365b-4fdb-8a03-0a4e40a56246@suse.cz>
[-- Attachment #1: Type: text/plain, Size: 3782 bytes --]
Hi Vlastimil,
On Mon, 9 Sep 2024 10:32:06 +0200 Vlastimil Babka <vbabka@suse.cz> wrote:
>
> I'm confused how did that help if slab tree didn't change since 20240906 and
> the commit ids meanwhile changed on the vfs side?
$ git grep slab next-20240906:Next/SHA1snext-20240906:Next/SHA1s:slab 2e0abb33823cd3885e6d9118fccf2a027db9b490
$ git diff --stat 2e0abb33823cd3885e6d9118fccf2a027db9b490...slab/slab/for-next
warning: 2e0abb33823cd3885e6d9118fccf2a027db9b490...slab/slab/for-next: multiple merge bases, using e02147cb703412fa13dd31908c734d7fb2314f55
drivers/net/tun.c | 6 +
drivers/tty/tty_io.c | 6 +
fs/fcntl.c | 166 +++++++++++++++++-----
fs/file_table.c | 14 +-
fs/internal.h | 1 +
fs/locks.c | 6 +-
fs/notify/dnotify/dnotify.c | 6 +-
include/linux/fs.h | 102 ++++++++------
include/linux/kasan.h | 65 ++++++++-
include/linux/rcutiny.h | 5 +
include/linux/rcutree.h | 1 +
include/linux/slab.h | 163 +++++++++++++++++++---
io_uring/io_uring.c | 14 +-
kernel/rcu/tree.c | 109 +++++++++++++--
lib/slub_kunit.c | 31 +++++
mm/Kconfig.debug | 32 +++++
mm/kasan/common.c | 64 +++++----
mm/kasan/kasan_test.c | 46 +++++++
mm/slab.h | 11 +-
mm/slab_common.c | 260 ++++++++++++----------------------
mm/slub.c | 299 ++++++++++++++++++++++++++++------------
net/core/sock.c | 2 +-
net/ipv4/inet_connection_sock.c | 5 +-
security/selinux/hooks.c | 2 +-
security/smack/smack_lsm.c | 2 +-
25 files changed, 1005 insertions(+), 413 deletions(-)
$ git log --oneline 2e0abb33823cd3885e6d9118fccf2a027db9b490..slab/slab/for-next
66dcd51a4503 (slab/slab/for-next) Merge branch 'slab/for-6.12/kmem_cache_args' into slab/for-next
fa9057f66dc8 Merge branch 'slab/for-6.12/rcu_barriers' into slab/for-next
8f88d16ae7c4 io_uring: port to struct kmem_cache_args
0745de59907f slab: make __kmem_cache_create() static inline
c97f071a3e39 slab: make kmem_cache_create_usercopy() static inline
6d5110520e00 slab: remove kmem_cache_create_rcu()
212a84da3190 file: port to struct kmem_cache_args
272d25721a77 slab: create kmem_cache_create() compatibility layer
7b8e2fe0c4b3 slab: port KMEM_CACHE_USERCOPY() to struct kmem_cache_args
1f4fcd6cfa1c slab: port KMEM_CACHE() to struct kmem_cache_args
dda9e30e63eb slab: remove rcu_freeptr_offset from struct kmem_cache
45bbb06b3ace slab: pass struct kmem_cache_args to do_kmem_cache_create()
d2ac7d61ed73 slab: pull kmem_cache_open() into do_kmem_cache_create()
2b7491007d1f slab: pass struct kmem_cache_args to create_cache()
be9b2ec72e53 slab: port kmem_cache_create_usercopy() to struct kmem_cache_args
f6ee8439fdad slab: port kmem_cache_create_rcu() to struct kmem_cache_args
e8ccc4307bb0 slab: port kmem_cache_create() to struct kmem_cache_args
95c65689ce1f slab: add struct kmem_cache_args
2a51e14ca2cc memcg: add charging of already allocated slab objects
432e6080ec7d slab: s/__kmem_cache_create/do_kmem_cache_create/g
01cc2238ba4a Merge branch 'vfs.file' of gitolite.kernel.org:pub/scm/linux/kernel/git/vfs/vfs into slab/for-6.12/kmem_cache_args
0f389adb4b80 mm: Removed @freeptr_offset to prevent doc warning
dfdc8d2565e8 Merge patch series "fs,mm: add kmem_cache_create_rcu()"
ea566e18b4de fs: use kmem_cache_create_rcu()
d345bd2e9834 mm: add kmem_cache_create_rcu()
e446f18e98e8 mm: remove unused argument from create_cache()
c0390d541128 fs: pack struct file
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2024-09-09 9:28 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-09 7:12 linux-next: duplicate patches in the slab tree Stephen Rothwell
2024-09-09 7:18 ` Vlastimil Babka
2024-09-09 9:16 ` Christian Brauner
2024-09-09 9:40 ` Vlastimil Babka
2024-09-09 10:13 ` Christian Brauner
2024-09-09 10:35 ` Vlastimil Babka
2024-09-09 10:42 ` Christian Brauner
2024-09-09 11:02 ` Christian Brauner
2024-09-09 11:45 ` Stephen Rothwell
2024-09-09 12:19 ` Christian Brauner
2024-09-09 12:37 ` Christian Brauner
2024-09-09 13:44 ` Stephen Rothwell
2024-09-09 12:09 ` Vlastimil Babka
2024-09-09 12:18 ` Christian Brauner
2024-09-09 13:11 ` Konstantin Ryabitsev
2024-09-09 8:10 ` Stephen Rothwell
2024-09-09 8:32 ` Vlastimil Babka
2024-09-09 8:49 ` Vlastimil Babka
2024-09-09 9:33 ` Stephen Rothwell
2024-09-09 9:28 ` Stephen Rothwell [this message]
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=20240909192800.4d60b754@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=brauner@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=vbabka@suse.cz \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox