Skip to contentSkip to conversation

gpioinfo: don't crash after EACCESS

PATCH New John Keeping 1 participant 1 message Apr 20, 2022 GPIO

lore
Share & tools
lore
#0 lore raw

PATCH 1/1 gpioinfo: don't crash after EACCESS

If chip_open_by_name() fails then EACCESS is not treated as a fatal error, but falling through calls list_lines(NULL) which leads to a segfault. Move on to the next chip in this instance.

---
 tools/gpioinfo.c | 3 +++
 1 file changed, 3 insertions(+)
tools/gpioinfo.c +3 -0
index d50af45..542a881 100644
@@ -226,6 +226,9 @@ int main(int argc, char **argv)
 				else
 					die_perror("unable to open %s",
 						   entries[i]->d_name);
+
+				free(entries[i]);
+				continue;
 			}
 
 			list_lines(chip);
Signature · 1 line
2.35.3