From: Abdul Haleem <abdhalee@linux.vnet.ibm.com>
To: Jens Axboe <axboe@kernel.dk>
Cc: Brian Foster <bfoster@redhat.com>,
linux-xfs@vger.kernel.org, linux-block@vger.kernel.org,
mpe@ellerman.id, linuxppc-dev <linuxppc-dev@lists.ozlabs.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: 4.11.0-rc1 boot resulted in WARNING: CPU: 14 PID: 1722 at fs/sysfs/dir.c:31 .sysfs_warn_dup+0x78/0xb0
Date: Mon, 13 Mar 2017 23:00:27 +0530 [thread overview]
Message-ID: <1489426227.19698.36.camel@abdul> (raw)
In-Reply-To: <158127ce-d71d-56a5-3dd3-f676b106c65d@kernel.dk>
On Sat, 2017-03-11 at 15:46 -0700, Jens Axboe wrote:
> On 03/09/2017 05:59 AM, Brian Foster wrote:
> > cc linux-block
> >
> > On Thu, Mar 09, 2017 at 04:20:06PM +0530, Abdul Haleem wrote:
> >> On Wed, 2017-03-08 at 08:17 -0500, Brian Foster wrote:
> >>> On Tue, Mar 07, 2017 at 10:01:04PM +0530, Abdul Haleem wrote:
> >>>>
> >>>> Hi,
> >>>>
> >>>> Today's mainline (4.11.0-rc1) booted with warnings on Power7 LPAR.
> >>>>
> >>>> Issue is not reproducible all the time.
>
> Is that still the case with -git as of yesterday? Check that you
> have this merge:
>
> 34bbce9e344b47e8871273409632f525973afad4
>
> in your tree.
>
Thanks for pointing out, with the below merge commit warnings disappear.
commit 34bbce9e344b47e8871273409632f525973afad4
Merge: bb61ce5 672a2c8
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date: Thu Mar 9 15:53:25 2017 -0800
Merge branch 'for-linus' of git://git.kernel.dk/linux-block
Thanks for the fix !
Reported-by & Tested-by : Abdul Haleem <abdhalee@linux.vnet.ibm.com>
--
Regard's
Abdul Haleem
IBM Linux Technology Centre
prev parent reply other threads:[~2017-03-13 17:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-07 16:31 4.11.0-rc1 boot resulted in WARNING: CPU: 14 PID: 1722 at fs/sysfs/dir.c:31 .sysfs_warn_dup+0x78/0xb0 Abdul Haleem
2017-03-08 13:17 ` Brian Foster
2017-03-09 10:50 ` Abdul Haleem
2017-03-09 12:59 ` Brian Foster
2017-03-11 22:46 ` Jens Axboe
2017-03-13 17:30 ` Abdul Haleem [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=1489426227.19698.36.camel@abdul \
--to=abdhalee@linux.vnet.ibm.com \
--cc=axboe@kernel.dk \
--cc=bfoster@redhat.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id \
/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).