From: Takahiro Yasui <tyasui@redhat.com>
To: device-mapper development <dm-devel@redhat.com>
Subject: Re: [PATCH] dm-log: fix return value in create_log_context function
Date: Thu, 18 Dec 2008 16:23:51 -0500 [thread overview]
Message-ID: <494ABF67.2030103@redhat.com> (raw)
In-Reply-To: <1FD128DB-404C-4758-A276-6149DAAE8F74@redhat.com>
Hi Jon,
Thanks for reviewing this patch.
> We might also want to change the message in that case then too,
> right? Maybe "Unable to create disk io client"?
Thanks, "create disk io client" is better. But I changed as
"couldn't create disk io client" for consistency with other
messages.
Regards,
---
Takahiro Yasui
Hitachi Computer Products (America) Inc.
When dm_io_client_create function fails in create_log_context function,
return value is set to r but it is not used. r should be returned.
In addition, the warning message is properly corrected so that it doesn't
indicate memory allocation.
Signed-off-by: Takahiro Yasui <tyasui@redhat.com>
---
drivers/md/dm-log.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
Index: linux-2.6.28-rc8/drivers/md/dm-log.c
===================================================================
--- linux-2.6.28-rc8.orig/drivers/md/dm-log.c
+++ linux-2.6.28-rc8/drivers/md/dm-log.c
@@ -459,9 +459,9 @@ static int create_log_context(struct dm_
PAGE_SIZE));
if (IS_ERR(lc->io_req.client)) {
r = PTR_ERR(lc->io_req.client);
- DMWARN("couldn't allocate disk io client");
+ DMWARN("couldn't create disk io client");
kfree(lc);
- return -ENOMEM;
+ return r;
}
lc->disk_header = vmalloc(buf_size);
next prev parent reply other threads:[~2008-12-18 21:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-04 1:15 [PATCH] dm-log: fix return value in create_log_context function Takahiro Yasui
2008-12-18 17:43 ` Takahiro Yasui
2008-12-18 18:57 ` Jonathan Brassow
2008-12-18 21:23 ` Takahiro Yasui [this message]
2009-01-08 15:39 ` Jonathan Brassow
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=494ABF67.2030103@redhat.com \
--to=tyasui@redhat.com \
--cc=dm-devel@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.