All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andreas Dilger <adilger@turbolabs.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] [PATCH] fix oops when snapshots get full
Date: Thu, 11 Oct 2001 15:37:24 -0600	[thread overview]
Message-ID: <20011011153724.J8382@turbolinux.com> (raw)
In-Reply-To: <1532480000.1002834194@tiny>

On Oct 11, 2001  17:03 -0400, Chris Mason wrote:
> > 3) The alternative would be to check lv->lv_block_exception inside
> >    lvm_snapshot_remap_block() instead of in the callers (returning "1"
> >    if it is NULL, and we don't want to do remap).  This would avoid any
> >    problems in the future if someone else calls lvm_snapshot_remap_block()
> >    without checking lv_block_exception first.  Untested patch below which
> >    should be equivalent to your previous patch.
> 
> The only thing I don't like about this is that it makes it hides
> the fact that lvm_snapshot_COW and a few other calls depend on 
> block_exception being valid.  The code certainly looks right though,
> just a matter of style.

Well, lvm_snapshot_COW() is only called from one place, AFAICS, which
is in __remap_snapshot() after we call lvm_snapshot_remap_block(), so
we should be OK (could add a comment about this, and also the fact that
you need to hold the lv_lock to call this function in the first place.

Cheers, Andreas
--
Andreas Dilger  \ "If a man ate a pound of pasta and a pound of antipasto,
                 \  would they cancel out, leaving him still hungry?"
http://www-mddsp.enel.ucalgary.ca/People/adilger/               -- Dogbert

  reply	other threads:[~2001-10-11 21:37 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-11 17:49 [linux-lvm] [PATCH] fix oops when snapshots get full Chris Mason
2001-10-11 19:57 ` Andreas Dilger
2001-10-11 21:03   ` Chris Mason
2001-10-11 21:37     ` Andreas Dilger [this message]
2001-10-12  7:53   ` Joe Thornber

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=20011011153724.J8382@turbolinux.com \
    --to=adilger@turbolabs.com \
    --cc=linux-lvm@sistina.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.