From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Jinpu Wang <jinpu.wang@profitbricks.com>
Cc: Thomas Gleixner <tglx@linutronix.de>, stable <stable@vger.kernel.org>
Subject: Re: [BUG]smt sysfs dir missing on 4.4.148 and 4.14.63
Date: Thu, 16 Aug 2018 17:51:26 +0200 [thread overview]
Message-ID: <20180816155126.GA18296@kroah.com> (raw)
In-Reply-To: <CAMGffEnzVo5VVSVBjCOBMhcoV1qXf0XXqJqr3C01xQn-aUiZFQ@mail.gmail.com>
On Thu, Aug 16, 2018 at 05:43:23PM +0200, Jinpu Wang wrote:
> Hi Greg, hi Thomas,
>
> I noticed /sys/devices/system/cpu/smt dir is missing on 4.4.148 and
> 4.14.63, default setting.
For 4.4, I would be amazed if anything was there, the backport was done
only to handle the local user issue, not the "full" protection. So
please try 4.9 or 4.14.
How about 4.17 and 4.18, do those trees work properly for you?
> Tried stable/master branch 31130a16d459 ("Merge tag
> 'for-linus-4.19-rc1-tag' of
> git://git.kernel.org/pub/scm/linux/kernel/git/xen/tip")
> It's the same there.
Ah, so we are bug compatible, good :)
> When boot with 'nosmt' kernel paramter kernel 4.14.63 panic during
> boot, 4.4.148 boot fine.
> The call trace seem irq related, is it known bug?
You are not giving us much to go on here sorry. We need full details,
and also please cc: lkml and the other developers who worked on this.
THomas is on vacation this week.
thanks,
greg k-h
next prev parent reply other threads:[~2018-08-16 18:50 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-16 15:43 [BUG]smt sysfs dir missing on 4.4.148 and 4.14.63 Jinpu Wang
2018-08-16 15:51 ` Greg Kroah-Hartman [this message]
2018-08-16 16:28 ` Jinpu Wang
2018-08-16 16:39 ` Greg Kroah-Hartman
2018-08-16 16:48 ` Jinpu Wang
2018-08-17 12:39 ` Jinpu Wang
2018-08-17 17:01 ` Greg Kroah-Hartman
2018-08-18 12:50 ` Thomas Gleixner
2018-08-20 8:05 ` Jinpu Wang
2018-08-20 13:02 ` Thomas Gleixner
2018-08-20 13:20 ` Jinpu Wang
2018-08-20 14:47 ` Thomas Gleixner
2018-08-20 14:52 ` Jinpu Wang
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=20180816155126.GA18296@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=jinpu.wang@profitbricks.com \
--cc=stable@vger.kernel.org \
--cc=tglx@linutronix.de \
/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