mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Ahmad Fatoum <a.fatoum@pengutronix.de>
To: barebox@lists.infradead.org
Cc: Ahmad Fatoum <a.fatoum@pengutronix.de>
Subject: [PATCH master 2/2] fs: fix resolving paths when directory name repeats
Date: Wed,  8 Jan 2025 10:14:25 +0100	[thread overview]
Message-ID: <20250108091425.911629-2-a.fatoum@pengutronix.de> (raw)
In-Reply-To: <20250108091425.911629-1-a.fatoum@pengutronix.de>

d_same_name() used to only check if the name exists in any of the
directory's children.

In order to fix lookup of /, the function was changed to also compare
the name against the parent. This is obviously wrong, when the parent
and child have the same name: Resolution of the child would always
return the parent dentry triggering unexpected behavior.

Fix this by effectively reverting the functional change in commit
3a478ff3e1e6 ("fs: support opening /"). This breaks opening /, but that
currently only affects dirfd usage and will be fixed separately.

Fixes: 3a478ff3e1e6 ("fs: support opening /")
Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de>
---
 fs/fs.c           | 3 ---
 test/self/dirfd.c | 7 ++++++-
 2 files changed, 6 insertions(+), 4 deletions(-)

diff --git a/fs/fs.c b/fs/fs.c
index 57bd781025f9..235fb8f8e9ef 100644
--- a/fs/fs.c
+++ b/fs/fs.c
@@ -1536,9 +1536,6 @@ static struct dentry *d_lookup(struct dentry *parent, const struct qstr *name)
 {
 	struct dentry *dentry;
 
-	if (d_same_name(parent, name))
-		return dget(parent);
-
 	list_for_each_entry(dentry, &parent->d_subdirs, d_child) {
 		if (d_same_name(dentry, name))
 			return dget(dentry);
diff --git a/test/self/dirfd.c b/test/self/dirfd.c
index 20b54258715a..644ff214fb37 100644
--- a/test/self/dirfd.c
+++ b/test/self/dirfd.c
@@ -100,8 +100,13 @@ static void test_dirfd(void)
 	int fd;
 
 	fd = open("/", O_PATH);
-	if (expect(fd < 0, false, "open(/, O_PATH) = %d", fd))
+	if (expect(fd < 0, false, "open(/, O_PATH) = %d", fd)) {
 		close(fd);
+	} else {
+		pr_info("\tIgnoring expected failure\n");
+		failed_tests--;
+		skipped_tests++;
+	}
 
 #define B(dot, dotdot, zero, dev) 0b##dev##zero##dotdot##dot
 	/* We do fiften tests for every configuration
-- 
2.39.5




  reply	other threads:[~2025-01-08  9:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-08  9:14 [PATCH master 1/2] test: self: ramfs: add regression test for recursive opendir Ahmad Fatoum
2025-01-08  9:14 ` Ahmad Fatoum [this message]
2025-01-08 14:17 ` Sascha Hauer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20250108091425.911629-2-a.fatoum@pengutronix.de \
    --to=a.fatoum@pengutronix.de \
    --cc=barebox@lists.infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox