From: "Heinz J. Mauelshagen" <Mauelshagen@sistina.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] typo in CVS: LVM/kernel/lvm.c
Date: Mon, 7 May 2001 10:34:57 +0000 [thread overview]
Message-ID: <20010507103457.C25752@sistina.com> (raw)
In-Reply-To: <20010506101133.A642@66bassett.freeserve.co.uk>; from thornber@btconnect.com on Sun, May 06, 2001 at 10:11:33AM +0100
On Sun, May 06, 2001 at 10:11:33AM +0100, Joe Thornber wrote:
> On Sat, May 05, 2001 at 11:24:43PM +0200, Gergely Tamas wrote:
> > Hi!
> >
> > There is a typo in CVS:LVM/kernel/lvm.c
> >
> > Gergely
>
> Yes, I just looked at cvs, you're right. Thanks.
>
> Heinz & Patrick what are you playing at !?
>
> lvm.c revision 1.10
> -------------------
>
> o why did you feel the need to change the name of __update_hardblocksize ?
>
Just to adopt the new naming in > 2.4.3
> o why change the name of the max_hardblocksize variable.
Same as above.
>
> o you've duplicated ~10 lines of code instead of putting them into a seperate
> function such as:
No, just added the (wrong) version check and function call.
>
> static inline ulong _get_hard_block_size(kdev_t dev) {
> etc.
> }
I don't mind.
>
> o The code has a typo 'get_hardbsect_size' from which we can conclude that it
> was *never* compiled for a kernel < 2.4.4
Oops, my fault ;-)
>
> o The version check itself is wrong.
>
> It looks to me like a botched search and replace without subsequent
> testing, or even a cvs diff before checkin.
May be... ;-)
>
> lvm.c revision 1.11
> -------------------
>
> o typo still there, it can't have been tested.
>
> lvm.c revision 1.12
> -------------------
>
> Patrick, you correctly fix most of the remaining mistakes apart from
> the version number. But what are all the other code changes that have
> slipped in ? They aren't mentioned in the checkin message, are they
> meant to be there ?
>
> - Joe
>
>
>
> >
> > --- LVM/kernel/lvm.c.orig Thu May 3 15:37:19 2001
> > +++ LVM/kernel/lvm.c Sat May 5 23:01:22 2001
> > @@ -1879,7 +1879,7 @@
> > int max_hardsectsize = 0, hardsectsize;
> >
> > for (le = 0; le < lv->lv_allocated_le; le++) {
> > -#if LINUX_VERSION_CODE <= KERNEL_VERSION ( 2, 4, 4)
> > +#if LINUX_VERSION_CODE <= KERNEL_VERSION ( 2, 4, 3)
> > hardsectsize = get_hardblocksize(lv->lv_current_pe[le].dev);
> > #else
> > hardsectsize = get_hardsect_size(lv->lv_current_pe[le].dev);
> > @@ -1892,7 +1892,7 @@
> >
> > if (lv->lv_access & LV_SNAPSHOT) {
> > for (e = 0; e < lv->lv_remap_end; e++) {
> > -#if LINUX_VERSION_CODE <= KERNEL_VERSION ( 2, 4, 4)
> > +#if LINUX_VERSION_CODE <= KERNEL_VERSION ( 2, 4, 3)
> > hardsectsize = get_hardblocksize( lv->lv_block_exception[e].rdev_new);
> > #else
> > hardsectsize = get_hardsect_size( lv->lv_block_exception[e].rdev_new);
> >
> >
> >
> > _______________________________________________
> > linux-lvm mailing list
> > linux-lvm@sistina.com
> > http://lists.sistina.com/mailman/listinfo/linux-lvm
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@sistina.com
> http://lists.sistina.com/mailman/listinfo/linux-lvm
--
Regards,
Heinz -- The LVM Guy --
*** Software bugs are stupid.
Nevertheless it needs not so stupid people to solve them ***
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Heinz Mauelshagen Sistina Software Inc.
Senior Consultant/Developer Am Sonnenhang 11
56242 Marienrachdorf
Germany
Mauelshagen@Sistina.com +49 2626 141200
FAX 924446
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
next prev parent reply other threads:[~2001-05-07 10:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-05 21:24 [linux-lvm] typo in CVS: LVM/kernel/lvm.c Gergely Tamas
2001-05-06 9:11 ` Joe Thornber
2001-05-06 12:55 ` Ed Tomlinson
2001-05-07 9:08 ` Patrick Caulfield
2001-05-07 10:34 ` Heinz J. Mauelshagen [this message]
2001-05-08 9:10 ` Patrick Caulfield
2001-05-08 9:43 ` Joe Thornber
2001-05-08 10:52 ` Patrick Caulfield
2001-05-08 14:38 ` Heinz J. Mauelshagen
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=20010507103457.C25752@sistina.com \
--to=mauelshagen@sistina.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.