From: NeilBrown <neilb@suse.com>
To: Zhilong Liu <zlliu@suse.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: report a bug that panic when grow size for external bitmap
Date: Thu, 31 Aug 2017 10:27:21 +1000 [thread overview]
Message-ID: <87r2vsfuom.fsf@notabene.neil.brown.name> (raw)
In-Reply-To: <73429dce-a22d-149e-656a-13af228c093f@suse.com>
[-- Attachment #1: Type: text/plain, Size: 1027 bytes --]
On Wed, Aug 30 2017, Zhilong Liu wrote:
> On 08/29/2017 06:47 PM, NeilBrown wrote:
>> Thanks. I see what I missed. Please try this patch instead.
>
> Hi, Neil;
> I have tested the following patch, I still got the call-trace after
> I built with it.
> If you need other infos, I would append.
Thanks for testing.
I looked more completely and I think it is easiest just to disable the
functionality rather than try to fix it.
Resizing the file in the kernel is extra complexity that I don't
want to get in to.
We could adjust the bitmap chunk size so that the file doesn't
need to grow, but it started getting more complicated than I really
wanted to deal with.
If there is anyone actually using file-backed bitmaps who wants to
be able to resize the array without removing the bitmap first, then
we can look at the problem again. For now I've sent a patch which
just returns an error instead of crashing when someone tries to resize
an array with a file-backed bitmap.
Thanks,
NeilBrown
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2017-08-31 0:27 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-28 9:37 report a bug that panic when grow size for external bitmap Zhilong Liu
[not found] ` <87y3q3gq8g.fsf@notabene.neil.brown.name>
2017-08-29 2:37 ` Zhilong Liu
2017-08-29 3:12 ` NeilBrown
2017-08-29 4:39 ` Zhilong Liu
2017-08-29 10:47 ` NeilBrown
2017-08-30 2:52 ` Zhilong Liu
2017-08-30 4:08 ` NeilBrown
2017-08-30 4:57 ` Zhilong Liu
2017-08-31 0:27 ` NeilBrown [this message]
2017-08-31 2:57 ` Zhilong Liu
2017-08-31 3:30 ` NeilBrown
2017-09-01 9:49 ` Zhilong Liu
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=87r2vsfuom.fsf@notabene.neil.brown.name \
--to=neilb@suse.com \
--cc=linux-raid@vger.kernel.org \
--cc=zlliu@suse.com \
/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).