From: Vivek Goyal <vgoyal@redhat.com>
To: Mike Snitzer <snitzer@redhat.com>
Cc: dm-devel@redhat.com, ejt@redhat.com, agk@redhat.com
Subject: Re: [PATCH] dm transaction manager: handle space map checker failure
Date: Wed, 20 Jun 2012 17:37:56 -0400 [thread overview]
Message-ID: <20120620213756.GL22599@redhat.com> (raw)
In-Reply-To: <20120620212010.GK22599@redhat.com>
On Wed, Jun 20, 2012 at 05:20:10PM -0400, Vivek Goyal wrote:
> On Wed, Jun 20, 2012 at 03:24:59PM -0400, Mike Snitzer wrote:
> > If CONFIG_DM_DEBUG_SPACE_MAPS is enabled and dm_sm_checker_create()
> > fails, dm_tm_create_internal() would still return success even though it
> > cleaned up all resources it was supposed to have created.
> >
> > Fix the space map checker code to return an appropriate ERR_PTR and have
> > dm_tm_create_internal() check for it with IS_ERR.
> >
>
> I tested the patch and it works. It fails gracefully instead of segfaulting.
>
> device-mapper: reload ioctl failed: Cannot allocate memory
>
> I still do get waring though about large memory allocation. That's a
> separate issue though.
I put a trace_printk() in ca_create() to see how much memory we are trying
to allocated using kzalloc. And answer is 10485760. Number of blocks
obtained from space map is 2621440. I think this might be happening because
my metadata device size is 10G.
Thanks
Vivek
next prev parent reply other threads:[~2012-06-20 21:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-20 19:24 [PATCH] dm transaction manager: handle space map checker failure Mike Snitzer
2012-06-20 21:20 ` Vivek Goyal
2012-06-20 21:37 ` Vivek Goyal [this message]
2012-06-20 22:15 ` Mike Snitzer
2012-06-21 5:10 ` Mike Snitzer
2012-06-21 6:10 ` Mike Snitzer
2012-06-25 12:16 ` Joe Thornber
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=20120620213756.GL22599@redhat.com \
--to=vgoyal@redhat.com \
--cc=agk@redhat.com \
--cc=dm-devel@redhat.com \
--cc=ejt@redhat.com \
--cc=snitzer@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.