public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Al Viro <viro@ZenIV•linux.org.uk>
Cc: Linux Next Mailing List <linux-next@vger•kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger•kernel.org>
Subject: linux-next: Fixes tag needs some work in the vfs-fixes tree
Date: Mon, 11 Nov 2019 09:09:17 +1100	[thread overview]
Message-ID: <20191111090917.0203cb82@canb.auug.org.au> (raw)

[-- Attachment #1: Type: text/plain, Size: 478 bytes --]

Hi all,

In commit

  bcf0d9d4b769 ("ecryptfs: fix unlink and rmdir in face of underlying fs modifications")

Fixes tag

  Fixes: 74dd7c97ea2 "ecryptfs_rename(): verify that lower dentries are still OK after lock_rename()"

has these problem(s):

  - SHA1 should be at least 12 digits long
    Can be fixed by setting core.abbrev to 12 (or more) or (for git v2.11
    or later) just making sure it is not set (or set to "auto").

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

             reply	other threads:[~2019-11-10 22:09 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-10 22:09 Stephen Rothwell [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-04-29  9:15 linux-next: Fixes tag needs some work in the vfs-fixes tree Stephen Rothwell
2025-05-07  7:43 ` Stephen Rothwell
2025-04-29  9:13 Stephen Rothwell
2024-05-31  6:08 Stephen Rothwell
2021-03-25 20:51 Stephen Rothwell
2020-11-12 21:02 Stephen Rothwell
2020-11-12 21:14 ` Al Viro
2019-10-21 20:44 Stephen Rothwell

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=20191111090917.0203cb82@canb.auug.org.au \
    --to=sfr@canb$(echo .)auug.org.au \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=viro@ZenIV$(echo .)linux.org.uk \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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