All of lore.kernel.org
 help / color / mirror / Atom feed
From: Amir Goldstein <amir73il@gmail.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Miklos Szeredi <miklos@szeredi.hu>,
	Linux-Next Mailing List <linux-next@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: build warning after merge of the overlayfs tree
Date: Wed, 17 May 2017 08:00:14 +0300	[thread overview]
Message-ID: <CAOQ4uxi0-WCYq3FHOAHVSRGdhzz_BY-+0+dVcS7ftGVuM=F-vg@mail.gmail.com> (raw)
In-Reply-To: <20170517101956.69c03d78@canb.auug.org.au>

On Wed, May 17, 2017 at 3:19 AM, Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> Hi Miklos,
>
> After merging the overlayfs tree, today's linux-next build (powerpc
> ppc64_defconfig) produced this warning:
>
> fs/overlayfs/dir.c: In function 'ovl_rename':
> fs/overlayfs/dir.c:1060:2: warning: 'newdentry' may be used uninitialized in this function [-Wmaybe-uninitialized]
>   dput(newdentry);
>   ^
> fs/overlayfs/dir.c:1062:2: warning: 'olddentry' may be used uninitialized in this function [-Wmaybe-uninitialized]
>   dput(olddentry);
>   ^
>
> Introduced by commit
>
>   02cac3227a28 ("ovl: mark upper dir with type origin entries "impure"")
>

Posted a fix for that ("ovl: fix wrong error handling of ovl_set_impure()")

Thanks!

  reply	other threads:[~2017-05-17  5:00 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-17  0:19 linux-next: build warning after merge of the overlayfs tree Stephen Rothwell
2017-05-17  5:00 ` Amir Goldstein [this message]
  -- strict thread matches above, loose matches on Subject: below --
2021-07-20  6:38 Stephen Rothwell
2021-07-21 13:39 ` Miklos Szeredi
2021-03-29  9:14 Stephen Rothwell
2021-03-29  9:28 ` Miklos Szeredi
2021-03-31  0:16   ` Stephen Rothwell
2021-04-21  6:26 ` Stephen Rothwell
2017-11-08 22:33 Stephen Rothwell
2017-11-09  3:59 ` Chandan Rajendra
2016-11-22  0:19 Stephen Rothwell
2016-11-22  8:41 ` Miklos Szeredi

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='CAOQ4uxi0-WCYq3FHOAHVSRGdhzz_BY-+0+dVcS7ftGVuM=F-vg@mail.gmail.com' \
    --to=amir73il@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=miklos@szeredi.hu \
    --cc=sfr@canb.auug.org.au \
    /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.