linux-kernel - [PATCH V2] lightnvm: pblk: refactor init/exit sequences

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: <1519919998-20829-1-git-send-email-javier@cnexlabs.com>
Date:   Thu,  1 Mar 2018 16:59:57 +0100
From:   "Javier González" <javier@...igon.com>
To:     mb@...htnvm.io
Cc:     linux-block@...r.kernel.org, linux-kernel@...r.kernel.org,
        dan.carpenter@...cle.com,
        Javier González <javier@...xlabs.com>
Subject: [PATCH V2] lightnvm: pblk: refactor init/exit sequences

# Changes since V1
  - Remove double check for factory initialization

The init/exit sequences have grown in a very bad way. Refactor them to
eliminate dependencies across initialization modules.

One of these dependencies caused a bad double free when introducing a
preparation patch for 2.0 bad block identification. This was reported by
Dan Carpenter and 0-DAY.

Matias,

Since you have not send the PR to Jens, please squash this patch with:
    lightnvm: pblk: refactor bad block identification

You will notice that I had queued this patch on the 2.0 series. I did
the rebase now, which is probably what I should have done from the
beginning. Since I'll be sending a V5 for it, this should not be a
problem.

Thanks,
Javier

Javier González (1):
  lightnvm: pblk: refactor init/exit sequences

 drivers/lightnvm/pblk-init.c | 415 +++++++++++++++++++++----------------------
 1 file changed, 206 insertions(+), 209 deletions(-)

-- 
2.7.4