Assorted fixes discovered with gcc 4.1
Subsystems (7)
cover Assorted fixes discovered with gcc 4.1
Hi all,
Ever since commit cafa0010cd51fb71 ("Raise the minimum required gcc version to 4.6"), I felt bored when looking at my test build logs, as I was no longer discovering many real issues. Hence I started wondering if the modern gcc versions are really catching these classes of bugs caught before with gcc 4.1, or if they just go undetected.
I reverted some changes and applied some fixes, which allowed me to compile most of the kernel with gcc 4.1 again. I built an m68k/allmodconfig kernel, looked at all new warnings, and fixed the ones that are not false positives. The result is a patch series of 5 patches, of which one or two fix real bugs.
Thanks for your comments, and for applying where appropriate!
Geert Uytterhoeven (5):
lightnvm: Fix uninitialized pointer in nvm_remove_tgt()
rxrpc: Fix uninitialized error code in rxrpc_send_data_packet()
net: sched: pie: Use ULL suffix for 64-bit constant
ALSA: fireface: Use ULL suffixes for 64-bit constants [RFC] devlink: Fix uninitialized error code in
devlink_fmsg_prepare_skb()
drivers/lightnvm/core.c | 2 +- net/core/devlink.c | 2 +- net/rxrpc/output.c | 4 +++- net/sched/sch_pie.c | 2 +- sound/firewire/fireface/ff-protocol-latter.c | 10 +++++----- 5 files changed, 11 insertions(+), 9 deletions(-)
Signature · 12 lines
2.17.1
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- [email protected]
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus TorvaldsPATCH 1/5 lightnvm: Fix uninitialized pointer in nvm_remove_tgt()
With gcc 4.1:
drivers/lightnvm/core.c: In function ‘nvm_remove_tgt’:
drivers/lightnvm/core.c:510: warning: ‘t’ is used uninitialized in this function
Indeed, if no NVM devices have been registered, t will be an uninitialized pointer, and may be dereferenced later. A call to nvm_remove_tgt() can be triggered from userspace by issuing the NVM_DEV_REMOVE ioctl on the lightnvm control device.
Fix this by preinitializing t to NULL.
--- drivers/lightnvm/core.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/lightnvm/core.c +1 -1
@@ -492,7 +492,7 @@ static void __nvm_remove_target(struct nvm_target *t, bool graceful)*/ static int nvm_remove_tgt (struct nvm_ioctl_remove *remove) { -struct nvm_target *t; +struct nvm_target *t =NULL ;struct nvm_dev *dev;down_read (&nvm_lock);
Signature · 1 line
2.17.1
Re: [PATCH 1/5] lightnvm: Fix uninitialized pointer in nvm_remove_tgt()
Quoted 24 lines · Geert Uytterhoeven
With gcc 4.1:
drivers/lightnvm/core.c: In function ‘nvm_remove_tgt’:
drivers/lightnvm/core.c:510: warning: ‘t’ is used uninitialized in this functionIndeed, if no NVM devices have been registered, t will be an uninitialized pointer, and may be dereferenced later. A call to
nvm_remove_tgt()can be triggered from userspace by issuing theNVM_DEV_REMOVEioctl on the lightnvm control device.Fix this by preinitializing t to NULL.
Fixes 843f2edbdde085b4 ("lightnvm: do not remove instance under global lock")Signed-off-by Geert Uytterhoeven <[email protected]>--- drivers/lightnvm/core.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)drivers/lightnvm/core.c +0
-0
drivers/lightnvm/core.c static void __nvm_remove_target(struct nvm_target *t, bool graceful) · line 498
Quoted 8 lines
drivers/lightnvm/core.c +1
-1@@ -492,7 +492,7 @@ static void __nvm_remove_target(struct nvm_target *t, bool graceful)*/ static int nvm_remove_tgt (struct nvm_ioctl_remove *remove) { -struct nvm_target *t; +struct nvm_target *t =NULL ;struct nvm_dev *dev;down_read (&nvm_lock);
Thanks Geert. Would you like me to carry the patch?
Re: [PATCH 1/5] lightnvm: Fix uninitialized pointer in nvm_remove_tgt()
Hi Matias,
Quoted 31 lines · Matias Bjørling
Quoted 30 lines · Geert Uytterhoeven
With gcc 4.1:
drivers/lightnvm/core.c: In function ‘nvm_remove_tgt’:
drivers/lightnvm/core.c:510: warning: ‘t’ is used uninitialized in this functionIndeed, if no NVM devices have been registered, t will be an uninitialized pointer, and may be dereferenced later. A call to
nvm_remove_tgt()can be triggered from userspace by issuing theNVM_DEV_REMOVEioctl on the lightnvm control device.Fix this by preinitializing t to NULL.
Fixes 843f2edbdde085b4 ("lightnvm: do not remove instance under global lock")Signed-off-by Geert Uytterhoeven <[email protected]>--- drivers/lightnvm/core.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)drivers/lightnvm/core.c +1
-1@@ -492,7 +492,7 @@ static void __nvm_remove_target(struct nvm_target *t, bool graceful)*/ static int nvm_remove_tgt (struct nvm_ioctl_remove *remove) { -struct nvm_target *t; +struct nvm_target *t =NULL ;struct nvm_dev *dev;
Quoted 4 lines
drivers/lightnvm/core.c static void __nvm_remove_target(struct nvm_target *t, bool graceful) · line 498
Quoted 2 lines
drivers/lightnvm/core.c +0
-0down_read (&nvm_lock);Thanks Geert. Would you like me to carry the patch?
Yes please. Thanks!
Gr{oetje,eeting}s,
Geert
Signature · 5 lines
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- [email protected] In personal conversations with technical people, I call myself a hacker. But when I'm talking to journalists I just say "programmer" or something like that. -- Linus Torvalds
PATCH 2/5 rxrpc: Fix uninitialized error code in rxrpc_send_data_packet()
In reply to Geert UytterhoevenWith gcc 4.1:
net/rxrpc/output.c: In function ‘rxrpc_send_data_packet’:
net/rxrpc/output.c:338: warning: ‘ret’ may be used uninitialized in this function
Indeed, if the first jump to the send_fragmentable label is made, and the address family is not handled in the switch() statement, ret will be used uninitialized.
Fix this by initializing err to zero before the jump, like is already done for the jump to the done label.
---
While this is not a real false-positive, I believe it cannot cause harm in practice, as AF_RXRPC cannot be used with other transport families than IPv4 and IPv6.
--- net/rxrpc/output.c | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-)
net/rxrpc/output.c +3 -1
@@ -403,8 +403,10 @@ int rxrpc_send_data_packet(struct rxrpc_call *call, struct sk_buff *skb,/* send the packet with the don't fragment bit set if we currently * think it's small enough */ -if (iov[1 ].iov_len >= call->peer->maxdata) +if (iov[1 ].iov_len >= call->peer->maxdata) { + ret =0 ; goto send_fragmentable; + }down_read (&conn->params.local->defrag_sem);
Signature · 1 line
2.17.1
David Howells
maintainerRe: [PATCH 2/5] rxrpc: Fix uninitialized error code in rxrpc_send_data_packet()
Quoted 3 lines · Geert Uytterhoeven
While this is not a real false-positive, I believe it cannot cause harm in practice, as
AF_RXRPCcannot be used with other transport families than IPv4 and IPv6.
Agreed.
Quoted 10 lines
--- net/rxrpc/output.c | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-)net/rxrpc/output.c +0
-0@@ -403,8 +403,10 @@ int rxrpc_send_data_packet(struct rxrpc_call *call, struct sk_buff *skb,
net/rxrpc/output.c int rxrpc_send_data_packet(struct rxrpc_call *call, struct sk_buff *skb, · line 412
Quoted 10 lines
net/rxrpc/output.c +3
-1/* send the packet with the don't fragment bit set if we currently * think it's small enough */ -if (iov[1 ].iov_len >= call->peer->maxdata) +if (iov[1 ].iov_len >= call->peer->maxdata) { + ret =0 ; goto send_fragmentable; + }down_read (&conn->params.local->defrag_sem);
Simply setting 0 is wrong. That would give the impression that the thing worked if support for a new transport address family was added and came through this function without full modification (say AF_INET7 becomes a thing).
A better way to do things would be to add a default case into the send_fragmentable switch statement that either BUG's or sets -EAFNOSUPPORT.
David
Re: [PATCH 2/5] rxrpc: Fix uninitialized error code in rxrpc_send_data_packet()
In reply to Geert UytterhoevenQuoted 13 lines · Geert Uytterhoeven
With gcc 4.1:
net/rxrpc/output.c: In function ‘rxrpc_send_data_packet’:
net/rxrpc/output.c:338: warning: ‘ret’ may be used uninitialized in this functionIndeed, if the first jump to the
send_fragmentablelabel is made, and the address family is not handled in theswitch()statement, ret will be used uninitialized.Fix this by initializing err to zero before the jump, like is already done for the jump to the done label.
Quoted 6 lines
Fixes 5a924b8951f835b5 ("rxrpc: Don't store the rxrpc header in the Tx queue sk_buffs")Signed-off-by Geert Uytterhoeven <[email protected]>---
While this is not a real false-positive, I believe it cannot cause harm in practice, asAF_RXRPCcannot be used with other transport families than IPv4 and IPv6.
This looks like a variant of the infamous bug
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=18501
What I don't understand is why clang fails to warn about it with -Wsometimes-uninitialized.
(cc clang-built-linux mailing list).
Arnd
Quoted 19 lines
net/rxrpc/output.c | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-)net/rxrpc/output.c +3
-1@@ -403,8 +403,10 @@ int rxrpc_send_data_packet(struct rxrpc_call *call, struct sk_buff *skb,/* send the packet with the don't fragment bit set if we currently * think it's small enough */ -if (iov[1 ].iov_len >= call->peer->maxdata) +if (iov[1 ].iov_len >= call->peer->maxdata) { + ret =0 ; goto send_fragmentable; + }down_read (&conn->params.local->defrag_sem);
David Howells
maintainerPATCH 1/1 rxrpc: Fix uninitialized error code in rxrpc_send_data_packet()
In reply to Geert UytterhoevenHi Geert,
Here's my take on the patch.
David
---
rxrpc: Fix uninitialized error code in rxrpc_send_data_packet()
With gcc 4.1:
net/rxrpc/output.c: In function ‘rxrpc_send_data_packet’:
net/rxrpc/output.c:338: warning: ‘ret’ may be used uninitialized in this function
Indeed, if the first jump to the send_fragmentable label is made, and the address family is not handled in the switch() statement, ret will be used uninitialized.
Fix this by BUG()'ing as is done in other places in rxrpc where internal support for future address families will need adding. It should not be possible to reach this normally as the address families are checked up-front.
---
net/rxrpc/output.c +3 -0
@@ -523,6 +523,9 @@ int rxrpc_send_data_packet(struct rxrpc_call *call, struct sk_buff *skb, }break ;#endif + +default : +BUG (); }if (ret <0 )
David Miller
maintainerRe: [PATCH] rxrpc: Fix uninitialized error code in rxrpc_send_data_packet()
From: David Howells <[email protected]>
Date: Fri, 31 May 2019 11:34:44 +0100
Quoted 1 line
Here's my take on the patch.
I assume I'll see a final version of this under separate cover.
Re: [PATCH] rxrpc: Fix uninitialized error code in rxrpc_send_data_packet()
In reply to David HowellsHi David,
Quoted 15 lines · David Howells
Here's my take on the patch.
David
---
rxrpc: Fix uninitialized error code inrxrpc_send_data_packet()With gcc 4.1:
net/rxrpc/output.c: In function ‘rxrpc_send_data_packet’:
net/rxrpc/output.c:338: warning: ‘ret’ may be used uninitialized in this functionIndeed, if the first jump to the
send_fragmentablelabel is made, and the address family is not handled in theswitch()statement, ret will be used uninitialized.
Quoted 8 lines
Fix this by BUG()'ing as is done in other places in rxrpc where internal support for future address families will need adding. It should not be possible to reach this normally as the address families are checked up-front.
Fixes 5a924b8951f835b5 ("rxrpc: Don't store the rxrpc header in the Tx queue sk_buffs")Reported-by Geert Uytterhoeven <[email protected]>Signed-off-by David Howells <[email protected]>
I'm not such a big fan of BUG(), so I'd go for ret = -EAFNOSUPPORT, but given rxrpc is already full of BUG() calls, I guess it is an acceptable solution.
Quoted 6 lines
---
net/rxrpc/output.c +0
-0
net/rxrpc/output.c int rxrpc_send_data_packet(struct rxrpc_call *call, struct sk_buff *skb, · line 531
Quoted 9 lines
net/rxrpc/output.c +3
-0@@ -523,6 +523,9 @@ int rxrpc_send_data_packet(struct rxrpc_call *call, struct sk_buff *skb, }break ;#endif + +default : +BUG (); }if (ret <0 )
Gr{oetje,eeting}s,
Geert
Signature · 5 lines
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- [email protected] In personal conversations with technical people, I call myself a hacker. But when I'm talking to journalists I just say "programmer" or something like that. -- Linus Torvalds
David Howells
maintainerRe: [PATCH] rxrpc: Fix uninitialized error code in rxrpc_send_data_packet()
Quoted 2 lines · Geert Uytterhoeven
I'm not such a big fan of
BUG(), so I'd go for ret =-EAFNOSUPPORT, but given rxrpc is already full ofBUG()calls, I guess it is an acceptable solution.
Okay. Are you okay with this going through net-next?
David
Re: [PATCH] rxrpc: Fix uninitialized error code in rxrpc_send_data_packet()
Hi David,
Quoted 6 lines · David Howells
Quoted 2 lines · Geert Uytterhoeven
I'm not such a big fan of
BUG(), so I'd go for ret =-EAFNOSUPPORT, but given rxrpc is already full ofBUG()calls, I guess it is an acceptable solution.Okay. Are you okay with this going through net-next?
Yes, I am.
Gr{oetje,eeting}s,
Geert
Signature · 5 lines
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- [email protected] In personal conversations with technical people, I call myself a hacker. But when I'm talking to journalists I just say "programmer" or something like that. -- Linus Torvalds
PATCH 3/5 net: sched: pie: Use ULL suffix for 64-bit constant
In reply to Geert UytterhoevenWith gcc 4.1, when compiling for a 32-bit platform:
net/sched/sch_pie.c: In function ‘drop_early’:
net/sched/sch_pie.c:116: warning: integer constant is too large for ‘long’ type net/sched/sch_pie.c:138: warning: integer constant is too large for ‘long’ type net/sched/sch_pie.c:144: warning: integer constant is too large for ‘long’ type net/sched/sch_pie.c:147: warning: integer constant is too large for ‘long’ type net/sched/sch_pie.c: In function ‘pie_qdisc_enqueue’:
net/sched/sch_pie.c:173: warning: integer constant is too large for ‘long’ type net/sched/sch_pie.c: In function ‘calculate_probability’:
net/sched/sch_pie.c:371: warning: integer constant is too large for ‘long’ type net/sched/sch_pie.c:372: warning: integer constant is too large for ‘long’ type net/sched/sch_pie.c:377: warning: integer constant is too large for ‘long’ type net/sched/sch_pie.c:382: warning: integer constant is too large for ‘long’ type net/sched/sch_pie.c:397: warning: integer constant is too large for ‘long’ type net/sched/sch_pie.c:398: warning: integer constant is too large for ‘long’ type net/sched/sch_pie.c:399: warning: integer constant is too large for ‘long’ type net/sched/sch_pie.c:407: warning: integer constant is too large for ‘long’ type net/sched/sch_pie.c:414: warning: integer constant is too large for ‘long’ type
Fix this by adding the missing "ULL" suffix.
--- net/sched/sch_pie.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
net/sched/sch_pie.c +1 -1
@@ -31,7 +31,7 @@#define QUEUE_THRESHOLD 16384#define DQCOUNT_INVALID -1 -#define MAX_PROB 0xffffffffffffffff +#define MAX_PROB 0xffffffffffffffffULL#define PIE_SCALE 8/* parameters used */
Signature · 1 line
2.17.1
Re: [PATCH 3/5] net: sched: pie: Use ULL suffix for 64-bit constant
Quoted 21 lines · Geert Uytterhoeven
With gcc 4.1, when compiling for a 32-bit platform:
net/sched/sch_pie.c: In function ‘drop_early’:
net/sched/sch_pie.c:116: warning: integer constant is too large for ‘long’ typenet/sched/sch_pie.c:138: warning: integer constant is too large for ‘long’ typenet/sched/sch_pie.c:144: warning: integer constant is too large for ‘long’ typenet/sched/sch_pie.c:147: warning: integer constant is too large for ‘long’ typenet/sched/sch_pie.c: In function ‘pie_qdisc_enqueue’:
net/sched/sch_pie.c:173: warning: integer constant is too large for ‘long’ typenet/sched/sch_pie.c: In function ‘calculate_probability’:
net/sched/sch_pie.c:371: warning: integer constant is too large for ‘long’ typenet/sched/sch_pie.c:372: warning: integer constant is too large for ‘long’ typenet/sched/sch_pie.c:377: warning: integer constant is too large for ‘long’ typenet/sched/sch_pie.c:382: warning: integer constant is too large for ‘long’ typenet/sched/sch_pie.c:397: warning: integer constant is too large for ‘long’ typenet/sched/sch_pie.c:398: warning: integer constant is too large for ‘long’ typenet/sched/sch_pie.c:399: warning: integer constant is too large for ‘long’ typenet/sched/sch_pie.c:407: warning: integer constant is too large for ‘long’ typenet/sched/sch_pie.c:414: warning: integer constant is too large for ‘long’ type
Quoted 4 lines
Fix this by adding the missing "ULL" suffix.
Fixes 3f7ae5f3dc5295ac ("net: sched: pie: add more cases to auto-tune alpha and beta")Signed-off-by Geert Uytterhoeven <[email protected]>
I created patches for all instances of this issue at some point in the past, but did not send those as we raised the minimum compiler version to one that handles this in the expected way without a warning.
Maybe you can just ignore these as well?
Arnd
PATCH 4/5 ALSA: fireface: Use ULL suffixes for 64-bit constants
In reply to Geert UytterhoevenWith gcc 4.1:
sound/firewire/fireface/ff-protocol-latter.c: In function ‘latter_switch_fetching_mode’:
sound/firewire/fireface/ff-protocol-latter.c:97: warning: integer constant is too large for ‘long’ type sound/firewire/fireface/ff-protocol-latter.c: In function ‘latter_begin_session’:
sound/firewire/fireface/ff-protocol-latter.c:170: warning: integer constant is too large for ‘long’ type sound/firewire/fireface/ff-protocol-latter.c:197: warning: integer constant is too large for ‘long’ type sound/firewire/fireface/ff-protocol-latter.c:205: warning: integer constant is too large for ‘long’ type sound/firewire/fireface/ff-protocol-latter.c: In function ‘latter_finish_session’:
sound/firewire/fireface/ff-protocol-latter.c:214: warning: integer constant is too large for ‘long’ type
Fix this by adding the missing "ULL" suffixes.
Add the same suffix to the last constant, to maintain consistency.
--- sound/firewire/fireface/ff-protocol-latter.c | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-)
sound/firewire/fireface/ff-protocol-latter.c +5 -5
@@ -9,11 +9,11 @@#include "ff.h" -#define LATTER_STF 0xffff00000004 -#define LATTER_ISOC_CHANNELS 0xffff00000008 -#define LATTER_ISOC_START 0xffff0000000c -#define LATTER_FETCH_MODE 0xffff00000010 -#define LATTER_SYNC_STATUS 0x0000801c0000 +#define LATTER_STF 0xffff00000004ULL +#define LATTER_ISOC_CHANNELS 0xffff00000008ULL +#define LATTER_ISOC_START 0xffff0000000cULL +#define LATTER_FETCH_MODE 0xffff00000010ULL +#define LATTER_SYNC_STATUS 0x0000801c0000ULLstatic int parse_clock_bits (u32 data,unsigned int *rate,enum snd_ff_clock_src *src)
Signature · 1 line
2.17.1
Re: [PATCH 4/5] ALSA: fireface: Use ULL suffixes for 64-bit constants
Hi,
Quoted 11 lines · Geert Uytterhoeven
With gcc 4.1:
sound/firewire/fireface/ff-protocol-latter.c: In function ‘latter_switch_fetching_mode’:
sound/firewire/fireface/ff-protocol-latter.c:97: warning: integer constant is too large for ‘long’ typesound/firewire/fireface/ff-protocol-latter.c: In function ‘latter_begin_session’:
sound/firewire/fireface/ff-protocol-latter.c:170: warning: integer constant is too large for ‘long’ typesound/firewire/fireface/ff-protocol-latter.c:197: warning: integer constant is too large for ‘long’ typesound/firewire/fireface/ff-protocol-latter.c:205: warning: integer constant is too large for ‘long’ typesound/firewire/fireface/ff-protocol-latter.c: In function ‘latter_finish_session’:
sound/firewire/fireface/ff-protocol-latter.c:214: warning: integer constant is too large for ‘long’ type
Quoted 8 lines
Fix this by adding the missing "ULL" suffixes.
Add the same suffix to the last constant, to maintain consistency.Fixes fd1cc9de64c2ca6c ("ALSA: fireface: add support for Fireface UCX")Signed-off-by Geert Uytterhoeven <[email protected]>--- sound/firewire/fireface/ff-protocol-latter.c | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-)
Thanks for your care.
Quoted 24 lines
sound/firewire/fireface/ff-protocol-latter.c +5
-5@@ -9,11 +9,11 @@#include "ff.h" -#define LATTER_STF 0xffff00000004 -#define LATTER_ISOC_CHANNELS 0xffff00000008 -#define LATTER_ISOC_START 0xffff0000000c -#define LATTER_FETCH_MODE 0xffff00000010 -#define LATTER_SYNC_STATUS 0x0000801c0000 +#define LATTER_STF 0xffff00000004ULL +#define LATTER_ISOC_CHANNELS 0xffff00000008ULL +#define LATTER_ISOC_START 0xffff0000000cULL +#define LATTER_FETCH_MODE 0xffff00000010ULL +#define LATTER_SYNC_STATUS 0x0000801c0000ULLstatic int parse_clock_bits (u32 data,unsigned int *rate,enum snd_ff_clock_src *src)Signature · 1 line
2.17.1
Regards
Takashi Sakamoto
_______________________________________________
Alsa-devel mailing list
[email protected]
https://mailman.alsa-project.org/mailman/listinfo/alsa-devel
Takashi Iwai
AppliedRe: [PATCH 4/5] ALSA: fireface: Use ULL suffixes for 64-bit constants
Quoted 24 lines · Takashi Sakamoto
Hi,
Quoted 11 lines · Geert Uytterhoeven
With gcc 4.1:
sound/firewire/fireface/ff-protocol-latter.c: In function ‘latter_switch_fetching_mode’:
sound/firewire/fireface/ff-protocol-latter.c:97: warning: integer constant is too large for ‘long’ typesound/firewire/fireface/ff-protocol-latter.c: In function ‘latter_begin_session’:
sound/firewire/fireface/ff-protocol-latter.c:170: warning: integer constant is too large for ‘long’ typesound/firewire/fireface/ff-protocol-latter.c:197: warning: integer constant is too large for ‘long’ typesound/firewire/fireface/ff-protocol-latter.c:205: warning: integer constant is too large for ‘long’ typesound/firewire/fireface/ff-protocol-latter.c: In function ‘latter_finish_session’:
sound/firewire/fireface/ff-protocol-latter.c:214: warning: integer constant is too large for ‘long’ typeQuoted 8 lines
Fix this by adding the missing "ULL" suffixes.
Add the same suffix to the last constant, to maintain consistency.Fixes fd1cc9de64c2ca6c ("ALSA: fireface: add support for Fireface UCX")Signed-off-by Geert Uytterhoeven <[email protected]>--- sound/firewire/fireface/ff-protocol-latter.c | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-)
Quoted 3 lines
Thanks for your care.
Reviewed-by Takashi Sakamoto <[email protected]>
Applied to sound git tree now. Thanks.
Takashi
RFC PATCH 5/5 devlink: Fix uninitialized error code in devlink_fmsg_prepare_skb()
In reply to Geert UytterhoevenWith gcc 4.1:
net/core/devlink.c: In function ‘devlink_fmsg_prepare_skb’:
net/core/devlink.c:4325: warning: ‘err’ may be used uninitialized in this function
Indeed, if the list has less than *start entries, an uninitialized error code will be returned.
Fix this by preinitializing err to zero.
---
I don't know if this can really happen, and if this is the right fix. Perhaps err should be initialized to some valid error code instead?
--- net/core/devlink.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
net/core/devlink.c +1 -1
@@ -4321,8 +4321,8 @@ devlink_fmsg_prepare_skb(struct devlink_fmsg *fmsg, struct sk_buff *skb, {struct devlink_fmsg_item *item;struct nlattr *fmsg_nlattr; +int err =0 ;int i =0 ; -int err; fmsg_nlattr =nla_nest_start_noflag (skb,DEVLINK_ATTR_FMSG );if (!fmsg_nlattr)
Signature · 1 line
2.17.1
Re: [PATCH 5/5] [RFC] devlink: Fix uninitialized error code in devlink_fmsg_prepare_skb()
Quoted 7 lines · Geert Uytterhoeven
With gcc 4.1:
net/core/devlink.c: In function ‘devlink_fmsg_prepare_skb’:
net/core/devlink.c:4325: warning: ‘err’ may be used uninitialized in this functionIndeed, if the list has less than *start entries, an uninitialized error code will be returned.
The logic guarantees that start is smaller than the length of the list. but I guess that the compiler can't detect that.
Quoted 27 lines
Fix this by preinitializing err to zero.
Fixes 1db64e8733f65381 ("devlink: Add devlink formatted message (fmsg) API")Signed-off-by Geert Uytterhoeven <[email protected]>---
I don't know if this can really happen, and if this is the right fix. Perhaps err should be initialized to some valid error code instead?--- net/core/devlink.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)net/core/devlink.c +1
-1@@ -4321,8 +4321,8 @@ devlink_fmsg_prepare_skb(struct devlink_fmsg *fmsg, struct sk_buff *skb, {struct devlink_fmsg_item *item;struct nlattr *fmsg_nlattr; +int err =0 ;int i =0 ; -int err; fmsg_nlattr =nla_nest_start_noflag (skb,DEVLINK_ATTR_FMSG );if (!fmsg_nlattr)
Re: [PATCH 5/5] [RFC] devlink: Fix uninitialized error code in devlink_fmsg_prepare_skb()
In reply to Geert UytterhoevenQuoted 8 lines · Tue, May 28, 2019 at 04:24:24PM CEST, [email protected] wrote:
With gcc 4.1:
net/core/devlink.c: In function ‘devlink_fmsg_prepare_skb’:
net/core/devlink.c:4325: warning: ‘err’ may be used uninitialized in this functionIndeed, if the list has less than *start entries, an uninitialized error code will be returned.
Quoted 7 lines
Fix this by preinitializing err to zero.
Fixes 1db64e8733f65381 ("devlink: Add devlink formatted message (fmsg) API")Signed-off-by Geert Uytterhoeven <[email protected]>---
I don't know if this can really happen, and if this is the right fix. Perhaps err should be initialized to some valid error code instead?
0 is correct here.
Thanks!
Quoted 21 lines
---
net/core/devlink.c| 2 +-1 file changed, 1 insertion(+), 1 deletion(-)net/core/devlink.c +1
-1@@ -4321,8 +4321,8 @@ devlink_fmsg_prepare_skb(struct devlink_fmsg *fmsg, struct sk_buff *skb, {struct devlink_fmsg_item *item;struct nlattr *fmsg_nlattr; +int err =0 ;int i =0 ; -int err; fmsg_nlattr =nla_nest_start_noflag (skb,DEVLINK_ATTR_FMSG );if (!fmsg_nlattr)Signature · 1 line
2.17.1