From: Zdenek Kabelac <zkabelac@redhat.com>
To: lvm-devel@redhat.com
Subject: Re: LVM2 lib/activate/dev_manager.c lib/cache/lvmc ...
Date: Thu, 17 Dec 2009 10:39:46 +0100 [thread overview]
Message-ID: <4B29FC62.4000003@redhat.com> (raw)
In-Reply-To: <20091216192214.22164.qmail@sourceware.org>
Dne 16.12.2009 20:22, mornfall at sourceware.org napsal(a):
> Modified files:
> lib/activate : dev_manager.c
> lib/cache : lvmcache.c
> lib/format_text: export.c text_label.c
> lib/locking : locking.c
> lib/log : log.c log.h
> lib/metadata : metadata.c
> lib/mm : memlock.c
> lib/striped : striped.c
> tools : lvm.c lvmcmdline.c
>
> Log message:
> #define an INTERNAL_ERROR macro and use it throughout LVM.
>
> > - log_error("Internal error: Nested locking attempted on VG %s.",
> + log_error(INTERNAL_ERROR "Nested locking attempted on VG %s.",
> vgname);
Maybe we could introduce new macro
log_IERROR() & log_IDEBUG() to prepend string INTERNAL_ERROR and make the line
shorter and more readable ?
And check for abort() on internal error could be used only in case of these
macros. (thus simplify print_log() function)
Also - it looks like when _log_suppress == 2 and abort_on_internal_errors is
set - the abort() is skipped - is this bug or features ?
Zdenek
prev parent reply other threads:[~2009-12-17 9:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-16 19:22 LVM2 lib/activate/dev_manager.c lib/cache/lvmc mornfall
2009-12-17 9:39 ` Zdenek Kabelac [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=4B29FC62.4000003@redhat.com \
--to=zkabelac@redhat.com \
--cc=lvm-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.