From: David Sterba <dsterba@suse.cz>
To: Qu Wenruo <quwenruo.btrfs@gmx.com>
Cc: kernel test robot <lkp@intel.com>, Qu Wenruo <wqu@suse.com>,
linux-btrfs@vger.kernel.org, llvm@lists.linux.dev,
oe-kbuild-all@lists.linux.dev
Subject: Re: [PATCH] btrfs: enhance ordered extent double freeing detection
Date: Wed, 11 Dec 2024 22:26:14 +0100 [thread overview]
Message-ID: <20241211212614.GV31418@twin.jikos.cz> (raw)
In-Reply-To: <2e8ec0ba-aaa8-4107-9fbe-b3288a45f5a6@gmx.com>
On Thu, Dec 12, 2024 at 06:17:37AM +1030, Qu Wenruo wrote:
> >>> fs/btrfs/ordered-data.c:200:10: error: no member named 'finished_bitmap' in 'struct btrfs_ordered_extent'
> > 200 | entry->finished_bitmap = bitmap_zalloc(
> > | ~~~~~ ^
>
> I don't know why but it looks like IS_ENABLED() is not exactly doing the
> #ifdef #endif, thus those checks are not fully skipped in this case.
It's never been equvalent to ifdef/endif, it evaluates to 0 or 1 if the
config option is enabled or not but otherwise the source code is still
compiled. The compiler then finds out it's dead code and eliminates it.
prev parent reply other threads:[~2024-12-11 21:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <53b793f2e7a7788f89cda97de565cfc1577cbf75.1733890357.git.wqu@suse.com>
2024-12-11 18:11 ` [PATCH] btrfs: enhance ordered extent double freeing detection kernel test robot
2024-12-11 19:47 ` Qu Wenruo
2024-12-11 21:26 ` David Sterba [this message]
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=20241211212614.GV31418@twin.jikos.cz \
--to=dsterba@suse.cz \
--cc=linux-btrfs@vger.kernel.org \
--cc=lkp@intel.com \
--cc=llvm@lists.linux.dev \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=quwenruo.btrfs@gmx.com \
--cc=wqu@suse.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox