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 71d7e593564b Merge branch 'nfsd-fixes' of git://git.kernel.org/pub/scm/ [...] omits ebb174126050 Merge branch 'next-fixes' of git://git.kernel.org/pub/scm/ [...] omits 49170cf81659 Merge branch 'vfs.fixes' of git://git.kernel.org/pub/scm/l [...] new 488ef3560196 KEYS: Invert FINAL_PUT bit new 6bdd3a01fe46 fs: add missing values to TRACE_IOCB_STRINGS new ad5a0351064c VFS: change try_lookup_noperm() to skip revalidation new e1eb84356318 Merge branch 'vfs.fixes' of git://git.kernel.org/pub/scm/l [...] new aeaea3aa9e82 Merge branch 'next-fixes' of git://git.kernel.org/pub/scm/ [...] new eaca20c03246 Merge branch 'nfsd-fixes' of git://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 (71d7e593564b) \ N -- N -- N refs/heads/fs-current (eaca20c03246)
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 6 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/namei.c | 17 +++++++++++++---- include/linux/fs.h | 4 +++- include/linux/key.h | 2 +- security/keys/gc.c | 4 ++-- security/keys/key.c | 5 +++-- 5 files changed, 22 insertions(+), 10 deletions(-)