From: Christoph Hellwig <hch@infradead.org>
To: Milan Broz <mbroz@redhat.com>
Cc: Christoph Hellwig <hch@infradead.org>,
device-mapper development <dm-devel@redhat.com>
Subject: Re: Re: [PATCH] dm: fix freeze_bdev() return value check
Date: Tue, 25 Sep 2007 16:56:24 +0100 [thread overview]
Message-ID: <20070925155624.GA28595@infradead.org> (raw)
In-Reply-To: <46F92EBD.9090007@redhat.com>
On Tue, Sep 25, 2007 at 05:52:29PM +0200, Milan Broz wrote:
> Akinobu Mita wrote:
> > 2007/9/24, Akinobu Mita <akinobu.mita@gmail.com>:
> >> freeze_bdev() does not return errno as pointer on failure.
> >> This patch fixes the return value check.
> >
> ...
> > But there is no reason to check the return value with IS_ERR().
> > Because freeze_bdev return NULL or valid super block
>
> Yes, but there is another place in kernel using this check
> (see /fs/xfs/xfs_fsops.c)
>
> Probably question for Christoph Hellwig - some changes related to
> returning error in frezze_bdev() were planned but never commited.
> (see list archive)
>
> Otherwise test for IS_ERR() should be removed.
The plan was to change freeze_bdev to do a trylock un s_umount_sem
and return SBUSY if it fails to avoid the deadlock scenario where
people called xfs_freeze and got another freeze request from dm.
I don't remember why this never got it, it's probably worth sending
a patch like this again.
prev parent reply other threads:[~2007-09-25 15:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-24 10:56 [PATCH] dm: fix freeze_bdev() return value check Akinobu Mita
2007-09-24 13:04 ` Alasdair G Kergon
2007-09-25 14:23 ` Akinobu Mita
2007-09-25 15:52 ` Milan Broz
2007-09-25 15:56 ` Christoph Hellwig [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=20070925155624.GA28595@infradead.org \
--to=hch@infradead.org \
--cc=dm-devel@redhat.com \
--cc=mbroz@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.