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 5518f1f0cdc7 Merge branch 'fixes' of https://git.kernel.org/pub/scm/lin [...] omits d8733dd793f1 Merge branch 'next-fixes' of https://git.kernel.org/pub/sc [...] omits 6cb75b530698 Merge branch 'vfs.fixes' of https://git.kernel.org/pub/scm [...] omits fc0b6e6a9e3f Merge branch 'misc-6.17' into next-fixes adds 6a912e8aa2b2 ext4: show the default enabled i_version option adds f2326fd14a22 ext4: preserve SB_I_VERSION on remount adds b4cc4a407726 ext4: check fast symlink for ea_inode correctly adds f3fbaa74d999 ext4: remove useless if check adds 59d8731c887b ext4: fix unused variable warning in ext4_init_new_dir adds 4ba97589ed19 ext4: remove redundant __GFP_NOWARN adds bae76c035bf0 ext4: fix fsmap end of range reporting with bigalloc adds 3ffbdd1f1165 ext4: fix reserved gdt blocks handling in fsmap adds c5e104a91e7b ext4: don't try to clear the orphan_present feature block [...] adds 02c7f7219ac0 ext4: fix hole length calculation overflow in non-extent inodes adds 76dba1fe277f ext4: use kmalloc_array() for array space allocation adds 757fc66da91b ext4: fix incorrect function name in comment adds 9d98cf463225 jbd2: prevent softlockup in jbd2_log_do_checkpoint() new 074e461d9ed5 Merge tag 'ext4_for_linus-6.17-rc3' of git://git.kernel.or [...] new be48bcf004f9 Merge tag 'for-6.17-rc2-tag' of git://git.kernel.org/pub/s [...] new ad4c1fbf0f35 Merge branch 'vfs.fixes' of https://git.kernel.org/pub/scm [...] new 8299ec04baed Merge branch 'misc-6.17' into next-fixes new 0e0fe4867716 Merge branch 'next-fixes' of https://git.kernel.org/pub/sc [...] new 9617c2114520 Merge branch 'fixes' of https://git.kernel.org/pub/scm/lin [...] new 5f1c8965e748 ovl: use I_MUTEX_PARENT when locking parent in ovl_create_temp() new e8bd877fb76b ovl: fix possible double unlink new 3c1a1f78bc55 Merge branch 'ovl-fixes' of https://git.kernel.org/pub/scm [...]
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 (5518f1f0cdc7) \ N -- N -- N refs/heads/fs-current (3c1a1f78bc55)
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 9 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/ext4/fsmap.c | 23 ++++++++++++++++++++--- fs/ext4/indirect.c | 4 ++-- fs/ext4/inode.c | 4 ++-- fs/ext4/namei.c | 4 ---- fs/ext4/orphan.c | 5 +++-- fs/ext4/page-io.c | 2 +- fs/ext4/super.c | 12 ++++++++---- fs/jbd2/checkpoint.c | 1 + fs/overlayfs/dir.c | 2 +- fs/overlayfs/util.c | 3 ++- 10 files changed, 40 insertions(+), 20 deletions(-)