From: Alex Elder <elder@linaro.org>
To: davem@davemloft.net, kuba@kernel.org
Cc: leon@kernel.org, andrew@lunn.ch, bjorn.andersson@linaro.org,
evgreen@chromium.org, cpratapa@codeaurora.org,
subashab@codeaurora.org, elder@kernel.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next v2 0/2] net: ipa: fix validation
Date: Mon, 22 Mar 2021 08:22:20 -0500 [thread overview]
Message-ID: <f1b719d3-c7f2-1815-9cfe-19ea23944cce@linaro.org> (raw)
In-Reply-To: <20210320141729.1956732-1-elder@linaro.org>
On 3/20/21 9:17 AM, Alex Elder wrote:
> There is sanity checking code in the IPA driver that's meant to be
> enabled only during development. This allows the driver to make
> certain assumptions, but not have to verify those assumptions are
> true at (operational) runtime. This code is built conditional on
> IPA_VALIDATION, set (if desired) inside the IPA makefile.
>
> Unfortunately, this validation code has some errors. First, there
> are some mismatched arguments supplied to some dev_err() calls in
> ipa_cmd_table_valid() and ipa_cmd_header_valid(), and these are
> exposed if validation is enabled. Second, the tag that enables
> this conditional code isn't used consistently (it's IPA_VALIDATE
> in some spots and IPA_VALIDATION in others).
>
> This series fixes those two problems with the conditional validation
> code.
After much back-and-forth with Leon Romanovsky:
--> I retract this series <--
I will include these patches in a future series that will
do cleanup of this validation code more completely.
Thanks.
-Alex
> Version 2 removes the two patches that introduced ipa_assert(). It
> also modifies the description in the first patch so that it mentions
> the changes made to ipa_cmd_table_valid().
>
> -Alex
>
> Alex Elder (2):
> net: ipa: fix init header command validation
> net: ipa: fix IPA validation
>
> drivers/net/ipa/Makefile | 2 +-
> drivers/net/ipa/gsi_trans.c | 8 ++---
> drivers/net/ipa/ipa_cmd.c | 54 ++++++++++++++++++++++------------
> drivers/net/ipa/ipa_cmd.h | 6 ++--
> drivers/net/ipa/ipa_endpoint.c | 6 ++--
> drivers/net/ipa/ipa_main.c | 6 ++--
> drivers/net/ipa/ipa_mem.c | 6 ++--
> drivers/net/ipa/ipa_table.c | 6 ++--
> drivers/net/ipa/ipa_table.h | 6 ++--
> 9 files changed, 58 insertions(+), 42 deletions(-)
>
next prev parent reply other threads:[~2021-03-22 13:24 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-20 14:17 Alex Elder
2021-03-20 14:17 ` [PATCH net-next v2 1/2] net: ipa: fix init header command validation Alex Elder
2021-03-20 14:17 ` [PATCH net-next v2 2/2] net: ipa: fix IPA validation Alex Elder
2021-03-21 8:21 ` Leon Romanovsky
2021-03-21 13:21 ` Alex Elder
2021-03-21 13:49 ` Leon Romanovsky
2021-03-21 17:19 ` Alex Elder
2021-03-22 6:40 ` Leon Romanovsky
2021-03-22 13:17 ` Alex Elder
2021-03-22 14:17 ` Leon Romanovsky
2021-03-22 15:06 ` Alex Elder
2021-03-22 22:56 ` Andrew Lunn
2021-03-23 0:03 ` Alex Elder
2021-03-22 13:22 ` Alex Elder [this message]
2021-03-22 14:16 ` [PATCH net-next v2 0/2] net: ipa: fix validation Leon Romanovsky
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=f1b719d3-c7f2-1815-9cfe-19ea23944cce@linaro.org \
--to=elder@linaro.org \
--cc=andrew@lunn.ch \
--cc=bjorn.andersson@linaro.org \
--cc=cpratapa@codeaurora.org \
--cc=davem@davemloft.net \
--cc=elder@kernel.org \
--cc=evgreen@chromium.org \
--cc=kuba@kernel.org \
--cc=leon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=subashab@codeaurora.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
all inboxes | Powered by JetHome®