linux-kernel - [PATCH blktests v2 0/2] nvme

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-next>] [day] [month] [year] [list]

Message-Id: <20230419084757.24846-1-dwagner@suse.de>
Date:   Wed, 19 Apr 2023 10:47:55 +0200
From:   Daniel Wagner <dwagner@...e.de>
To:     linux-nvme@...ts.infradead.org
Cc:     linux-kernel@...r.kernel.org, linux-block@...r.kernel.org,
        Chaitanya Kulkarni <kch@...dia.com>,
        Shin'ichiro Kawasaki <shinichiro@...tmail.com>,
        Daniel Wagner <dwagner@...e.de>
Subject: [PATCH blktests v2 0/2] nvme_trtype=fc fixes

With the attempt to get the fc transport running for blktest I found a couple of
issues in the current cleanup code path for fc. With these fixes and the kernel
patches and configuration from

  https://lore.kernel.org/linux-nvme/20230418130159.11075-1-dwagner@suse.de/

it starts to work nicely, incl finding some bugs in fc I think.

Daniel Wagner (2):
  nvme-rc: Cleanup fc ports in reverse order
  nvme-rc: Cleanup fc resource before module unloading

 tests/nvme/rc | 16 +++++++++-------
 1 file changed, 9 insertions(+), 7 deletions(-)

-- 
2.40.0