* [PATCH] KEYS: fix compilation warnings in the dump_options() function
@ 2025-10-24 6:11 Ye Bin
2025-10-24 7:02 ` yebin
2025-10-27 20:04 ` Jarkko Sakkinen
0 siblings, 2 replies; 7+ messages in thread
From: Ye Bin @ 2025-10-24 6:11 UTC (permalink / raw)
To: a.fatoum, kernel, James.Bottomley, jarkko, zohar, dhowells, paul,
jmorris, serge, linux-integrity, keyrings, linux-security-module,
yebin, yebin10
From: Ye Bin <yebin10@huawei.com>
There's issue as follows:
security/keys/trusted-keys/trusted_caam.c: In function ‘dump_options’:
security/keys/trusted-keys/trusted_caam.c:37:20: note: the ABI of passing struct with a flexible array member has changed in GCC 4.4
37 | static inline void dump_options(struct caam_pkey_info pkey_info)
| ^~~~~~~~~~~~
To solve the above problem, pass 'struct caam_pkey_info*' type parameter
to the dump_options() function.
Fixes: 9eb25ca6c973 ("KEYS: trusted: caam based protected key")
Signed-off-by: Ye Bin <yebin10@huawei.com>
---
security/keys/trusted-keys/trusted_caam.c | 10 +++++-----
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/security/keys/trusted-keys/trusted_caam.c b/security/keys/trusted-keys/trusted_caam.c
index 090099d1b04d..dd7a69bcf6a3 100644
--- a/security/keys/trusted-keys/trusted_caam.c
+++ b/security/keys/trusted-keys/trusted_caam.c
@@ -29,12 +29,12 @@ static const match_table_t key_tokens = {
};
#ifdef CAAM_DEBUG
-static inline void dump_options(struct caam_pkey_info pkey_info)
+static inline void dump_options(struct caam_pkey_info *pkey_info)
{
- pr_info("key encryption algo %d\n", pkey_info.key_enc_algo);
+ pr_info("key encryption algo %d\n", pkey_info->key_enc_algo);
}
#else
-static inline void dump_options(struct caam_pkey_info pkey_info)
+static inline void dump_options(struct caam_pkey_info *pkey_info)
{
}
#endif
@@ -108,7 +108,7 @@ static int trusted_caam_seal(struct trusted_key_payload *p, char *datablob)
ret = get_pkey_options(datablob, &info.pkey_info);
if (ret < 0)
return 0;
- dump_options(info.pkey_info);
+ dump_options(&info.pkey_info);
}
ret = caam_encap_blob(blobifier, &info);
@@ -140,7 +140,7 @@ static int trusted_caam_unseal(struct trusted_key_payload *p, char *datablob)
ret = get_pkey_options(datablob, &info.pkey_info);
if (ret < 0)
return 0;
- dump_options(info.pkey_info);
+ dump_options(&info.pkey_info);
p->key_len = p->blob_len + sizeof(struct caam_pkey_info);
memcpy(p->key, &info.pkey_info, sizeof(struct caam_pkey_info));
--
2.34.1
^ permalink raw reply related [flat|nested] 7+ messages in thread* Re: [PATCH] KEYS: fix compilation warnings in the dump_options() function 2025-10-24 6:11 [PATCH] KEYS: fix compilation warnings in the dump_options() function Ye Bin @ 2025-10-24 7:02 ` yebin 2025-10-24 8:10 ` Ahmad Fatoum 2025-10-27 20:04 ` Jarkko Sakkinen 1 sibling, 1 reply; 7+ messages in thread From: yebin @ 2025-10-24 7:02 UTC (permalink / raw) To: a.fatoum, kernel, James.Bottomley, jarkko, zohar, dhowells, paul, jmorris, serge, linux-integrity, keyrings, linux-security-module, yebin10 Ignore this patch as 275a9a3f9b6a(“KEYS: trusted: Pass argument by pointer in dump_options”)already fix this issue. On 2025/10/24 14:11, Ye Bin wrote: > From: Ye Bin <yebin10@huawei.com> > > There's issue as follows: > security/keys/trusted-keys/trusted_caam.c: In function ‘dump_options’: > security/keys/trusted-keys/trusted_caam.c:37:20: note: the ABI of passing struct with a flexible array member has changed in GCC 4.4 > 37 | static inline void dump_options(struct caam_pkey_info pkey_info) > | ^~~~~~~~~~~~ > > To solve the above problem, pass 'struct caam_pkey_info*' type parameter > to the dump_options() function. > > Fixes: 9eb25ca6c973 ("KEYS: trusted: caam based protected key") > Signed-off-by: Ye Bin <yebin10@huawei.com> > --- > security/keys/trusted-keys/trusted_caam.c | 10 +++++----- > 1 file changed, 5 insertions(+), 5 deletions(-) > > diff --git a/security/keys/trusted-keys/trusted_caam.c b/security/keys/trusted-keys/trusted_caam.c > index 090099d1b04d..dd7a69bcf6a3 100644 > --- a/security/keys/trusted-keys/trusted_caam.c > +++ b/security/keys/trusted-keys/trusted_caam.c > @@ -29,12 +29,12 @@ static const match_table_t key_tokens = { > }; > > #ifdef CAAM_DEBUG > -static inline void dump_options(struct caam_pkey_info pkey_info) > +static inline void dump_options(struct caam_pkey_info *pkey_info) > { > - pr_info("key encryption algo %d\n", pkey_info.key_enc_algo); > + pr_info("key encryption algo %d\n", pkey_info->key_enc_algo); > } > #else > -static inline void dump_options(struct caam_pkey_info pkey_info) > +static inline void dump_options(struct caam_pkey_info *pkey_info) > { > } > #endif > @@ -108,7 +108,7 @@ static int trusted_caam_seal(struct trusted_key_payload *p, char *datablob) > ret = get_pkey_options(datablob, &info.pkey_info); > if (ret < 0) > return 0; > - dump_options(info.pkey_info); > + dump_options(&info.pkey_info); > } > > ret = caam_encap_blob(blobifier, &info); > @@ -140,7 +140,7 @@ static int trusted_caam_unseal(struct trusted_key_payload *p, char *datablob) > ret = get_pkey_options(datablob, &info.pkey_info); > if (ret < 0) > return 0; > - dump_options(info.pkey_info); > + dump_options(&info.pkey_info); > > p->key_len = p->blob_len + sizeof(struct caam_pkey_info); > memcpy(p->key, &info.pkey_info, sizeof(struct caam_pkey_info)); > ^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [PATCH] KEYS: fix compilation warnings in the dump_options() function 2025-10-24 7:02 ` yebin @ 2025-10-24 8:10 ` Ahmad Fatoum 2025-10-28 2:39 ` yebin 0 siblings, 1 reply; 7+ messages in thread From: Ahmad Fatoum @ 2025-10-24 8:10 UTC (permalink / raw) To: yebin, kernel, James.Bottomley, jarkko, zohar, dhowells, paul, jmorris, serge, linux-integrity, keyrings, linux-security-module, yebin10 Hello, On 10/24/25 9:02 AM, yebin wrote: > Ignore this patch as 275a9a3f9b6a(“KEYS: trusted: Pass argument by > pointer in dump_options”)already fix this issue. What tree are you looking at? I can't find this commit in my git and the code you are purportedly patching never existed upstream. If you run into issues exclusive to a vendor fork, you need to submit your patches to the vendor. The upstream mailing lists are for upstream. Thanks, Ahmad > > On 2025/10/24 14:11, Ye Bin wrote: >> From: Ye Bin <yebin10@huawei.com> >> >> There's issue as follows: >> security/keys/trusted-keys/trusted_caam.c: In function ‘dump_options’: >> security/keys/trusted-keys/trusted_caam.c:37:20: note: the ABI of >> passing struct with a flexible array member has changed in GCC 4.4 >> 37 | static inline void dump_options(struct caam_pkey_info pkey_info) >> | ^~~~~~~~~~~~ >> >> To solve the above problem, pass 'struct caam_pkey_info*' type parameter >> to the dump_options() function. >> >> Fixes: 9eb25ca6c973 ("KEYS: trusted: caam based protected key") >> Signed-off-by: Ye Bin <yebin10@huawei.com> >> --- >> security/keys/trusted-keys/trusted_caam.c | 10 +++++----- >> 1 file changed, 5 insertions(+), 5 deletions(-) >> >> diff --git a/security/keys/trusted-keys/trusted_caam.c b/security/ >> keys/trusted-keys/trusted_caam.c >> index 090099d1b04d..dd7a69bcf6a3 100644 >> --- a/security/keys/trusted-keys/trusted_caam.c >> +++ b/security/keys/trusted-keys/trusted_caam.c >> @@ -29,12 +29,12 @@ static const match_table_t key_tokens = { >> }; >> >> #ifdef CAAM_DEBUG >> -static inline void dump_options(struct caam_pkey_info pkey_info) >> +static inline void dump_options(struct caam_pkey_info *pkey_info) >> { >> - pr_info("key encryption algo %d\n", pkey_info.key_enc_algo); >> + pr_info("key encryption algo %d\n", pkey_info->key_enc_algo); >> } >> #else >> -static inline void dump_options(struct caam_pkey_info pkey_info) >> +static inline void dump_options(struct caam_pkey_info *pkey_info) >> { >> } >> #endif >> @@ -108,7 +108,7 @@ static int trusted_caam_seal(struct >> trusted_key_payload *p, char *datablob) >> ret = get_pkey_options(datablob, &info.pkey_info); >> if (ret < 0) >> return 0; >> - dump_options(info.pkey_info); >> + dump_options(&info.pkey_info); >> } >> >> ret = caam_encap_blob(blobifier, &info); >> @@ -140,7 +140,7 @@ static int trusted_caam_unseal(struct >> trusted_key_payload *p, char *datablob) >> ret = get_pkey_options(datablob, &info.pkey_info); >> if (ret < 0) >> return 0; >> - dump_options(info.pkey_info); >> + dump_options(&info.pkey_info); >> >> p->key_len = p->blob_len + sizeof(struct caam_pkey_info); >> memcpy(p->key, &info.pkey_info, sizeof(struct caam_pkey_info)); >> > > -- Pengutronix e.K. | | Steuerwalder Str. 21 | http://www.pengutronix.de/ | 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 | Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 | ^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [PATCH] KEYS: fix compilation warnings in the dump_options() function 2025-10-24 8:10 ` Ahmad Fatoum @ 2025-10-28 2:39 ` yebin 2025-10-28 7:03 ` Ahmad Fatoum 0 siblings, 1 reply; 7+ messages in thread From: yebin @ 2025-10-28 2:39 UTC (permalink / raw) To: Ahmad Fatoum, kernel, James.Bottomley, jarkko, zohar, dhowells, paul, jmorris, serge, linux-integrity, keyrings, linux-security-module, yebin10 On 2025/10/24 16:10, Ahmad Fatoum wrote: > Hello, > > On 10/24/25 9:02 AM, yebin wrote: >> Ignore this patch as 275a9a3f9b6a(“KEYS: trusted: Pass argument by >> pointer in dump_options”)already fix this issue. > > What tree are you looking at? I can't find this commit in my git and the > code you are purportedly patching never existed upstream. > > If you run into issues exclusive to a vendor fork, you need to submit > your patches to the vendor. The upstream mailing lists are for upstream. > This patch was submitted by Herbert Xu and is on linux-next. https://git.kernel.org/pub/scm/linux/kernel/git/herbert/cryptodev-2.6.git commit 275a9a3f9b6a2158bfb7826074b72d5bdfb2ac35 Author: Herbert Xu <herbert@gondor.apana.org.au> Date: Tue Oct 21 12:07:56 2025 +0800 KEYS: trusted: Pass argument by pointer in dump_options Instead of passing pkey_info into dump_options by value, using a pointer instead. Reported-by: Stephen Rothwell <sfr@canb.auug.org.au> Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au> > Thanks, > Ahmad > >> >> On 2025/10/24 14:11, Ye Bin wrote: >>> From: Ye Bin <yebin10@huawei.com> >>> >>> There's issue as follows: >>> security/keys/trusted-keys/trusted_caam.c: In function ‘dump_options’: >>> security/keys/trusted-keys/trusted_caam.c:37:20: note: the ABI of >>> passing struct with a flexible array member has changed in GCC 4.4 >>> 37 | static inline void dump_options(struct caam_pkey_info pkey_info) >>> | ^~~~~~~~~~~~ >>> >>> To solve the above problem, pass 'struct caam_pkey_info*' type parameter >>> to the dump_options() function. >>> >>> Fixes: 9eb25ca6c973 ("KEYS: trusted: caam based protected key") >>> Signed-off-by: Ye Bin <yebin10@huawei.com> >>> --- >>> security/keys/trusted-keys/trusted_caam.c | 10 +++++----- >>> 1 file changed, 5 insertions(+), 5 deletions(-) >>> >>> diff --git a/security/keys/trusted-keys/trusted_caam.c b/security/ >>> keys/trusted-keys/trusted_caam.c >>> index 090099d1b04d..dd7a69bcf6a3 100644 >>> --- a/security/keys/trusted-keys/trusted_caam.c >>> +++ b/security/keys/trusted-keys/trusted_caam.c >>> @@ -29,12 +29,12 @@ static const match_table_t key_tokens = { >>> }; >>> >>> #ifdef CAAM_DEBUG >>> -static inline void dump_options(struct caam_pkey_info pkey_info) >>> +static inline void dump_options(struct caam_pkey_info *pkey_info) >>> { >>> - pr_info("key encryption algo %d\n", pkey_info.key_enc_algo); >>> + pr_info("key encryption algo %d\n", pkey_info->key_enc_algo); >>> } >>> #else >>> -static inline void dump_options(struct caam_pkey_info pkey_info) >>> +static inline void dump_options(struct caam_pkey_info *pkey_info) >>> { >>> } >>> #endif >>> @@ -108,7 +108,7 @@ static int trusted_caam_seal(struct >>> trusted_key_payload *p, char *datablob) >>> ret = get_pkey_options(datablob, &info.pkey_info); >>> if (ret < 0) >>> return 0; >>> - dump_options(info.pkey_info); >>> + dump_options(&info.pkey_info); >>> } >>> >>> ret = caam_encap_blob(blobifier, &info); >>> @@ -140,7 +140,7 @@ static int trusted_caam_unseal(struct >>> trusted_key_payload *p, char *datablob) >>> ret = get_pkey_options(datablob, &info.pkey_info); >>> if (ret < 0) >>> return 0; >>> - dump_options(info.pkey_info); >>> + dump_options(&info.pkey_info); >>> >>> p->key_len = p->blob_len + sizeof(struct caam_pkey_info); >>> memcpy(p->key, &info.pkey_info, sizeof(struct caam_pkey_info)); >>> >> >> > ^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [PATCH] KEYS: fix compilation warnings in the dump_options() function 2025-10-28 2:39 ` yebin @ 2025-10-28 7:03 ` Ahmad Fatoum 0 siblings, 0 replies; 7+ messages in thread From: Ahmad Fatoum @ 2025-10-28 7:03 UTC (permalink / raw) To: yebin, kernel, James.Bottomley, jarkko, zohar, dhowells, paul, jmorris, serge, linux-integrity, keyrings, linux-security-module, yebin10, Horia Geantă, Pankaj Gupta, Gaurav Jain, linux-crypto, Herbert Xu, Meenakshi Aggarwal Hi, On 10/28/25 3:39 AM, yebin wrote: > > > On 2025/10/24 16:10, Ahmad Fatoum wrote: >> Hello, >> >> On 10/24/25 9:02 AM, yebin wrote: >>> Ignore this patch as 275a9a3f9b6a(“KEYS: trusted: Pass argument by >>> pointer in dump_options”)already fix this issue. >> >> What tree are you looking at? I can't find this commit in my git and the >> code you are purportedly patching never existed upstream. >> >> If you run into issues exclusive to a vendor fork, you need to submit >> your patches to the vendor. The upstream mailing lists are for upstream. >> > This patch was submitted by Herbert Xu and is on linux-next. > > https://git.kernel.org/pub/scm/linux/kernel/git/herbert/cryptodev-2.6.git > commit 275a9a3f9b6a2158bfb7826074b72d5bdfb2ac35 > Author: Herbert Xu <herbert@gondor.apana.org.au> > Date: Tue Oct 21 12:07:56 2025 +0800 > > KEYS: trusted: Pass argument by pointer in dump_options > > Instead of passing pkey_info into dump_options by value, using a > pointer instead. > > Reported-by: Stephen Rothwell <sfr@canb.auug.org.au> > Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au> Thanks for the clarification. The maintainers for trusted keys were unfortunately not Cc'd on that submission, so it flew at least under my radar. :/ Cheers, Ahmad > > >> Thanks, >> Ahmad >> >>> >>> On 2025/10/24 14:11, Ye Bin wrote: >>>> From: Ye Bin <yebin10@huawei.com> >>>> >>>> There's issue as follows: >>>> security/keys/trusted-keys/trusted_caam.c: In function ‘dump_options’: >>>> security/keys/trusted-keys/trusted_caam.c:37:20: note: the ABI of >>>> passing struct with a flexible array member has changed in GCC 4.4 >>>> 37 | static inline void dump_options(struct caam_pkey_info >>>> pkey_info) >>>> | ^~~~~~~~~~~~ >>>> >>>> To solve the above problem, pass 'struct caam_pkey_info*' type >>>> parameter >>>> to the dump_options() function. >>>> >>>> Fixes: 9eb25ca6c973 ("KEYS: trusted: caam based protected key") >>>> Signed-off-by: Ye Bin <yebin10@huawei.com> >>>> --- >>>> security/keys/trusted-keys/trusted_caam.c | 10 +++++----- >>>> 1 file changed, 5 insertions(+), 5 deletions(-) >>>> >>>> diff --git a/security/keys/trusted-keys/trusted_caam.c b/security/ >>>> keys/trusted-keys/trusted_caam.c >>>> index 090099d1b04d..dd7a69bcf6a3 100644 >>>> --- a/security/keys/trusted-keys/trusted_caam.c >>>> +++ b/security/keys/trusted-keys/trusted_caam.c >>>> @@ -29,12 +29,12 @@ static const match_table_t key_tokens = { >>>> }; >>>> >>>> #ifdef CAAM_DEBUG >>>> -static inline void dump_options(struct caam_pkey_info pkey_info) >>>> +static inline void dump_options(struct caam_pkey_info *pkey_info) >>>> { >>>> - pr_info("key encryption algo %d\n", pkey_info.key_enc_algo); >>>> + pr_info("key encryption algo %d\n", pkey_info->key_enc_algo); >>>> } >>>> #else >>>> -static inline void dump_options(struct caam_pkey_info pkey_info) >>>> +static inline void dump_options(struct caam_pkey_info *pkey_info) >>>> { >>>> } >>>> #endif >>>> @@ -108,7 +108,7 @@ static int trusted_caam_seal(struct >>>> trusted_key_payload *p, char *datablob) >>>> ret = get_pkey_options(datablob, &info.pkey_info); >>>> if (ret < 0) >>>> return 0; >>>> - dump_options(info.pkey_info); >>>> + dump_options(&info.pkey_info); >>>> } >>>> >>>> ret = caam_encap_blob(blobifier, &info); >>>> @@ -140,7 +140,7 @@ static int trusted_caam_unseal(struct >>>> trusted_key_payload *p, char *datablob) >>>> ret = get_pkey_options(datablob, &info.pkey_info); >>>> if (ret < 0) >>>> return 0; >>>> - dump_options(info.pkey_info); >>>> + dump_options(&info.pkey_info); >>>> >>>> p->key_len = p->blob_len + sizeof(struct caam_pkey_info); >>>> memcpy(p->key, &info.pkey_info, sizeof(struct >>>> caam_pkey_info)); >>>> >>> >>> >> > > -- Pengutronix e.K. | | Steuerwalder Str. 21 | http://www.pengutronix.de/ | 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 | Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 | ^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [PATCH] KEYS: fix compilation warnings in the dump_options() function 2025-10-24 6:11 [PATCH] KEYS: fix compilation warnings in the dump_options() function Ye Bin 2025-10-24 7:02 ` yebin @ 2025-10-27 20:04 ` Jarkko Sakkinen 2025-10-28 2:41 ` yebin 1 sibling, 1 reply; 7+ messages in thread From: Jarkko Sakkinen @ 2025-10-27 20:04 UTC (permalink / raw) To: Ye Bin Cc: a.fatoum, kernel, James.Bottomley, zohar, dhowells, paul, jmorris, serge, linux-integrity, keyrings, linux-security-module, yebin10 On Fri, Oct 24, 2025 at 02:11:53PM +0800, Ye Bin wrote: > From: Ye Bin <yebin10@huawei.com> > > There's issue as follows: > security/keys/trusted-keys/trusted_caam.c: In function ‘dump_options’: > security/keys/trusted-keys/trusted_caam.c:37:20: note: the ABI of passing struct with a flexible array member has changed in GCC 4.4 > 37 | static inline void dump_options(struct caam_pkey_info pkey_info) > | ^~~~~~~~~~~~ > > To solve the above problem, pass 'struct caam_pkey_info*' type parameter > to the dump_options() function. > > Fixes: 9eb25ca6c973 ("KEYS: trusted: caam based protected key") > Signed-off-by: Ye Bin <yebin10@huawei.com> > --- > security/keys/trusted-keys/trusted_caam.c | 10 +++++----- > 1 file changed, 5 insertions(+), 5 deletions(-) > > diff --git a/security/keys/trusted-keys/trusted_caam.c b/security/keys/trusted-keys/trusted_caam.c > index 090099d1b04d..dd7a69bcf6a3 100644 > --- a/security/keys/trusted-keys/trusted_caam.c > +++ b/security/keys/trusted-keys/trusted_caam.c > @@ -29,12 +29,12 @@ static const match_table_t key_tokens = { > }; > > #ifdef CAAM_DEBUG > -static inline void dump_options(struct caam_pkey_info pkey_info) > +static inline void dump_options(struct caam_pkey_info *pkey_info) > { > - pr_info("key encryption algo %d\n", pkey_info.key_enc_algo); > + pr_info("key encryption algo %d\n", pkey_info->key_enc_algo); > } > #else > -static inline void dump_options(struct caam_pkey_info pkey_info) > +static inline void dump_options(struct caam_pkey_info *pkey_info) > { > } > #endif Please fix the broken design while at it: 1. Remove the ad-hoc compilation flag (i.e., CAAM_DEBUG). 2. Substitute pr_info calls with pr_debug calls. Then you can turn then on and off either dynamically, or alternatively from the kernel command-line [1]. [1] https://www.kernel.org/doc/html/latest/admin-guide/dynamic-debug-howto.html BR, Jarkko ^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [PATCH] KEYS: fix compilation warnings in the dump_options() function 2025-10-27 20:04 ` Jarkko Sakkinen @ 2025-10-28 2:41 ` yebin 0 siblings, 0 replies; 7+ messages in thread From: yebin @ 2025-10-28 2:41 UTC (permalink / raw) To: Jarkko Sakkinen Cc: a.fatoum, kernel, James.Bottomley, zohar, dhowells, paul, jmorris, serge, linux-integrity, keyrings, linux-security-module, yebin10 On 2025/10/28 4:04, Jarkko Sakkinen wrote: > On Fri, Oct 24, 2025 at 02:11:53PM +0800, Ye Bin wrote: >> From: Ye Bin <yebin10@huawei.com> >> >> There's issue as follows: >> security/keys/trusted-keys/trusted_caam.c: In function ‘dump_options’: >> security/keys/trusted-keys/trusted_caam.c:37:20: note: the ABI of passing struct with a flexible array member has changed in GCC 4.4 >> 37 | static inline void dump_options(struct caam_pkey_info pkey_info) >> | ^~~~~~~~~~~~ >> >> To solve the above problem, pass 'struct caam_pkey_info*' type parameter >> to the dump_options() function. >> >> Fixes: 9eb25ca6c973 ("KEYS: trusted: caam based protected key") >> Signed-off-by: Ye Bin <yebin10@huawei.com> >> --- >> security/keys/trusted-keys/trusted_caam.c | 10 +++++----- >> 1 file changed, 5 insertions(+), 5 deletions(-) >> >> diff --git a/security/keys/trusted-keys/trusted_caam.c b/security/keys/trusted-keys/trusted_caam.c >> index 090099d1b04d..dd7a69bcf6a3 100644 >> --- a/security/keys/trusted-keys/trusted_caam.c >> +++ b/security/keys/trusted-keys/trusted_caam.c >> @@ -29,12 +29,12 @@ static const match_table_t key_tokens = { >> }; >> >> #ifdef CAAM_DEBUG >> -static inline void dump_options(struct caam_pkey_info pkey_info) >> +static inline void dump_options(struct caam_pkey_info *pkey_info) >> { >> - pr_info("key encryption algo %d\n", pkey_info.key_enc_algo); >> + pr_info("key encryption algo %d\n", pkey_info->key_enc_algo); >> } >> #else >> -static inline void dump_options(struct caam_pkey_info pkey_info) >> +static inline void dump_options(struct caam_pkey_info *pkey_info) >> { >> } >> #endif > > Please fix the broken design while at it: > > 1. Remove the ad-hoc compilation flag (i.e., CAAM_DEBUG). > 2. Substitute pr_info calls with pr_debug calls. > Alright, I'll fix the two points you mentioned. > Then you can turn then on and off either dynamically, or alternatively > from the kernel command-line [1]. > > [1] https://www.kernel.org/doc/html/latest/admin-guide/dynamic-debug-howto.html > > BR, Jarkko > ^ permalink raw reply [flat|nested] 7+ messages in thread
end of thread, other threads:[~2025-10-28 7:04 UTC | newest] Thread overview: 7+ messages (download: mbox.gz follow: Atom feed -- links below jump to the message on this page -- 2025-10-24 6:11 [PATCH] KEYS: fix compilation warnings in the dump_options() function Ye Bin 2025-10-24 7:02 ` yebin 2025-10-24 8:10 ` Ahmad Fatoum 2025-10-28 2:39 ` yebin 2025-10-28 7:03 ` Ahmad Fatoum 2025-10-27 20:04 ` Jarkko Sakkinen 2025-10-28 2:41 ` yebin
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).