From: "Javier González" <javier@javigon.com>
To: mb@lightnvm.io
Cc: linux-block@vger.kernel.org, linux-kernel@vger.kernel.org,
dan.carpenter@oracle.com, "Javier González" <javier@cnexlabs.com>
Subject: [PATCH] lightnvm: pblk: refactor init/exit sequences
Date: Thu, 1 Mar 2018 16:08:55 +0100 [thread overview]
Message-ID: <1519916936-30079-1-git-send-email-javier@cnexlabs.com> (raw)
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 | 412 +++++++++++++++++++++----------------------
1 file changed, 206 insertions(+), 206 deletions(-)
--
2.7.4
next reply other threads:[~2018-03-01 15:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-01 15:08 Javier González [this message]
2018-03-01 15:08 ` [PATCH] lightnvm: pblk: refactor init/exit sequences Javier González
2018-03-01 15:59 [PATCH V2] " Javier González
2018-03-01 15:59 ` [PATCH] " Javier González
2018-03-01 18:49 ` Matias Bjørling
2018-03-01 19:29 ` Javier González
2018-03-05 13:38 ` Matias Bjørling
2018-03-05 13:45 ` Javier González
2018-03-05 14:16 ` Matias Bjørling
2018-03-05 14:18 ` Javier González
2018-03-05 18:27 ` Matias Bjørling
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1519916936-30079-1-git-send-email-javier@cnexlabs.com \
--to=javier@javigon.com \
--cc=dan.carpenter@oracle.com \
--cc=javier@cnexlabs.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mb@lightnvm.io \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).