linux-kernel - Re: [driver core] eedc73d4f3: BUG:kernel_reboot-without-warning_in_boot

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <YVVX3ir2DHg0FUxF@kroah.com>
Date:   Thu, 30 Sep 2021 08:23:26 +0200
From:   Greg KH <gregkh@...uxfoundation.org>
To:     Oliver Sang <oliver.sang@...el.com>
Cc:     Yang Li <yang.lee@...ux.alibaba.com>, 0day robot <lkp@...el.com>,
        Abaci Robot <abaci@...ux.alibaba.com>,
        LKML <linux-kernel@...r.kernel.org>, lkp@...ts.01.org
Subject: Re: [driver core]  eedc73d4f3:
 BUG:kernel_reboot-without-warning_in_boot_stage

On Thu, Sep 30, 2021 at 01:59:44PM +0800, Oliver Sang wrote:
> Hi, Greg KH,
> 
> On Wed, Sep 29, 2021 at 05:13:55PM +0200, Greg KH wrote:
> > On Wed, Sep 29, 2021 at 11:02:40PM +0800, kernel test robot wrote:
> > > 
> > > 
> > > Greeting,
> > > 
> > > FYI, we noticed the following commit (built with gcc-9):
> > > 
> > > commit: eedc73d4f330cf7a8d18d64f327837ae9a00d003 ("[PATCH] driver core: Switch to using the new API kobj_to_dev()")
> > > url: https://github.com/0day-ci/linux/commits/Yang-Li/driver-core-Switch-to-using-the-new-API-kobj_to_dev/20210929-102216
> > > base: https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git 5816b3e6577eaa676ceb00a848f0fd65fe2adc29
> > 
> > There is no such commit in my tree, or anywhere else I can see, so I
> > have no idea what is happening here :(
> > 
> 
> this report was sent to Yang Li, who is the patch author.
> https://lore.kernel.org/lkml/1614590004-69592-1-git-send-email-yang.lee@linux.alibaba.com/
> 
> since Yang sent the patch to you, so our Rot automatically add you in
> the Cc list.

That patch was sent back on March 1.  And was instantly rejected for the
obvious reason it was never tested :)

Why is 0-day running on such old changes now?

And it is not obvious that this is being run on an email submission at
all, where would I have found that information in this response?  I see
a git id that points to a kernel tree.  No email link at all.

thanks,

greg k-h