linux-kernel - Regression in my latest GFS2 pull request

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:   Fri, 5 May 2017 12:31:11 -0400 (EDT)
From:   Bob Peterson <rpeterso@...hat.com>
To:     Linus Torvalds <torvalds@...ux-foundation.org>
Cc:     cluster-devel <cluster-devel@...hat.com>,
        linux-kernel@...r.kernel.org
Subject: Regression in my latest GFS2 pull request

Hi Linus,

I see that you haven't processed my latest GFS2 pull request.

Today I found a regression in one of those patches. I've written,
tested, and posted a patch to cluster-devel to fix the problem,
and I'd like to get it into this merge window because it's severe.
(You can't unmount a gfs2 file system after withdraw due to errors).

My question is: How would you like me to handle it?

Push the new patch, tag it, and do a second pull request?
Wait until you've processed the first pull request, then do so?
Or is there a better way?

Regards,

Bob Peterson