From: Jens Axboe <axboe@kernel.dk>
To: "Matias Bjørling" <m@bjorling.me>,
linux-block@vger.kernel.org, linux-kernel@vger.kernel.org,
axboe@fb.com
Subject: Re: [PATCH] lightnvm: wrong offset in bad blk lun calculation
Date: Tue, 29 Dec 2015 08:28:54 -0700 [thread overview]
Message-ID: <5682A6B6.1010909@kernel.dk> (raw)
In-Reply-To: <1451396276-2589-2-git-send-email-m@bjorling.me>
On 12/29/2015 06:37 AM, Matias Bjørling wrote:
> dev->nr_luns reports the total number of luns available in a device
> while dev->luns_per_chnl is the number of luns per channel.
>
> When multiple channels are available, the offset is calculated from a
> channel and lun id into a linear array. As it multiplies with
> the total number of luns, we go out of bound when channel id > 0 and
> causes the kernel to panic when we read a protected kernel memory area.
Added for 4.4, thanks.
--
Jens Axboe
prev parent reply other threads:[~2015-12-29 15:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-29 13:37 [PATCH] Fix for 4.4-rc7 Matias Bjørling
2015-12-29 13:37 ` [PATCH] lightnvm: wrong offset in bad blk lun calculation Matias Bjørling
2015-12-29 15:28 ` Jens Axboe [this message]
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=5682A6B6.1010909@kernel.dk \
--to=axboe@kernel.dk \
--cc=axboe@fb.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=m@bjorling.me \
/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