linux-kernel - linux-next: Fixes tags need some work in the overlayfs tree

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Date:   Thu, 16 Jul 2020 07:52:29 +1000
From:   Stephen Rothwell <sfr@...b.auug.org.au>
To:     Miklos Szeredi <miklos@...redi.hu>
Cc:     Linux Next Mailing List <linux-next@...r.kernel.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Amir Goldstein <amir73il@...il.com>,
        youngjun <her0gyugyu@...il.com>
Subject: linux-next: Fixes tags need some work in the overlayfs tree

Hi all,

In commit

  c70cc896be1c ("ovl: fix oops in ovl_indexdir_cleanup() with nfs_export=on")

Fixes tag

  Fixes: commit c21c839b8448 ("ovl: whiteout inode sharing")

has these problem(s):

  - leading word 'commit' unexpected

In commit

  6083ba4ed54a ("ovl: inode reference leak in ovl_is_inuse true case.")

Fixes tag

  Fixes: 0be0bfd2de9d ("ovl: fix regression caused by overlapping layers..")

has these problem(s):

  - Subject does not match target commit subject
    Just use
	git log -1 --format='Fixes: %h ("%s")'

There is no need to truncate the subject of the fixed commit.

Neither of these warrants rebasing the tree, just remember for next time.

-- 
Cheers,
Stephen Rothwell

Content of type "application/pgp-signature" skipped