From: Leon Romanovsky <leon@kernel.org>
To: Alex Elder <elder@linaro.org>
Cc: davem@davemloft.net, kuba@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 2/2] net: ipa: fix IPA validation
Date: Mon, 22 Mar 2021 16:17:24 +0200 [thread overview]
Message-ID: <YFim9CWuu45FcdcN@unreal> (raw)
In-Reply-To: <f152c274-6fe0-37a1-3723-330b7bfe249a@linaro.org>
On Mon, Mar 22, 2021 at 08:17:59AM -0500, Alex Elder wrote:
> On 3/22/21 1:40 AM, Leon Romanovsky wrote:
> > > I'd like to suggest a plan so I can begin to make progress,
> > > but do so in a way you/others think is satisfactory.
> > > - I would first like to fix the existing bugs, namely that
> > > if IPA_VALIDATION is defined there are build errors, and
> > > that IPA_VALIDATION is not consistently used. That is
> > > this 2-patch series.
> > The thing is that IPA_VALIDATION is not defined in the upstream kernel.
> > There is nothing to be fixed in netdev repository
> >
> > > - I assure you that my goal is to simplify the code that
> > > does this sort of checking. So here are some specific
> > > things I can implement in the coming weeks toward that:
> > > - Anything that can be checked at build time, will
> > > be checked with BUILD_BUG_ON().
> > +1
> >
> > > - Anything checked with BUILD_BUG_ON() will*not*
> > > be conditional. I.e. it won't be inside an
> > > #ifdef IPA_VALIDATION block.
> > > - I will review all remaining VALIDATION code (which
> > > can't--or can't always--be checked at build time),
> > > If it looks prudent to make it*always* be checked,
> > > I will make it always be checked (not conditional
> > > on IPA_VALIDATION).
> > +1
> >
> > > The result should clearly separate checks that can be done
> > > at build time from those that can't.
> > >
> > > And with what's left (especially on that third sub-bullet)
> > > I might have some better examples with which to argue
> > > for something different. Or I might just concede that
> > > you were right all along.
> > I hope so.
>
> I came up with a solution last night that I'm going to try
> to implement. I will still do the things I mention above.
>
> The solution is to create a user space tool inside the
> drivers/net/ipa directory that will link with the kernel
> source files and will perform all the basic one-time checks
> I want to make.
We are not talking about putting this tool in upstream repo, right?
If yes, please get buy-in from David/Jakub first.
Thanks
next prev parent reply other threads:[~2021-03-22 14:18 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-20 14:17 [PATCH net-next v2 0/2] net: ipa: fix validation 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 [this message]
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 ` [PATCH net-next v2 0/2] net: ipa: fix validation Alex Elder
2021-03-22 14:16 ` 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=YFim9CWuu45FcdcN@unreal \
--to=leon@kernel.org \
--cc=andrew@lunn.ch \
--cc=bjorn.andersson@linaro.org \
--cc=cpratapa@codeaurora.org \
--cc=davem@davemloft.net \
--cc=elder@kernel.org \
--cc=elder@linaro.org \
--cc=evgreen@chromium.org \
--cc=kuba@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;
as well as URLs for NNTP newsgroup(s).