summaryrefslogtreecommitdiffstats
path: root/fs/fs.c
diff options
context:
space:
mode:
authorSascha Hauer <s.hauer@pengutronix.de>2022-11-07 11:28:00 +0100
committerSascha Hauer <s.hauer@pengutronix.de>2022-11-08 11:05:00 +0100
commitd974b8e8f0ecd67507a40f97d1da59f0e4f9ec9d (patch)
tree2e71ee3473e2e21053857357ead635d145db2c79 /fs/fs.c
parent174253baaf9b7576517930b752f5e727d4b04914 (diff)
downloadbarebox-d974b8e8f0ecd67507a40f97d1da59f0e4f9ec9d.tar.gz
barebox-d974b8e8f0ecd67507a40f97d1da59f0e4f9ec9d.tar.xz
fs: avoid uninitialized var warning
With gcc-12.2.1-clang-15.0.2-glibc-2.36-binutils-2.39-kernel-6.0.5-sanitized we get a warning about path.dentry being used uninitialized: fs/fs.c:1978:43: warning: 'path.dentry' may be used uninitialized -Wmaybe-uninitialized] I can't see how this can really happen. gcc seems to think that this sequence used in lookup_fast() can result in returning 0: if (IS_ERR(dentry)) return PTR_ERR(dentry); This shouldn't happen. Silence the warning by initializing 'path'. Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de> Link: https://lore.barebox.org/20221107102800.3669168-1-s.hauer@pengutronix.de Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
Diffstat (limited to 'fs/fs.c')
-rw-r--r--fs/fs.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/fs/fs.c b/fs/fs.c
index 8f21420494..b5a0912405 100644
--- a/fs/fs.c
+++ b/fs/fs.c
@@ -1956,7 +1956,7 @@ static inline int step_into(struct nameidata *nd, struct path *path,
static int walk_component(struct nameidata *nd, int flags)
{
- struct path path;
+ struct path path = {};
int err;
/*