linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Mark Tinguely <mark.tinguely@oracle.com>
To: Andrew Morton <akpm@linux-foundation.org>,
	Nathan Chancellor <nathan@kernel.org>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
	kernel test robot <lkp@intel.com>,
	Linux Memory Management List <linux-mm@kvack.org>,
	"Matthew Wilcox (Oracle)" <willy@infradead.org>,
	Joseph Qi <joseph.qi@linux.alibaba.com>
Subject: Re: [External] : Re: [akpm-mm:mm-nonmm-unstable 66/67] fs/ocfs2/aops.c:1133:17: warning: variable 'i' is uninitialized when used here
Date: Wed, 23 Apr 2025 09:13:50 -0500	[thread overview]
Message-ID: <6923843e-081f-427c-88db-90ee098ca8c3@oracle.com> (raw)
In-Reply-To: <20250422175508.cbb4875faacbda05e6c68cfd@linux-foundation.org>

On 4/22/25 7:55 PM, Andrew Morton wrote:
> On Tue, 22 Apr 2025 13:12:41 -0700 Nathan Chancellor <nathan@kernel.org> wrote:
> 
>> Hi Andrew,
>>
>> On Sat, Apr 19, 2025 at 09:21:13AM +0800, kernel test robot wrote:
>>> tree:   https://urldefense.com/v3/__https://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm.git__;!!ACWV5N9M2RV99hQ!NYsFjZmx0oSNmGPOQ57M8FqiwN9x_0uNHOsZ0H_bxMZw11U8F1-i2FIS7wctmB4sSockZwPpufGxuROeTnhBAaPs$  mm-nonmm-unstable
>>> head:   d1a9b961293d30be9a865d8685590635db282957
>>> commit: 89e3e963129e945e0333e474709bde627b6a9cee [66/67] ocfs2: fix panic in failed foilio allocation
>>> config: s390-randconfig-001-20250419 (https://urldefense.com/v3/__https://download.01.org/0day-ci/archive/20250419/202504190950.rq1NDlDz-lkp@intel.com/config__;!!ACWV5N9M2RV99hQ!NYsFjZmx0oSNmGPOQ57M8FqiwN9x_0uNHOsZ0H_bxMZw11U8F1-i2FIS7wctmB4sSockZwPpufGxuROeTvSadMWN$ )
>>> compiler: clang version 21.0.0git (https://urldefense.com/v3/__https://github.com/llvm/llvm-project__;!!ACWV5N9M2RV99hQ!NYsFjZmx0oSNmGPOQ57M8FqiwN9x_0uNHOsZ0H_bxMZw11U8F1-i2FIS7wctmB4sSockZwPpufGxuROeTvn1221-$  f819f46284f2a79790038e1f6649172789734ae8)
>>> reproduce (this is a W=1 build): (https://urldefense.com/v3/__https://download.01.org/0day-ci/archive/20250419/202504190950.rq1NDlDz-lkp@intel.com/reproduce__;!!ACWV5N9M2RV99hQ!NYsFjZmx0oSNmGPOQ57M8FqiwN9x_0uNHOsZ0H_bxMZw11U8F1-i2FIS7wctmB4sSockZwPpufGxuROeTuWmwFGg$ )
>>>
>>> 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://urldefense.com/v3/__https://lore.kernel.org/oe-kbuild-all/202504190950.rq1NDlDz-lkp@intel.com/__;!!ACWV5N9M2RV99hQ!NYsFjZmx0oSNmGPOQ57M8FqiwN9x_0uNHOsZ0H_bxMZw11U8F1-i2FIS7wctmB4sSockZwPpufGxuROeTgKlYSkL$
>>>
>>> All warnings (new ones prefixed by >>):
>>>
>>>>> fs/ocfs2/aops.c:1133:17: warning: variable 'i' is uninitialized when used here [-Wuninitialized]
>>>      1133 |                         wc->w_folios[i] = NULL;
>>>           |                                      ^
>>>     fs/ocfs2/aops.c:1101:12: note: initialize the variable 'i' to silence this warning
>>>      1101 |         int ret, i;
>>>           |                   ^
>>>           |                    = 0
>>
>> There appears to be something funky going on with "ocfs2: fix panic in
>> failed foilio allocation" in your tree, perhaps as a result of applying
>> v2 to mm-nonmm-unstable and v1 to mm-hotfixes-unstable? If you compare
>> https://urldefense.com/v3/__https://git.kernel.org/akpm/mm/c/392a664f6d2740eeae23df0d29b56f444f558a7c__;!!ACWV5N9M2RV99hQ!NYsFjZmx0oSNmGPOQ57M8FqiwN9x_0uNHOsZ0H_bxMZw11U8F1-i2FIS7wctmB4sSockZwPpufGxuROeTnnwerZK$
>> to https://urldefense.com/v3/__https://lore.kernel.org/c879a52b-835c-4fa0-902b-8b2e9196dcbd@oracle.com/__;!!ACWV5N9M2RV99hQ!NYsFjZmx0oSNmGPOQ57M8FqiwN9x_0uNHOsZ0H_bxMZw11U8F1-i2FIS7wctmB4sSockZwPpufGxuROeTnn7W1rC$ ,
>> the second hunks do not match, which is what this is warning about. I
>> see this same warning in next-20250422.
> 
> Thanks.  Confirms that the universe is a plot to confuse akpm.
> 
> I dropped everything and remerged the v2 patch.
> 

Thank-you for remerging the patch.
I did see the automaic tool complaint and I visually verified the 
indexes and discredited the complaint.

--Mark Tinguely


      reply	other threads:[~2025-04-23 14:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-19  1:21 kernel test robot
2025-04-22 20:12 ` Nathan Chancellor
2025-04-23  0:55   ` Andrew Morton
2025-04-23 14:13     ` Mark Tinguely [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=6923843e-081f-427c-88db-90ee098ca8c3@oracle.com \
    --to=mark.tinguely@oracle.com \
    --cc=akpm@linux-foundation.org \
    --cc=joseph.qi@linux.alibaba.com \
    --cc=linux-mm@kvack.org \
    --cc=lkp@intel.com \
    --cc=llvm@lists.linux.dev \
    --cc=nathan@kernel.org \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=willy@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