linux-kernel - Re: linux-next: duplicate patch in the device-mapper 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>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <ebfd8bf4-6260-f04-38f9-2ec234968171@redhat.com>
Date: Thu, 11 Jul 2024 20:51:17 +0200 (CEST)
From: Mikulas Patocka <mpatocka@...hat.com>
To: Mike Snitzer <snitzer@...nel.org>
cc: Stephen Rothwell <sfr@...b.auug.org.au>, Jens Axboe <axboe@...nel.dk>, 
    Alasdair G Kergon <agk@...hat.com>, 
    Linux Kernel Mailing List <linux-kernel@...r.kernel.org>, 
    Linux Next Mailing List <linux-next@...r.kernel.org>
Subject: Re: linux-next: duplicate patch in the device-mapper tree



On Thu, 11 Jul 2024, Mike Snitzer wrote:

> > Looks like the dm tree is re-applying patches yesterday rather
> > than pulling in the dependency?
> > 
> > https://git.kernel.org/pub/scm/linux/kernel/git/device-mapper/linux-dm.git/commit/?h=dm-6.11&id=e87621ac68fec9086d9f0af4fe96594dd8e07fbb
> > 
> > why?
> 
> Really good question.
> 
> Mikulas has been handling DM for the 6.11 development cycle.  But I've
> helped answer question and such along the way.  We actually had a
> meeting on Tuesday to discuss outstanding patches (in patchwork) and
> specifically discussed this very patch.  At the time I said I would
> get with you to make sure you were the one to pick up Damien's 5
> patches (which included what is now commit e87621ac68fe in block).  I
> specifically said that the entire series should go through block
> because even if DM picked up the one "dm: Refactor is_abnormal_io()"
> it'd cause problems because block would then depend on DM for a simple
> prep commit needed for later a patch in series.

I probably badly understood it, I added the patch to my notes and then I 
thought that I should apply it. Sorry for that.

Mikulas

> Anyway, I later saw you had already picked up Damien's series and had
> no need to reach out to you, I noted as much to a group chat at Red
> Hat (Mikulas included).  So not really sure what happened.
> 
> Sorry for the noise/trouble.
> 
> Mike
>