This is an automated email from the git hooks/post-receive script.

unknown user pushed a change to branch fs-current in repository linux-next.

omits 3c1a1f78bc55 Merge branch 'ovl-fixes' of https://git.kernel.org/pub/scm [...] omits 9617c2114520 Merge branch 'fixes' of https://git.kernel.org/pub/scm/lin [...] omits 0e0fe4867716 Merge branch 'next-fixes' of https://git.kernel.org/pub/sc [...] omits ad4c1fbf0f35 Merge branch 'vfs.fixes' of https://git.kernel.org/pub/scm [...] omits cda250b0fc83 change_mnt_propagation(): calculate propagation source onl [...] omits c71bd3dfe01d use uniform permission checks for all mount propagation changes omits 62c3c5d01aed propagate_umount(): only surviving overmounts should be re [...] omits dcfb19fd6ca0 fix the softlockups in attach_recursive_mnt() omits fb6d0f63f46d fs/buffer: fix use-after-free when call bh_read() helper omits acc836740ca6 Merge patch series "iterate_folioq bug when offset==size ( [...] omits 334430b2d585 iov_iter: iov_folioq_get_pages: don't leave empty slot behind omits 546a40359fd2 iov_iter: iterate_folioq: fix handling of offset >= folio size new 7375f22495e7 fs/buffer: fix use-after-free when call bh_read() helper new 589c12edcd8a coredump: Fix return value in coredump_parse() new c237aa9884f2 kernfs: don't fail listing extended attributes new a2c1f82618b0 signal: Fix memory leak for PIDFD_SELF* sentinels new 055f213075fb Merge tag 'vfs-6.17-rc3.fixes' of git://git.kernel.org/pub [...] new 7cca555b94a2 Merge tag 'ovl-fixes-6.17-rc1' of git://git.kernel.org/pub [...] new 0ddfb62f5d01 fix the softlockups in attach_recursive_mnt() new da025cdb97a2 propagate_umount(): only surviving overmounts should be re [...] new cffd0441872e use uniform permission checks for all mount propagation changes new fb924b7b8669 change_mnt_propagation(): calculate propagation source onl [...] new b19a97d57c15 Merge tag 'pull-fixes' of git://git.kernel.org/pub/scm/lin [...] new b471d5fdedf8 Merge branch 'next-fixes' of https://git.kernel.org/pub/sc [...]

This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the branch are not in the new version. This situation occurs when a user --force pushes a change and generates a repository containing something like this:

* -- * -- B -- O -- O -- O (3c1a1f78bc55) \ N -- N -- N refs/heads/fs-current (b471d5fdedf8)

You should already have received notification emails for all of the O revisions, and so the following emails describe only the N revisions from the common base, B.

Any revisions marked "omits" are not gone; other references still refer to them. Any revisions marked "discards" are gone forever.

The 12 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference.

Summary of changes: fs/coredump.c | 2 +- fs/kernfs/inode.c | 4 ++-- include/linux/iov_iter.h | 20 +++++++++----------- kernel/signal.c | 6 +++++- lib/iov_iter.c | 6 +++--- 5 files changed, 20 insertions(+), 18 deletions(-)