From: Andrew Morton <akpm@linux-foundation.org>
To: kernel test robot <lkp@intel.com>
Cc: ntfs3@lists.linux.dev, linux-mm@kvack.org,
linux-ext4@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
jfs-discussion@lists.sourceforge.net,
Liam Howlett <liam.howlett@oracle.com>
Subject: Re: [linux-next:master] BUILD REGRESSION 4ca786ae6681b90b0ec3f4c55c89d12f835f8944
Date: Tue, 18 Oct 2022 14:02:36 -0700 [thread overview]
Message-ID: <20221018140236.f55b76d77f5b872edf9bfdce@linux-foundation.org> (raw)
In-Reply-To: <634eca23.ML3KLI/hjp2jt28w%lkp@intel.com>
On Tue, 18 Oct 2022 23:45:39 +0800 kernel test robot <lkp@intel.com> wrote:
> tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
> branch HEAD: 4ca786ae6681b90b0ec3f4c55c89d12f835f8944 Add linux-next specific files for 20221018
>
> ...
>
> mm/mmap.c:802 __vma_adjust() error: uninitialized symbol 'next_next'.
>
The code's OK but I guess we should make this warning go away.
--- a/mm/mmap.c~a
+++ a/mm/mmap.c
@@ -618,7 +618,8 @@ int __vma_adjust(struct vm_area_struct *
struct vm_area_struct *expand)
{
struct mm_struct *mm = vma->vm_mm;
- struct vm_area_struct *next_next, *next = find_vma(mm, vma->vm_end);
+ struct vm_area_struct *next_next = NULL; /* uninit var warning */
+ struct vm_area_struct *next = find_vma(mm, vma->vm_end);
struct vm_area_struct *orig_vma = vma;
struct address_space *mapping = NULL;
struct rb_root_cached *root = NULL;
_
next prev parent reply other threads:[~2022-10-18 21:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-18 15:45 kernel test robot
2022-10-18 21:02 ` Andrew Morton [this message]
2022-10-18 22:04 ` Liam Howlett
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=20221018140236.f55b76d77f5b872edf9bfdce@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=jfs-discussion@lists.sourceforge.net \
--cc=liam.howlett@oracle.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=ntfs3@lists.linux.dev \
/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