From: Joe Lawrence <joe.lawrence@redhat.com>
To: Sudip Mukherjee <sudipm.mukherjee@gmail.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
gregkh@linuxfoundation.org
Subject: Re: [ppdev] sysfs warning on qemu boot
Date: Fri, 11 Nov 2016 17:16:08 -0500 [thread overview]
Message-ID: <80647f01-bf8e-56c6-4933-c161bbce3fc6@redhat.com> (raw)
In-Reply-To: <5826349F.80408@gmail.com>
On 11/11/2016 04:14 PM, Sudip Mukherjee wrote:
> Hi Joe,
>
> On Wednesday 09 November 2016 06:41 PM, Joe Lawrence wrote:
>> On 11/09/2016 12:04 PM, Sudip Mukherjee wrote:
>>> Hi Joe,
>>>
>>> On 09/11/16 16:00, Joe Lawrence wrote:
>>>> Hi Sudip,
>>>>
>>>> I hit a sysfs_warn_dup inside QEMU running 4.9.0-rc4 (I suspect earlier
>>>> versions as well, but this is the first upstream I've run in a while).
>>>> This warning looks like something the kernel test robot ran into a few
>>>> months ago:
>>>
>>> Yes, 0day reported, but I was unable to reproduce it with the config
>>> file that was given. Can you please send me your .config file and I will
>>> try to reproduce this on my setup, and if I am not able to then i will
>>> have to disturb you for debugging and testing.
>
> Can you please test the attached patch and try to reproduce the error...
> Sorry I could not test it as i could not build using your .config, I
> guess its time for me to upgrade gcc.
FWIW, my versino of gcc:
gcc (GCC) 4.8.5 20150623 (Red Hat 4.8.5-4)
I gave the patch a quick test and it loaded without any warnings on
boot. I also gave it a few rmmod / modprobe cycles and didn't see any
further warnings.
Thanks!
Tested-by: Joe Lawrence <joe.lawrence@redhat.com>
-- Joe
prev parent reply other threads:[~2016-11-11 22:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-09 16:00 Joe Lawrence
2016-11-09 17:04 ` Sudip Mukherjee
2016-11-09 18:41 ` Joe Lawrence
2016-11-11 21:14 ` Sudip Mukherjee
2016-11-11 22:16 ` Joe Lawrence [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=80647f01-bf8e-56c6-4933-c161bbce3fc6@redhat.com \
--to=joe.lawrence@redhat.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sudipm.mukherjee@gmail.com \
/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
all inboxes | Powered by JetHome®