From: Kevin Wolf <kwolf@redhat.com>
To: Eric Blake <eblake@redhat.com>
Cc: nhuck15@gmail.com, qemu-devel@nongnu.org, qemu-block@nongnu.org,
ppandit@redhat.com
Subject: Re: [PATCH 2/2] vvfat: Fix array_remove_slice()
Date: Wed, 24 Jun 2020 14:42:43 +0200 [thread overview]
Message-ID: <20200624124243.GC9253@linux.fritz.box> (raw)
In-Reply-To: <ca89d6ae-734f-66b0-3862-e41ab4ce6455@redhat.com>
Am 23.06.2020 um 20:30 hat Eric Blake geschrieben:
> On 6/23/20 12:55 PM, Kevin Wolf wrote:
> > array_remove_slice() calls array_roll() with array->next - 1 as the
> > destination index. This is only correct for count == 1, otherwise we're
> > writing past the end of the array. array->next - count would be correct.
> >
> > However, this is the only place ever calling array_roll(), so this
> > rather complicated operation isn't even necessary.
> >
> > Fix the problem and simplify the code by replacing it with a single
> > memmove() call. array_roll() can now be removed.
> >
> > Reported-by: Nathan Huckleberry <nhuck15@gmail.com>
> > Signed-off-by: Kevin Wolf <kwolf@redhat.com>
> > ---
> > block/vvfat.c | 42 +++++-------------------------------------
> > 1 file changed, 5 insertions(+), 37 deletions(-)
> >
> > diff --git a/block/vvfat.c b/block/vvfat.c
> > index 2fab371258..d6e464c595 100644
> > --- a/block/vvfat.c
> > +++ b/block/vvfat.c
> > @@ -140,48 +140,16 @@ static inline void* array_insert(array_t* array,unsigned int index,unsigned int
> > return array->pointer+index*array->item_size;
> > }
> > -/* this performs a "roll", so that the element which was at index_from becomes
> > - * index_to, but the order of all other elements is preserved. */
> > -static inline int array_roll(array_t* array,int index_to,int index_from,int count)
>
> If I understand the intent from just the comment, the old code would take a
> directory listing of six files:
>
> ABCDEF
>
> and on the request to delete file C, would produce:
>
> ABFDE
>
> by moving just F, instead of all of DEF.
I think what the old code did was actually moving C, not F, so you get:
ABDEFC
And then you reduce the array size by one so that C isn't visible any
more. My code preserves this behaviour, except that the invisible final
element is a copy of F instead C now.
Kevin
next prev parent reply other threads:[~2020-06-24 12:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-23 17:55 [PATCH 0/2] vvfat: Two small patches Kevin Wolf
2020-06-23 17:55 ` [PATCH 1/2] vvfat: Check that updated filenames are valid Kevin Wolf
2020-06-23 18:21 ` Eric Blake
2020-06-24 12:36 ` Kevin Wolf
2020-06-23 17:55 ` [PATCH 2/2] vvfat: Fix array_remove_slice() Kevin Wolf
2020-06-23 18:30 ` Eric Blake
2020-06-24 12:42 ` Kevin Wolf [this message]
2020-06-23 18:32 ` [PATCH 0/2] vvfat: Two small patches no-reply
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=20200624124243.GC9253@linux.fritz.box \
--to=kwolf@redhat.com \
--cc=eblake@redhat.com \
--cc=nhuck15@gmail.com \
--cc=ppandit@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
/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;
as well as URLs for NNTP newsgroup(s).