qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Denis V. Lunev" <den@virtuozzo.com>
To: Alexander Ivanov <alexander.ivanov@virtuozzo.com>, qemu-devel@nongnu.org
Cc: qemu-block@nongnu.org, stefanha@redhat.com,
	vsementsov@yandex-team.ru, kwolf@redhat.com, hreitz@redhat.com
Subject: Re: [PATCH v8 01/10] parallels: Fix comments formatting inside parallels driver
Date: Wed, 26 Jul 2023 11:41:42 +0200	[thread overview]
Message-ID: <9d67fa44-42fe-8f04-c24c-de254aef1b83@virtuozzo.com> (raw)
In-Reply-To: <20230718104432.1130469-2-alexander.ivanov@virtuozzo.com>

On 7/18/23 12:44, Alexander Ivanov wrote:
> This patch is technically necessary as git patch rendering could result
> in moving some code from one place to the another and that hits
> checkpatch.pl warning. This problem specifically happens within next
> series.
>
> Signed-off-by: Alexander Ivanov <alexander.ivanov@virtuozzo.com>
> ---
>   block/parallels.c | 18 ++++++++++++------
>   1 file changed, 12 insertions(+), 6 deletions(-)
>
> diff --git a/block/parallels.c b/block/parallels.c
> index 18e34aef28..c7b2ed5a54 100644
> --- a/block/parallels.c
> +++ b/block/parallels.c
> @@ -188,7 +188,8 @@ allocate_clusters(BlockDriverState *bs, int64_t sector_num,
>       idx = sector_num / s->tracks;
>       to_allocate = DIV_ROUND_UP(sector_num + *pnum, s->tracks) - idx;
>   
> -    /* This function is called only by parallels_co_writev(), which will never
> +    /*
> +     * This function is called only by parallels_co_writev(), which will never
>        * pass a sector_num at or beyond the end of the image (because the block
>        * layer never passes such a sector_num to that function). Therefore, idx
>        * is always below s->bat_size.
> @@ -196,7 +197,8 @@ allocate_clusters(BlockDriverState *bs, int64_t sector_num,
>        * exceed the image end. Therefore, idx + to_allocate cannot exceed
>        * s->bat_size.
>        * Note that s->bat_size is an unsigned int, therefore idx + to_allocate
> -     * will always fit into a uint32_t. */
> +     * will always fit into a uint32_t.
> +     */
>       assert(idx < s->bat_size && idx + to_allocate <= s->bat_size);
>   
>       space = to_allocate * s->tracks;
> @@ -230,13 +232,15 @@ allocate_clusters(BlockDriverState *bs, int64_t sector_num,
>           }
>       }
>   
> -    /* Try to read from backing to fill empty clusters
> +    /*
> +     * Try to read from backing to fill empty clusters
>        * FIXME: 1. previous write_zeroes may be redundant
>        *        2. most of data we read from backing will be rewritten by
>        *           parallels_co_writev. On aligned-to-cluster write we do not need
>        *           this read at all.
>        *        3. it would be good to combine write of data from backing and new
> -     *           data into one write call */
> +     *           data into one write call.
> +     */
>       if (bs->backing) {
>           int64_t nb_cow_sectors = to_allocate * s->tracks;
>           int64_t nb_cow_bytes = nb_cow_sectors << BDRV_SECTOR_BITS;
> @@ -864,8 +868,10 @@ static int parallels_open(BlockDriverState *bs, QDict *options, int flags,
>           s->data_end = ROUND_UP(bat_entry_off(s->bat_size), BDRV_SECTOR_SIZE);
>       }
>       if (s->data_end < s->header_size) {
> -        /* there is not enough unused space to fit to block align between BAT
> -           and actual data. We can't avoid read-modify-write... */
> +        /*
> +         * There is not enough unused space to fit to block align between BAT
> +         * and actual data. We can't avoid read-modify-write...
> +         */
>           s->header_size = size;
>       }
>   
Reviewed-by: Denis V. Lunev <den@openvz.org>


  reply	other threads:[~2023-07-26  9:43 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-18 10:44 [PATCH v8 00/10] parallels: Add duplication check, repair at open, fix bugs Alexander Ivanov
2023-07-18 10:44 ` [PATCH v8 01/10] parallels: Fix comments formatting inside parallels driver Alexander Ivanov
2023-07-26  9:41   ` Denis V. Lunev [this message]
2023-07-18 10:44 ` [PATCH v8 02/10] parallels: Incorrect data end calculation in parallels_open() Alexander Ivanov
2023-07-18 10:44 ` [PATCH v8 03/10] parallels: Check if data_end greater than the file size Alexander Ivanov
2023-07-18 10:44 ` [PATCH v8 04/10] parallels: Add "explicit" argument to parallels_check_leak() Alexander Ivanov
2023-07-18 10:44 ` [PATCH v8 05/10] parallels: Add data_start field to BDRVParallelsState Alexander Ivanov
2023-07-18 10:44 ` [PATCH v8 06/10] parallels: Add checking and repairing duplicate offsets in BAT Alexander Ivanov
2023-07-18 10:44 ` [PATCH v8 07/10] parallels: Image repairing in parallels_open() Alexander Ivanov
2023-07-18 10:44 ` [PATCH v8 08/10] parallels: Use bdrv_co_getlength() in parallels_check_outside_image() Alexander Ivanov
2023-07-18 10:44 ` [PATCH v8 09/10] parallels: Add data_off check Alexander Ivanov
2023-07-18 10:44 ` [PATCH v8 10/10] parallels: Add data_off repairing to parallels_open() Alexander Ivanov

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=9d67fa44-42fe-8f04-c24c-de254aef1b83@virtuozzo.com \
    --to=den@virtuozzo.com \
    --cc=alexander.ivanov@virtuozzo.com \
    --cc=hreitz@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=qemu-block@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@redhat.com \
    --cc=vsementsov@yandex-team.ru \
    /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).