linux-kernel - Re: Future of liblockdep

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: <20170503210032.q5ot4qximfdoqrk5@sasha-lappy>
Date:   Wed, 3 May 2017 21:00:34 +0000
From:   alexander.levin@...izon.com
To:     Ben Hutchings <ben@...adent.org.uk>
CC:     Ingo Molnar <mingo@...hat.com>, LKML <linux-kernel@...r.kernel.org>
Subject: Re: Future of liblockdep

On Wed, May 03, 2017 at 09:13:57PM +0100, Ben Hutchings wrote:
> liblockdep hasn't been buildable since (I think) Linux 4.6.  I sent
> Sasha fixes for that last June and he included these in a pull request
> to Ingo, but somehow they never reached mainline.  Linux 4.8 broke
> liblockdep further, and I gave up packaging it for Debian.
> 
> There have been no other changes to liblockdep since then, other than a
> general change in the tools/ directory.  Sasha's address in MAINTAINERS
> is also out-of-date.
> 
> Please either maintain liblockdep properly or delete it.  We shouldn't
> keep code in the tree in a broken state.

Hi Ben,

I indeed received those patches and forwarded them on:

	https://lkml.org/lkml/2016/6/17/1044

As well as an updated maintainers entry:

	https://lkml.org/lkml/2016/7/29/431

But I failed to follow up on that and it seems to have fallen through the
cracks.

I'll get it back into shape, sorry.

I also don't expect many changes to liblockdep other than keeping it buildable,
if there are any missing features or bugs you'd like to discuss I'd be happy to
look into those.

-- 

Thanks,
Sasha