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>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20210921142919.ahfrtqcu7lpenzsz@kari-VirtualBox>
Date:   Tue, 21 Sep 2021 17:29:19 +0300
From:   Kari Argillander <kari.argillander@...il.com>
To:     Konstantin Komarov <almaz.alexandrovich@...agon-software.com>
Cc:     Stephen Rothwell <sfr@...b.auug.org.au>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Linux Next Mailing List <linux-next@...r.kernel.org>
Subject: Re: linux-next: Fixes tag needs some work in the ntfs3 tree

On Tue, Sep 21, 2021 at 04:50:02PM +0300, Konstantin Komarov wrote:
> 
> 
> On 21.09.2021 01:31, Stephen Rothwell wrote:
> > Hi all,
> > 
> > In commit
> > 
> >   0412016e4807 ("fs/ntfs3: Fix wrong error message $Logfile -> $UpCase")
> > 
> > Fixes tag
> > 
> >   Fixes: 203c2b3a406a ("fs/ntfs3: Add initialization of super block")
> > 
> > has these problem(s):
> > 
> >   - Target SHA1 does not exist
> > 
> > Maybe you meant
> > 
> > Fixes: 82cae269cfa9 ("fs/ntfs3: Add initialization of super block")
> > 
> 
> Hello.
> 
> You are right, correct SHA is 82cae269cfa9.
> Sorry, I've missed this while applying patch.

Sorry also from my part.

> As far as I know there is no way to fix this now -
> commit is already in linux-next.

But these things needs fixing. Rebase is needed.

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ