From: Luis Henriques <luis.henriques@linux.dev>
To: Jan Kara <jack@suse.cz>
Cc: kernel test robot <lkp@intel.com>,
oe-kbuild-all@lists.linux.dev,
Linux Memory Management List <linux-mm@kvack.org>,
Theodore Ts'o <tytso@mit.edu>
Subject: Re: [linux-next:master 5690/11210] fs/ext4/fast_commit.c:362:21-23: WARNING !A || A && B is equivalent to !A || B
Date: Thu, 12 Sep 2024 11:08:41 +0100 [thread overview]
Message-ID: <87y13xb2vq.fsf@linux.dev> (raw)
In-Reply-To: <20240912094646.brhe2exsizgwzlai@quack3> (Jan Kara's message of "Thu, 12 Sep 2024 11:46:46 +0200")
On Thu, Sep 12 2024, Jan Kara wrote:
> On Thu 12-09-24 09:19:18, Luis Henriques wrote:
>> On Thu, Sep 12 2024, kernel test robot wrote:
>>
>> > tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
>> > head: 32ffa5373540a8d1c06619f52d019c6cdc948bb4
>> > commit: ebc4b2c1ac92fc0f8bf3f5a9c285a871d5084a6b [5690/11210] ext4: fix incorrect tid assumption in ext4_fc_mark_ineligible()
>> > config: loongarch-randconfig-r063-20240911 (https://download.01.org/0day-ci/archive/20240912/202409120149.GdjqoVYQ-lkp@intel.com/config)
>> > compiler: loongarch64-linux-gcc (GCC) 14.1.0
>> >
>> > If you fix the issue in a separate patch/commit (i.e. not just a new version of
>> > the same patch/commit), kindly add following tags
>> > | Reported-by: kernel test robot <lkp@intel.com>
>> > | Closes: https://lore.kernel.org/oe-kbuild-all/202409120149.GdjqoVYQ-lkp@intel.com/
>> >
>> > cocci warnings: (new ones prefixed by >>)
>> >>> fs/ext4/fast_commit.c:362:21-23: WARNING !A || A && B is equivalent to !A || B
>> >
>> > vim +362 fs/ext4/fast_commit.c
>> >
>> > 332
>> > 333 /*
>> > 334 * Mark file system as fast commit ineligible, and record latest
>> > 335 * ineligible transaction tid. This means until the recorded
>> > 336 * transaction, commit operation would result in a full jbd2 commit.
>> > 337 */
>> > 338 void ext4_fc_mark_ineligible(struct super_block *sb, int reason, handle_t *handle)
>> > 339 {
>> > 340 struct ext4_sb_info *sbi = EXT4_SB(sb);
>> > 341 tid_t tid;
>> > 342 bool has_transaction = true;
>> > 343 bool is_ineligible;
>> > 344
>> > 345 if (ext4_fc_disabled(sb))
>> > 346 return;
>> > 347
>> > 348 if (handle && !IS_ERR(handle))
>> > 349 tid = handle->h_transaction->t_tid;
>> > 350 else {
>> > 351 read_lock(&sbi->s_journal->j_state_lock);
>> > 352 if (sbi->s_journal->j_running_transaction)
>> > 353 tid = sbi->s_journal->j_running_transaction->t_tid;
>> > 354 else
>> > 355 has_transaction = false;
>> > 356 read_unlock(&sbi->s_journal->j_state_lock);
>> > 357 }
>> > 358 spin_lock(&sbi->s_fc_lock);
>> > 359 is_ineligible = ext4_test_mount_flag(sb, EXT4_MF_FC_INELIGIBLE);
>> > 360 if (has_transaction &&
>> > 361 (!is_ineligible ||
>> > > 362 (is_ineligible && tid_gt(tid, sbi->s_fc_ineligible_tid))))
>> > 363 sbi->s_fc_ineligible_tid = tid;
>>
>> This suggestion is obviously correct. However, my brain found it much
>> easier to write (and understand) this logic if written this way.
>>
>> Ted, want me to re-send this patch (or a fix for it), or are you happy
>> leaving it as is?
>
> I think I've already seen a patch for this. Yes [1]. Frankly I don't care
> much but I slightly prefer the shorter variant.
Oh! I totally missed that patch on the mailing-list. OK, so no action for
me then. Thanks!
> [1] https://lore.kernel.org/all/20240912090722.4e7o4l462y6hccau@quack3
(Minor nit: looks like this patch has a 'Closes:' tag pointing to a
bugzilla link which isn't accessible at the moment. But maybe it's just a
temporary '502'.)
Cheers,
--
Luís
prev parent reply other threads:[~2024-09-12 10:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-11 17:14 [linux-next:master 5690/11210] fs/ext4/fast_commit.c:362:21-23: WARNING !A || A && B is equivalent to !A || B kernel test robot
2024-09-12 8:19 ` Luis Henriques
2024-09-12 9:46 ` Jan Kara
2024-09-12 10:08 ` Luis Henriques [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=87y13xb2vq.fsf@linux.dev \
--to=luis.henriques@linux.dev \
--cc=jack@suse.cz \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=tytso@mit.edu \
/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;
as well as URLs for NNTP newsgroup(s).