From: Theodore Tso <tytso@MIT.EDU>
To: Eric Sandeen <sandeen@redhat.com>
Cc: ext4 development <linux-ext4@vger.kernel.org>,
pspencer@fields.utoronto.ca
Subject: Re: [PATCH] e2fsprogs: error checking in blkid/devname.c
Date: Fri, 22 Feb 2008 08:16:22 -0500 [thread overview]
Message-ID: <20080222131622.GK20118@mit.edu> (raw)
In-Reply-To: <47BDF6C9.8090009@redhat.com>
On Thu, Feb 21, 2008 at 04:10:17PM -0600, Eric Sandeen wrote:
> This is for RH Bugzilla #433857:
> rpc.mountd segfaults due to uninitialized value in e2fsprogs devname.c
>
> https://bugzilla.redhat.com/show_bug.cgi?id=433857
>
> which did some very helpful analysis & provided a patch.
>
> This patch is based on that, but checks all the devicemapper calls,
> and does some goto error handling / unwrapping, in the same style as
> the device-mapper lib code itself.
This looks good, but I assume that the bug was caused by some race
condition where if you try to call dm_task_get_info() while some other
process is creating or removing a snapshot, dm_task_get_info() is
returning some kind of EAGAIN, or some other "Try again; we're busy"
error, right?
If that is the case, can you try to find out what error is being
returned? It may be the right thing to do is to check to see if we
are getting a "resource is locked; try again in a sec" error message,
and retry the dm_task_get_info(), instead of just returning a failure.
Thanks!!
- Ted
next prev parent reply other threads:[~2008-02-22 13:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-21 22:10 [PATCH] e2fsprogs: error checking in blkid/devname.c Eric Sandeen
2008-02-22 13:16 ` Theodore Tso [this message]
2008-02-22 15:02 ` Eric Sandeen
2008-02-22 15:44 ` Theodore Tso
2008-02-22 16:16 ` Eric Sandeen
2008-02-22 16:33 ` Theodore Tso
2008-02-22 16:52 ` Eric Sandeen
2008-02-22 18:22 ` Theodore Tso
2008-02-22 18:10 ` Philip Spencer
2008-02-22 18:25 ` Theodore Tso
2008-02-22 15:46 ` Philip Spencer
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=20080222131622.GK20118@mit.edu \
--to=tytso@mit.edu \
--cc=linux-ext4@vger.kernel.org \
--cc=pspencer@fields.utoronto.ca \
--cc=sandeen@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