From: Mike Snitzer <snitzer@redhat.com>
To: Mikulas Patocka <mpatocka@redhat.com>
Cc: dm-devel@redhat.com
Subject: Re: [dm-devel] dm-integrity: fix the maximum number of arguments
Date: Tue, 12 Jan 2021 15:04:17 -0500 [thread overview]
Message-ID: <20210112200417.GA15241@redhat.com> (raw)
In-Reply-To: <alpine.LRH.2.02.2101121453090.31583@file01.intranet.prod.int.rdu2.redhat.com>
On Tue, Jan 12 2021 at 2:54pm -0500,
Mikulas Patocka <mpatocka@redhat.com> wrote:
> Advance the maximum number of arguments to 15.
>
> Signed-off-by: Mikulas Patocka <mpatocka@redhat.com>
> Cc: stable@vger.kernel.org # v4.19+
>
> ---
> drivers/md/dm-integrity.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> Index: linux-2.6/drivers/md/dm-integrity.c
> ===================================================================
> --- linux-2.6.orig/drivers/md/dm-integrity.c 2021-01-12 20:45:23.000000000 +0100
> +++ linux-2.6/drivers/md/dm-integrity.c 2021-01-12 20:46:15.000000000 +0100
> @@ -3792,7 +3792,7 @@ static int dm_integrity_ctr(struct dm_ta
> unsigned extra_args;
> struct dm_arg_set as;
> static const struct dm_arg _args[] = {
> - {0, 9, "Invalid number of feature args"},
> + {0, 15, "Invalid number of feature args"},
> };
> unsigned journal_sectors, interleave_sectors, buffer_sectors, journal_watermark, sync_msec;
> bool should_write_sb;
Can you please expand on which args weren't accounted for?
Which commit introduced the problem? (I'd like a "Fixes:" reference)
Thanks,
Mike
--
dm-devel mailing list
dm-devel@redhat.com
https://www.redhat.com/mailman/listinfo/dm-devel
next prev parent reply other threads:[~2021-01-12 20:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-12 19:54 [dm-devel] [PATCH] dm-integrity: fix the maximum number of arguments Mikulas Patocka
2021-01-12 20:04 ` Mike Snitzer [this message]
2021-01-12 20:21 ` [dm-devel] " Mikulas Patocka
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=20210112200417.GA15241@redhat.com \
--to=snitzer@redhat.com \
--cc=dm-devel@redhat.com \
--cc=mpatocka@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.