All of lore.kernel.org
 help / color / mirror / Atom feed
From: andy.shevchenko@gmail.com
To: Jan Kara <jack@suse.cz>
Cc: Andy Shevchenko <andriy.shevchenko@intel.com>,
	Baokun Li <libaokun1@huawei.com>,
	Josh Poimboeuf <jpoimboe@kernel.org>, Jan Kara <jack@suse.cz>,
	Nathan Chancellor <nathan@kernel.org>,
	Nick Desaulniers <ndesaulniers@google.com>,
	Kees Cook <keescook@chromium.org>,
	Ferry Toth <ftoth@exalondelft.nl>,
	linux-fsdevel@vger.kernel.org, linux-ext4@vger.kernel.org
Subject: Re: [GIT PULL] ext2, quota, and udf fixes for 6.6-rc1
Date: Fri, 20 Oct 2023 23:36:36 +0300	[thread overview]
Message-ID: <ZTLk1G0KCF7YNjRx@surfacebook.localdomain> (raw)
In-Reply-To: <CAHk-=wgHFSTuANT3jXsw1EtzdHQe-XQtWQACzeFxn2BEBzX-gA@mail.gmail.com>

Fri, Oct 20, 2023 at 12:43:56PM -0700, Linus Torvalds kirjoitti:
> On Fri, 20 Oct 2023 at 11:29, Andy Shevchenko
> <andriy.shevchenko@intel.com> wrote:
> >
> > I'll reply to this with the attached object file, I assume it won't go to the
> > mailing list, but should be available in your mailbox.
> 
> Honestly, both cases (that function gets inlined twice) look
> *identical* from a quick look, apart from obviously the extra call to
> __quota_error().
> 
> I might be missing something, but this most definitely is not a "gcc
> ends up creating very different code when it doesn't need to
> synchronize around the call" thing.
> 
> So a compiler issue looks very unlikely. No absolute guarantees - I
> didn't do *that* kind of walk-through instruction by instruction - but
> the results actually seem to line up perfectly.
> 
> Even register allocation didn't change, making the compare between #if
> 0 and without rather easy.
> 
> There's one extra spill/reload due to the call in the "non-#if0" case,
> and that actually made me look twice (because it spilled %eax, and
> then reloaded it as %rcx), but it turns that %eax/%ecx had the same
> value at the time of the spill, so even that was not a "real"
> difference.
> 
> So I will claim that no, it's not the compiler. It's some unrelated
> subtle timing, or possibly just a random code layout issue (because
> the code addresses do obviously change).

Okay, but since now I can't use the certain configuration, the bug is
persistent to me after this merge with the GCC. Yet, you mentioned that
you would expect some reports but I don't think many people have a
configuration similar to what I have. In any case a bug is lurking somewhere
there.

Let me check next week on different CPU (but I'm quite sceptical that it
may anyhow trigger the same behaviour as if it's a timing, many parameters
are involved, including hardware clocks, etc).

That said, if you or anyone has ideas how to debug futher, I'm all ears!

-- 
With Best Regards,
Andy Shevchenko



  reply	other threads:[~2023-10-20 20:36 UTC|newest]

Thread overview: 53+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-30 10:24 [GIT PULL] ext2, quota, and udf fixes for 6.6-rc1 Jan Kara
2023-08-30 19:50 ` pr-tracker-bot
2023-10-17 10:27 ` Andy Shevchenko
2023-10-17 10:29   ` Andy Shevchenko
2023-10-17 10:32     ` Andy Shevchenko
2023-10-17 11:36       ` Jan Kara
2023-10-17 11:49         ` Andy Shevchenko
2023-10-17 11:46       ` Andy Shevchenko
2023-10-17 13:32         ` Jan Kara
2023-10-17 13:42           ` Andy Shevchenko
2023-10-17 14:50             ` Andy Shevchenko
2023-10-17 15:14               ` Andy Shevchenko
2023-10-17 15:34                 ` Andy Shevchenko
2023-10-17 16:02                   ` Andy Shevchenko
2023-10-18 18:46                     ` Jan Kara
2023-10-19  8:46                       ` Andy Shevchenko
2023-10-19 10:18                         ` Jan Kara
2023-10-19 12:01                           ` Andy Shevchenko
2023-10-19 14:12                             ` Andy Shevchenko
2023-10-19 14:49                               ` Andy Shevchenko
2023-10-19 14:44                             ` Andy Shevchenko
2023-10-19 16:42                               ` Josh Poimboeuf
2023-10-19 17:05                                 ` Andy Shevchenko
2023-10-19 17:26                                   ` Linus Torvalds
2023-10-19 17:51                                     ` Linus Torvalds
2023-10-19 18:10                                       ` Andy Shevchenko
2023-10-19 18:16                                         ` Andy Shevchenko
2023-10-19 18:43                                           ` Linus Torvalds
2023-10-20 14:51                                             ` Andy Shevchenko
2023-10-20 15:06                                               ` Andy Shevchenko
2023-10-20 15:12                                                 ` Andy Shevchenko
2023-10-20 17:26                                                   ` Linus Torvalds
2023-10-20 18:09                                                     ` Jan Kara
2023-10-21  1:48                                                 ` Baokun Li
2023-10-23 12:19                                                   ` Andy Shevchenko
2023-10-23 13:40                                                     ` Baokun Li
2023-10-20 17:23                                               ` Linus Torvalds
2023-10-20 18:29                                                 ` Andy Shevchenko
2023-10-20 18:31                                                   ` Andy Shevchenko
2023-10-20 19:43                                                   ` Linus Torvalds
2023-10-20 20:36                                                     ` andy.shevchenko [this message]
2023-10-21 23:36                                                       ` Kees Cook
2023-10-23 11:45                                                         ` Andy Shevchenko
2023-10-23 12:15                                                           ` Jan Kara
2023-10-23 16:08                                                             ` Kees Cook
2023-10-20 18:05                                               ` Jan Kara
2023-10-20 20:29                                                 ` andy.shevchenko
2023-10-20 11:07                                       ` Jan Kara
2025-01-28 13:24         ` Andy Shevchenko
2023-10-22 13:46   ` Linux regression tracking #adding (Thorsten Leemhuis)
2023-11-22  8:15     ` Linux regression tracking #update (Thorsten Leemhuis)
2023-11-24 16:47       ` Andy Shevchenko
2025-01-28 13:26         ` Andy Shevchenko

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=ZTLk1G0KCF7YNjRx@surfacebook.localdomain \
    --to=andy.shevchenko@gmail.com \
    --cc=andriy.shevchenko@intel.com \
    --cc=ftoth@exalondelft.nl \
    --cc=jack@suse.cz \
    --cc=jpoimboe@kernel.org \
    --cc=keescook@chromium.org \
    --cc=libaokun1@huawei.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=nathan@kernel.org \
    --cc=ndesaulniers@google.com \
    /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.