All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sasha Levin <sashal@kernel.org>
To: Al Viro <viro@zeniv.linux.org.uk>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [git pull] d_revalidate pile
Date: Mon, 27 Jan 2025 18:26:58 -0500	[thread overview]
Message-ID: <Z5gWQnUDMyE5sniC@lappy> (raw)
In-Reply-To: <20250127224059.GI1977892@ZenIV>

On Mon, Jan 27, 2025 at 10:40:59PM +0000, Al Viro wrote:
>On Mon, Jan 27, 2025 at 09:34:56PM +0000, Al Viro wrote:
>
>> If so, then
>> 	a) it's a false positive (and IIRC, it's not the first time
>> kfence gets confused by that)
>> 	b) your bisection will probably converge to bdd9951f60f9
>> "dissolve external_name.u into separate members" which is where we'd
>> ended up with offsetof(struct external_name, name) being 4 modulo 8.
>>
>> As a quick test, try to flip the order of head and count in
>> struct external_name and see if that makes the warning go away.
>> If it does, I'm pretty certain that theory above is correct.
>
>Not quite...   dentry_string_cmp() assumes that ->d_name.name is
>word-aligned, so load_unaligned_zeropad() is done only to the
>second string (the one we compare against).

Sorry for the silence on my end: this issue doesn't reproduce
consistently, so I need to do more runs for these tests.

-- 
Thanks,
Sasha

  parent reply	other threads:[~2025-01-27 23:27 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-27  4:47 [git pull] d_revalidate pile Al Viro
2025-01-27 17:19 ` Sasha Levin
2025-01-27 17:36   ` Al Viro
2025-01-27 20:52     ` Sasha Levin
2025-01-27 21:34       ` Al Viro
2025-01-27 22:40         ` Al Viro
2025-01-27 23:08           ` Linus Torvalds
2025-01-27 23:26           ` Sasha Levin [this message]
2025-01-28  0:26             ` Al Viro
2025-01-28  0:31               ` Al Viro
2025-01-30  4:37                 ` [git pull] d_revalidate pile (v2) Al Viro
2025-01-30 17:24                   ` Linus Torvalds
2025-01-30 19:31                     ` Miklos Szeredi
2025-01-31  5:56                     ` Al Viro
2025-01-30 17:46                   ` pr-tracker-bot
2025-01-28  0:43               ` [git pull] d_revalidate pile Linus Torvalds
2025-01-28  1:21                 ` Al Viro
2025-01-28  1:27                   ` Linus Torvalds
2025-01-28  2:56                     ` Al Viro
2025-01-27 19:12   ` Linus Torvalds
2025-01-27 20:38     ` Mark Brown
2025-01-27 22:32       ` Sasha Levin
2025-01-28 12:14         ` Mark Brown
2025-01-28 12:43           ` Dan Carpenter
2025-01-28 12:33         ` Dan Carpenter
2025-01-28 19:24           ` Sasha Levin
2025-01-28  9:19       ` Guillaume Tucker

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=Z5gWQnUDMyE5sniC@lappy \
    --to=sashal@kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    --cc=viro@zeniv.linux.org.uk \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.