staging: vhciq_core: replace snprintf with scnprintf
Subsystems (3)
PATCH 1/1 staging: vhciq_core: replace snprintf with scnprintf
When the number of bytes to be printed exceeds the limit snprintf returns the number of bytes that would have been printed (if there was no truncation). This might cause issues, hence use scnprintf which returns the actual number of bytes printed to buffer always
--- .../interface/vchiq_arm/vchiq_core.c | 38 +++++++++---------- 1 file changed, 19 insertions(+), 19 deletions(-)
drivers/staging/vc04_services/interface/vchiq_arm/vchiq_core.c +19 -19
@@ -3322,13 +3322,13 @@ vchiq_dump_shared_state(void *dump_context, struct vchiq_state *state,char buf[80 ];int len; - len =snprintf (buf,sizeof (buf), + len =scnprintf (buf,sizeof (buf)," %s: slots %d-%d tx_pos=%x recycle=%x" , label, shared->slot_first, shared->slot_last, shared->tx_pos, shared->slot_queue_recycle);vchiq_dump (dump_context, buf, len +1 ); - len =snprintf (buf,sizeof (buf), + len =scnprintf (buf,sizeof (buf)," Slots claimed:" );vchiq_dump (dump_context, buf, len +1 );
@@ -3336,7 +3336,7 @@ vchiq_dump_shared_state(void *dump_context, struct vchiq_state *state, struct vchiq_slot_info slot_info *SLOT_INFO_FROM_INDEX(state, i);if (slot_info.use_count != slot_info.release_count) { - len =snprintf (buf,sizeof (buf), + len =scnprintf (buf,sizeof (buf)," %d: %d/%d" , i, slot_info.use_count, slot_info.release_count);vchiq_dump (dump_context, buf, len +1 );
@@ -3344,7 +3344,7 @@ vchiq_dump_shared_state(void *dump_context, struct vchiq_state *state, }for (i =1 ; i < shared->debug[DEBUG_ENTRIES ]; i++) { - len =snprintf (buf,sizeof (buf)," DEBUG: %s = %d(%x)" , + len =scnprintf (buf,sizeof (buf)," DEBUG: %s = %d(%x)" , debug_names[i], shared->debug[i], shared->debug[i]);vchiq_dump (dump_context, buf, len +1 ); }
@@ -3357,11 +3357,11 @@ vchiq_dump_state(void *dump_context, struct vchiq_state *state)int len;int i; - len =snprintf (buf,sizeof (buf),"State %d: %s" , state->id, + len =scnprintf (buf,sizeof (buf),"State %d: %s" , state->id, conn_state_names[state->conn_state]);vchiq_dump (dump_context, buf, len +1 ); - len = snprintf(buf, sizeof(buf), + len = scnprintf(buf, sizeof(buf), " tx_pos=%x(@%pK), rx_pos=%x(@%pK)", state->local->tx_pos, state->tx_data + (state->local_tx_pos & VCHIQ_SLOT_MASK),
@@ -3369,13 +3369,13 @@ vchiq_dump_state(void *dump_context, struct vchiq_state *state) state->rx_data + (state->rx_pos & VCHIQ_SLOT_MASK));vchiq_dump (dump_context, buf, len +1 ); - len =snprintf (buf,sizeof (buf), + len =scnprintf (buf,sizeof (buf)," Version: %d (min %d)" ,VCHIQ_VERSION ,VCHIQ_VERSION_MIN );vchiq_dump (dump_context, buf, len +1 );if (VCHIQ_ENABLE_STATS ) { - len = snprintf(buf, sizeof(buf), + len = scnprintf(buf, sizeof(buf), " Stats: ctrl_tx_count=%d, ctrl_rx_count=%d, " "error_count=%d", state->stats.ctrl_tx_count, state->stats.ctrl_rx_count,
@@ -3383,7 +3383,7 @@ vchiq_dump_state(void *dump_context, struct vchiq_state *state)vchiq_dump (dump_context, buf, len +1 ); } - len = snprintf(buf, sizeof(buf), + len = scnprintf(buf, sizeof(buf), " Slots: %d available (%d data), %d recyclable, %d stalls " "(%d data)", ((state->slot_queue_available * VCHIQ_SLOT_SIZE) -
@@ -3416,7 +3416,7 @@ vchiq_dump_service_state(void *dump_context, struct vchiq_service *service)char buf[80 ];int len; - len =snprintf (buf,sizeof (buf),"Service %u: %s (ref %u)" , + len =scnprintf (buf,sizeof (buf),"Service %u: %s (ref %u)" , service->localport, srvstate_names[service->srvstate], service->ref_count -1 );/*Don't include the lock just taken*/
@@ -3428,17 +3428,17 @@ vchiq_dump_service_state(void *dump_context, struct vchiq_service *service)int tx_pending, rx_pending;if (service->remoteport !=VCHIQ_PORT_FREE ) { -int len2 =snprintf (remoteport,sizeof (remoteport), +int len2 =scnprintf (remoteport,sizeof (remoteport),"%u" , service->remoteport);if (service->public_fourcc !=VCHIQ_FOURCC_INVALID ) -snprintf (remoteport + len2, +scnprintf (remoteport + len2,sizeof (remoteport) - len2," (client %x)" , service->client_id); }else strcpy (remoteport,"n/a" ); - len += snprintf(buf + len, sizeof(buf) - len, + len += scnprintf(buf + len, sizeof(buf) - len, " '%c%c%c%c' remote %s (msg use %d/%d, slot use %d/%d)", VCHIQ_FOURCC_AS_4CHARS(fourcc), remoteport,
@@ -3455,7 +3455,7 @@ vchiq_dump_service_state(void *dump_context, struct vchiq_service *service) rx_pending = service->bulk_rx.local_insert - service->bulk_rx.remote_insert; - len = snprintf(buf, sizeof(buf), + len = scnprintf(buf, sizeof(buf), " Bulk: tx_pending=%d (size %d)," " rx_pending=%d (size %d)", tx_pending,
@@ -3468,7 +3468,7 @@ vchiq_dump_service_state(void *dump_context, struct vchiq_service *service)if (VCHIQ_ENABLE_STATS ) {vchiq_dump (dump_context, buf, len +1 ); - len = snprintf(buf, sizeof(buf), + len = scnprintf(buf, sizeof(buf), " Ctrl: tx_count=%d, tx_bytes=%llu, " "rx_count=%d, rx_bytes=%llu", service->stats.ctrl_tx_count,
@@ -3477,7 +3477,7 @@ vchiq_dump_service_state(void *dump_context, struct vchiq_service *service) service->stats.ctrl_rx_bytes);vchiq_dump (dump_context, buf, len +1 ); - len = snprintf(buf, sizeof(buf), + len = scnprintf(buf, sizeof(buf), " Bulk: tx_count=%d, tx_bytes=%llu, " "rx_count=%d, rx_bytes=%llu", service->stats.bulk_tx_count,
@@ -3486,7 +3486,7 @@ vchiq_dump_service_state(void *dump_context, struct vchiq_service *service) service->stats.bulk_rx_bytes);vchiq_dump (dump_context, buf, len +1 ); - len = snprintf(buf, sizeof(buf), + len = scnprintf(buf, sizeof(buf), " %d quota stalls, %d slot stalls, " "%d bulk stalls, %d aborted, %d errors", service->stats.quota_stalls,
@@ -3562,9 +3562,9 @@ void vchiq_log_dump_mem(const char *label, u32 addr, const void *void_mem,for (offset =0 ; offset <16 ; offset++) {if (offset < num_bytes) - s +=snprintf (s,4 ,"%02x " , mem[offset]); + s +=scnprintf (s,4 ,"%02x " , mem[offset]);else - s +=snprintf (s,4 ," " ); + s +=scnprintf (s,4 ," " ); }for (offset =0 ; offset <16 ; offset++) {
Signature · 1 line
2.17.1
Hi Rohit,
Quoted 6 lines · Rohit Sarkar
When the number of bytes to be printed exceeds the limit snprintf returns the number of bytes that would have been printed (if there was no truncation). This might cause issues, hence use scnprintf which returns the actual number of bytes printed to buffer always
Signed-off-by Rohit Sarkar <[email protected]>
thanks for your patch. Did you test your change on the Raspberry Pi?
Quoted 10 lines · Stefan Wahren
Hi Rohit,
Quoted 6 lines · Rohit Sarkar
When the number of bytes to be printed exceeds the limit snprintf returns the number of bytes that would have been printed (if there was no truncation). This might cause issues, hence use scnprintf which returns the actual number of bytes printed to buffer always
Signed-off-by Rohit Sarkar <[email protected]>thanks for your patch. Did you test your change on the Raspberry Pi?
Hey Stefan,
No I haven't done so as I thought this is a generic change? Will that be necessary?
I am relatively new to kernel development
Thanks,
Rohit
Dan Carpenter
Reviewed-byQuoted 9 lines · Rohit Sarkar
Quoted 8 lines · Stefan Wahren
Hi Rohit,
Quoted 5 lines · Rohit Sarkar
When the number of bytes to be printed exceeds the limit snprintf returns the number of bytes that would have been printed (if there was no truncation). This might cause issues, hence use scnprintf which returns the actual number of bytes printed to buffer always
Quoted 6 lines
Quoted 2 lines
Quoted 1 line
Signed-off-by Rohit Sarkar <[email protected]>thanks for your patch. Did you test your change on the Raspberry Pi?
Hey Stefan,
No I haven't done so as I thought this is a generic change? Will that be necessary?
No. It's not required. The patch is easy to audit and clearly harmless.
The question would be does it actually fix a bug? I looked at it and some of the strings are definitely a bit long. The longest one I saw was:
" Slots: %d available (%d data), %d recyclable, %d stalls (%d data)", 123456789 123456789 123456789 123456789 123456789 123456789 123456789
If you get a lot of stalls, then that looks like it could lead to a read overflow (an information leak). Either way this does make the code a bit easier to audit so it seems like a nice cleanup. Next time though, I really would prefer if you put this sort analysis in your commit message so I can just glance over it. (I'm lazy).
regards,
dan carpenter
Quoted 32 lines · Dan Carpenter
Quoted 9 lines · Rohit Sarkar
Quoted 8 lines · Stefan Wahren
Hi Rohit,
Quoted 5 lines · Rohit Sarkar
When the number of bytes to be printed exceeds the limit snprintf returns the number of bytes that would have been printed (if there was no truncation). This might cause issues, hence use scnprintf which returns the actual number of bytes printed to buffer always
Quoted 6 lines
Quoted 2 lines
Quoted 1 line
Signed-off-by Rohit Sarkar <[email protected]>thanks for your patch. Did you test your change on the Raspberry Pi?
Hey Stefan,
No I haven't done so as I thought this is a generic change? Will that be necessary?No. It's not required. The patch is easy to audit and clearly harmless.
The question would be does it actually fix a bug? I looked at it and some of the strings are definitely a bit long. The longest one I saw was:
" Slots: %d available (%d data), %d recyclable, %d stalls (%d data)", 123456789 123456789 123456789 123456789 123456789 123456789 123456789If you get a lot of stalls, then that looks like it could lead to a read overflow (an information leak). Either way this does make the code a bit easier to audit so it seems like a nice cleanup. Next time though, I really would prefer if you put this sort analysis in your commit message so I can just glance over it. (I'm lazy).
Quoted 4 lines
Reviewed-by Dan Carpenter <[email protected]>regards,
dan carpenter
Hey Dan,
Thanks for reviewing this :)
I will make sure to add some analysis the next time I do a clean up like this.
There are a lot of usages of "snprintf" throughout the staging directory (315 to be exact)
Would it be worthwhile to find ones that may cause an information leak and replace them with "scnprintf"?
Thanks,
Rohit
Quoted 4 lines · Rohit Sarkar
There are a lot of usages of "snprintf" throughout the staging directory (315 to be exact)
Would it be worthwhile to find ones that may cause an information leak and replace them with "scnprintf"?
A lot of times it's really easy to see that the uses are safe, so snprintf() is fine in that case. If it's not obviously safe then change it.
regards,
dan carpenter
Quoted 6 lines · Dan Carpenter
Quoted 4 lines · Rohit Sarkar
There are a lot of usages of "snprintf" throughout the staging directory (315 to be exact)
Would it be worthwhile to find ones that may cause an information leak and replace them with "scnprintf"?
Quoted 7 lines
A lot of times it's really easy to see that the uses are safe, so
snprintf()is fine in that case. If it's not obviously safe then change it.regards,
dan carpenter
Sure, thanks a ton!
regards,
Rohit