From: Andrew Price <anprice@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [PATCH 5/5] mkfs.gfs2: Improve error messages
Date: Wed, 18 Jan 2012 16:39:31 +0000 [thread overview]
Message-ID: <1326904771-12416-5-git-send-email-anprice@redhat.com> (raw)
In-Reply-To: <1326904771-12416-1-git-send-email-anprice@redhat.com>
Currently mkfs.gfs2 does not warn that the lock table has been omitted,
it just complains about a missing colon in the lock table. It also
prefixes error messages with the absolute path of the source file. This
patch removes the path from error messages (in mkfs and edit) and adds a
check for an empty lock table.
Signed-off-by: Andrew Price <anprice@redhat.com>
---
gfs2/edit/hexedit.h | 1 -
gfs2/mkfs/gfs2_mkfs.h | 1 -
gfs2/mkfs/main_mkfs.c | 4 ++++
3 files changed, 4 insertions(+), 2 deletions(-)
diff --git a/gfs2/edit/hexedit.h b/gfs2/edit/hexedit.h
index b05b5c0..dd76810 100644
--- a/gfs2/edit/hexedit.h
+++ b/gfs2/edit/hexedit.h
@@ -129,7 +129,6 @@ static __inline__ __attribute__((noreturn, format (printf, 1, 2)))
void die(const char *fmt, ...)
{
va_list ap;
- fprintf(stderr, "%s: ", __FILE__);
va_start(ap, fmt);
vfprintf(stderr, fmt, ap);
va_end(ap);
diff --git a/gfs2/mkfs/gfs2_mkfs.h b/gfs2/mkfs/gfs2_mkfs.h
index d7d7da7..231f370 100644
--- a/gfs2/mkfs/gfs2_mkfs.h
+++ b/gfs2/mkfs/gfs2_mkfs.h
@@ -24,7 +24,6 @@ static __inline__ __attribute__((noreturn, format (printf, 1, 2)))
void die(const char *fmt, ...)
{
va_list ap;
- fprintf(stderr, "%s: ", __FILE__);
va_start(ap, fmt);
vfprintf(stderr, fmt, ap);
va_end(ap);
diff --git a/gfs2/mkfs/main_mkfs.c b/gfs2/mkfs/main_mkfs.c
index 3658fd4..7c93621 100644
--- a/gfs2/mkfs/main_mkfs.c
+++ b/gfs2/mkfs/main_mkfs.c
@@ -257,6 +257,10 @@ static void test_locking(char *lockproto, char *locktable)
/* Nolock is always ok. */
} else if (strcmp(lockproto, "lock_gulm") == 0 ||
strcmp(lockproto, "lock_dlm") == 0) {
+ if (locktable == NULL || *locktable == '\0') {
+ fprintf(stderr, _("No lock table specified.\n"));
+ exit(-1);
+ }
for (c = locktable; *c; c++) {
if (isspace(*c))
die( _("locktable error: contains space characters\n"));
--
1.7.7.5
next prev parent reply other threads:[~2012-01-18 16:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-18 16:39 [Cluster-devel] [PATCH 1/5] fsck.gfs2: Plug memory leak in check_system_dir() Andrew Price
2012-01-18 16:39 ` [Cluster-devel] [PATCH 2/5] fsck.gfs2: Fix null pointer deref " Andrew Price
2012-01-18 16:39 ` [Cluster-devel] [PATCH 3/5] fsck.gfs2: Plug a leak in find_block_ref() Andrew Price
2012-01-18 16:39 ` [Cluster-devel] [PATCH 4/5] fsck.gfs2: Remove unused hash.c, hash.h Andrew Price
2012-01-18 16:39 ` Andrew Price [this message]
2012-01-18 16:48 ` [Cluster-devel] [PATCH 5/5] mkfs.gfs2: Improve error messages Steven Whitehouse
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=1326904771-12416-5-git-send-email-anprice@redhat.com \
--to=anprice@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 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).