On Mon, Aug 12, 2019 at 07:18:45PM +0200, Hans de Goede wrote:
> Hi,
>
> On 09-08-19 17:11, Yauhen Kharuzhy wrote:
> > On Fri, Aug 09, 2019 at 01:06:01PM +0200, Hans de Goede wrote:
> > > Hi,
> > >
> > > On 8/9/19 12:01 AM, Yauhen Kharuzhy wrote:
> > > > Intel Cherry Trail Whiskey Cove extcon
Prepare for future PM support and fix error handling by disabling
interrupts as needed.
Signed-off-by: Pierre-Louis Bossart
---
drivers/soundwire/cadence_master.c | 18 --
drivers/soundwire/cadence_master.h | 2 +-
drivers/soundwire/intel.c | 12 +++-
3 files
Move code to helper for reuse in power management routines
Signed-off-by: Pierre-Louis Bossart
---
drivers/soundwire/intel.c | 16 +++-
1 file changed, 11 insertions(+), 5 deletions(-)
diff --git a/drivers/soundwire/intel.c b/drivers/soundwire/intel.c
index
Multiple changes squashed in single patch to avoid tick-tock effect
and avoid breaking compilation/bisect
1. Per the hardware documentation, all changes to MCP_CONFIG,
MCP_CONTROL, MCP_CMDCTRL and MCP_PHYCTRL need to be validated with a
self-clearing write to MCP_CONFIG_UPDATE. Add a helper and
The use of clock stop is not a requirement, the IP can e.g. be
completely power gated and not detect any wakes while in s2idle/deep
sleep.
For now clock-stop is not supported anyways so the control parameter
is always false. This will be revisited when we add clock stop.
Signed-off-by:
V2 of the original series 'soundwire: inits and PM additions for 5.4',
with PM additions removed since more tests on hardware are required.
Changes since v1: addressed feedback from Vinod Koul
clarified init changes impact Intel and Cadence sides
remove unnecessary intermediate variable
disable
Provide debugfs capability to kick link and devices into hard-reset
(as defined by MIPI). This capability is really useful when some
devices are no longer responsive and/or to check the software handling
of resynchronization.
Signed-off-by: Pierre-Louis Bossart
---
On Mon, Sep 16, 2019 at 10:44:31AM -0700, Linus Torvalds wrote:
> - add new GRND_SECURE and GRND_INSECURE flags that have the actual
> useful behaviors that we currently pretty much lack
>
> - consider the old 0-3 flag values legacy, deprecated, and unsafe
> because they _will_ time out to fix
The Real-Time Summit is organized by the Linux Foundation Real-Time Linux (RTL)
collaborative project. The event is intended to gather developers and users of
Linux as a Real-Time Operating System. The main intent is to provide room for
discussion between developers, tooling experts, and users.
On 9/15/19 2:20 PM, Marc Zyngier wrote:
> On Sun, 15 Sep 2019 18:31:33 +0100,
> Palmer Dabbelt wrote:
>
> Hi Palmer,
>
>>
>> On Sun, 15 Sep 2019 07:24:20 PDT (-0700), m...@kernel.org wrote:
>>> On Thu, 12 Sep 2019 22:40:34 +0100,
>>> Darius Rad wrote:
>>>
>>> Hi Darius,
>>>
As per
Use devm_platform_ioremap_resource helper which wraps
platform_get_resource() and devm_ioremap_resource() together.
The semantic patch that makes this report is available
in scripts/coccinelle/api/devm_platform_ioremap_resource.cocci.
Found using - http://coccinelle.lip6.fr/
Signed-off-by:
Convert existing device tree bindings to yaml.
Signed-off-by: Tomasz Duszynski
---
.../devicetree/bindings/iio/light/bh1750.txt | 18
.../devicetree/bindings/iio/light/bh1750.yaml | 43 +++
2 files changed, 43 insertions(+), 18 deletions(-)
delete mode 100644
Convert ROHM BH1750 ambient light sensor bindings to yaml
format and while at it add myself as a driver maintainer.
Tomasz Duszynski (2):
dt-bindings: iio: light: bh1750: convert bindings to yaml
MAINTAINERS: add entry for ROHM BH1750 driver
.../devicetree/bindings/iio/light/bh1750.txt |
Add myself as a ROHM BH1750 ambient light sensor driver maintainer.
Signed-off-by: Tomasz Duszynski
---
MAINTAINERS | 6 ++
1 file changed, 6 insertions(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index f0c03740b9fb..928059c5cd49 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -13792,6
On Mon, Sep 16, 2019 at 12:32:52PM -0400, Alan Stern wrote:
> On Mon, 16 Sep 2019, Andrey Konovalov wrote:
>
> > On Fri, Sep 13, 2019 at 10:35 PM Alan Stern
> > wrote:
> > >
> > > On Fri, 13 Sep 2019, syzbot wrote:
> > >
> > > > syzbot has found a reproducer for the following crash on:
> > > >
The debug message after platform_get_irq() failure is redundant
because platform_get_irq() already prints an error. Thus remove it.
The semantic patch that makes this report is available
in scripts/coccinelle/api/platform_get_irq.cocci.
Found using - http://coccinelle.lip6.fr/
Signed-off-by:
This is not needed and may generate unmet dependencies when
COMPILE_TEST is used for SOF.
ACPI is required, and should be tested when selecting this option.
Signed-off-by: Pierre-Louis Bossart
---
drivers/soundwire/Kconfig | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
readl/writel and ioread32 are used without the relevant headers, fix.
Signed-off-by: Pierre-Louis Bossart
---
drivers/soundwire/intel.c | 1 +
drivers/soundwire/intel_init.c | 1 +
2 files changed, 2 insertions(+)
diff --git a/drivers/soundwire/intel.c b/drivers/soundwire/intel.c
index
Relational and logical operators evaluate to bool,
explicit conversion is overly verbose and unneeded.
Found using - Coccinelle (http://coccinelle.lip6.fr)
Signed-off-by: Saiyam Doshi
---
drivers/i2c/busses/i2c-qup.c | 14 ++
1 file changed, 6 insertions(+), 8 deletions(-)
diff
The Intel kbuild test reported issues with COMPILE_TEST or
cross-compilation when SOF is enabled, fix. This has no functional
impact.
Pierre-Louis Bossart (2):
soundwire: intel: add missing headers for cross-compilation
soundwire: intel: remove X86 dependency
drivers/soundwire/Kconfig
Using cocciecheck to ensure there are no semantic issues in
i2c-qup driver.
Refer below links for more information.
http://coccinelle.lip6.fr
https://bottest.wiki.kernel.org/coccicheck
Saiyam Doshi (3):
i2c: qup: remove explicit conversion to boolean
i2c: qup: Remove dev_err() log after
On Mon, Sep 16, 2019 at 04:39:59PM +0800, Wanpeng Li wrote:
> From: Wanpeng Li
>
> Filter out drastic fluctuation and random fluctuation, remove
> timer_advance_adjust_done altogether, the adjustment would be
> continuous.
>
> Signed-off-by: Wanpeng Li
> ---
> arch/x86/kvm/lapic.c | 26
Dear Friend!!!
I know that this message will come to you as a surprise.
I am the Auditing and Accounting section manager in (BOA BANK)
Ouagadougou Burkina Faso. I Hope that you
will not expose or betray
this trust and confident that I am about to repose on you for the
mutual benefit of our both
Hello,
syzbot found the following crash on:
HEAD commit:f0df5c1b usb-fuzzer: main usb gadget fuzzer driver
git tree: https://github.com/google/kasan.git usb-fuzzer
console output: https://syzkaller.appspot.com/x/log.txt?x=1462f9a560
kernel config:
Hello,
syzbot found the following crash on:
HEAD commit:f0df5c1b usb-fuzzer: main usb gadget fuzzer driver
git tree: https://github.com/google/kasan.git usb-fuzzer
console output: https://syzkaller.appspot.com/x/log.txt?x=170b213e60
kernel config:
As reported by Eugeniu Rosca, a side of affect of commit c3f2490d6e92
("selftests: watchdog: Add optional file argument") is that arbitrary files
may be opened for watchdog testing, e.g.
./watchdog-test -f /dev/zero
Watchdog Ticking Away!
To prevent watchdog-test from operating on non-watchdog
Hello,
syzbot found the following crash on:
HEAD commit:f0df5c1b usb-fuzzer: main usb gadget fuzzer driver
git tree: https://github.com/google/kasan.git usb-fuzzer
console output: https://syzkaller.appspot.com/x/log.txt?x=10efb5fa60
kernel config:
Hello,
syzbot found the following crash on:
HEAD commit:014077b5 DO-NOT-SUBMIT: usb-fuzzer: main usb gadget fuzzer..
git tree: https://github.com/google/kmsan.git master
console output: https://syzkaller.appspot.com/x/log.txt?x=1510d63a60
kernel config:
Hello,
syzbot found the following crash on:
HEAD commit:f0df5c1b usb-fuzzer: main usb gadget fuzzer driver
git tree: https://github.com/google/kasan.git usb-fuzzer
console output: https://syzkaller.appspot.com/x/log.txt?x=14982e6e60
kernel config:
Hello,
syzbot found the following crash on:
HEAD commit:014077b5 DO-NOT-SUBMIT: usb-fuzzer: main usb gadget fuzzer..
git tree: https://github.com/google/kmsan.git master
console output: https://syzkaller.appspot.com/x/log.txt?x=16a7dde160
kernel config:
Hello,
syzbot found the following crash on:
HEAD commit:f0df5c1b usb-fuzzer: main usb gadget fuzzer driver
git tree: https://github.com/google/kasan.git usb-fuzzer
console output: https://syzkaller.appspot.com/x/log.txt?x=1681c9c160
kernel config:
Hello,
syzbot found the following crash on:
HEAD commit:f0df5c1b usb-fuzzer: main usb gadget fuzzer driver
git tree: https://github.com/google/kasan.git usb-fuzzer
console output: https://syzkaller.appspot.com/x/log.txt?x=14b1537160
kernel config:
On Sat, Sep 14, 2019 at 02:43:28PM +0200, Borislav Petkov wrote:
> Hey Josh,
>
> I'm seeing
>
> arch/x86/kernel/cpu/mce/core.o: warning: objtool: mce_panic()+0x11b:
> unreachable instruction
>
> on a brand new debian install here with gcc9: gcc (Debian 9.2.1-4) 9.2.1
> 20190821
>
> and
On Mon, Sep 16, 2019 at 02:42:03PM +0100, Mark Brown wrote:
> On Mon, Sep 16, 2019 at 03:16:54PM +0200, Anders Roxell wrote:
>
> > If I re-read the Documentation/dev-tools/kselftest.rst
> > I think the patch from the kselftest tree should be dropped.
>
> > I saw that I didn't send an email to
Quoting Kim, Cheol Yong (2019-09-09 07:16:29)
>
> I've discussed internally the amount of efforts to create a reusable
> regmap clock driver which might be reused by other companies too.
>
> It seems it requires significant efforts for implementation/tests. As we
> don't plan to support our
Jacek
On 9/15/19 11:20 AM, Jacek Anaszewski wrote:
+
+static int led_multicolor_init_color(struct led_classdev_mc_data *data,
+struct led_classdev_mc *mcled_cdev,
+int color_id, int color_index)
+{
+ struct
On Mon, 16 Sep 2019, Qian Cai wrote:
> SLUB_RESILIENCY_TEST and SLUB_DEBUG_CMPXCHG look like some left-over
> debugging code during the internal development that probably nobody uses
> it anymore. Remove them to make the world greener.
Adding Pengfei Li who has been working on a patchset for
Quoting Wen He (2019-08-19 19:24:25)
>
> >
> > > > > +
> > > > > +static int plldig_clk_probe(struct platform_device *pdev) {
> > > > > + struct clk_plldig *data;
> > > > > + struct resource *mem;
> > > > > + const char *parent_name;
> > > > > + struct clk_init_data init
Dan,
On 9/16/19 3:56 PM, Dan Murphy wrote:
> Hello
>
> On 9/15/19 8:57 AM, Jacek Anaszewski wrote:
>> Hi Dan,
>>
>> On 9/11/19 8:01 PM, Dan Murphy wrote:
>>> Add a documentation of LED Multicolor LED class specific
>>> sysfs attributes.
>>>
>>> Signed-off-by: Dan Murphy
>>> ---
>>>
Hi Linus,
please pull the parisc architecture updates for kernel 5.4 from:
git://git.kernel.org/pub/scm/linux/kernel/git/deller/parisc-linux.git
parisc-5.4-1
Major changes:
* Make the powerpc implementation to read elf files available as a public
kexec interface so it can be re-used on
set_zspage_inuse() was introduced in the commit 4f42047bbde0 ("zsmalloc:
use accessor") but all the users of it were removed later by the
commits,
bdb0af7ca8f0 ("zsmalloc: factor page chain functionality out")
3783689a1aa8 ("zsmalloc: introduce zspage structure")
so the function can be safely
Hello,
On Fri, Sep 13, 2019 at 03:57:43PM -0700, Guru Das Srinagesh wrote:
> From: Fenglin Wu
>
> Normally, PWM channel has fixed output until software request to change
> its settings. There are some PWM devices which their outputs could be
> changed autonomously according to a predefined
On Mon, Sep 16, 2019 at 09:52:51AM +0100, David Howells wrote:
> Joe Perches wrote:
>
> > > I would recommend splitting the patch in two and putting something like:
> > >
> > > keys: Add Jarkko Sakkinen as co-maintainer
> > >
> > > as the subject of the keyrings maintainership one.
> >
> >
On Fri, Sep 13, 2019 at 4:48 PM Joe Perches wrote:
>
> On Fri, 2019-09-13 at 16:13 -0500, Rob Herring wrote:
> > DT bindings are moving to using a json-schema based schema format
> > instead of freeform text. Add a checkpatch.pl check to encourage using
> > the schema for new bindings. It's not
@@ -1043,8 +1043,6 @@ static int intel_probe(struct platform_device
*pdev)
if (ret)
goto err_init;
- ret = sdw_cdns_enable_interrupt(>cdns);
-
/* Read the PDI config and initialize cadence PDI */
intel_pdi_init(sdw, );
ret = sdw_cdns_pdi_init(>cdns,
The tm_yday and tm_wday fields are not used by userspace,
so since they aren't needed within the driver, don't
bother calculating them. This is especially needed since
the rtc_year_days() call was crashing if the HW returned
an invalid time.
Signed-off-by: Nick Crews
---
Signed-off-by: Nick Crews
---
drivers/rtc/rtc-wilco-ec.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/rtc/rtc-wilco-ec.c b/drivers/rtc/rtc-wilco-ec.c
index e84faa268caf..951268f5e690 100644
--- a/drivers/rtc/rtc-wilco-ec.c
+++ b/drivers/rtc/rtc-wilco-ec.c
@@ -184,5
On So, 15.09.19 10:32, Linus Torvalds (torva...@linux-foundation.org) wrote:
> [ Added Lennart, who was active in the other thread ]
>
> On Sat, Sep 14, 2019 at 10:22 PM Theodore Y. Ts'o wrote:
> >
> > Thus, add an optional configuration option which stops getrandom(2)
> > from blocking, but
Hello,
My name is MR Ben, I am very happy to be in contact with you.
Please I want you to assist me to invest my inherited funds in your country.
Reply for more details to this myprivate Email ID:
pinkbirds2...@gmail.com if you are willing to assist me.
Sincerely,
MR Ben,
On Mon, Sep 16, 2019 at 11:15 AM Manivannan Sadhasivam
wrote:
>
> Add YAML devicetree binding for Bitmain BM1880 SoC.
>
> Signed-off-by: Manivannan Sadhasivam
> ---
> .../bindings/clock/bitmain,bm1880-clk.yaml| 76 +
> include/dt-bindings/clock/bm1880-clock.h | 82
16.09.2019 22:21, Theodore Y. Ts'o пишет:
On Mon, Sep 16, 2019 at 09:17:10AM -0700, Linus Torvalds wrote:
So the semantics that getrandom() should have had are:
getrandom(0) - just give me reasonable random numbers for any of a
million non-strict-long-term-security use (ie the old urandom)
On Mon, Sep 16, 2019 at 10:46 AM Manivannan Sadhasivam
wrote:
>
> Add devicetree YAML binding for Actions Semi Owl SoC's SD/MMC/SDIO
> controller.
>
> Signed-off-by: Manivannan Sadhasivam
> ---
> .../devicetree/bindings/mmc/owl-mmc.yaml | 59 +++
> 1 file changed, 59
On 9/16/19 9:49 AM, Cong Wang wrote:
On Mon, Sep 16, 2019 at 6:29 AM syzbot
wrote:
Hello,
syzbot found the following crash on:
HEAD commit:f4b752a6 mlx4: fix spelling mistake "veify" -> "verify"
git tree: net
console output: https://syzkaller.appspot.com/x/log.txt?x=16cbebe660
On Mon, Sep 16, 2019 at 2:02 AM Alexandre Belloni
wrote:
>
> On 15/09/2019 23:44:03+0100, Nick Crews wrote:
> > Hi Alexandre, thanks for the thoughts.
> >
> > On Thu, Sep 12, 2019 at 9:09 AM Alexandre Belloni
> > wrote:
> > >
> > > Hi Nick,
> > >
> > > On 10/09/2019 16:19:29+0100, Nick Crews
> - add new GRND_SECURE and GRND_INSECURE flags that have the actual
> useful behaviors that we currently pretty much lack
>
> - consider the old 0-3 flag values legacy, deprecated, and unsafe
> because they _will_ time out to fix the existing problem we have right
> now because of their bad
Hello,
My name is MR Ben, I am very happy to be in contact with you.
Please I want you to assist me to invest my inherited funds in your country.
Reply for more details to this myprivate Email ID:
pinkbirds2...@gmail.com if you are willing to assist me.
Sincerely,
MR Ben,
On Wed, 11 Sep 2019, Cornelia Huck wrote:
> The common I/O layer is maintaining an "intparm" inspired by
> the hardware intparm for driver usage. This "intparm" is not
> only applicaple for ssch, but also for hsch/csch. The kerneldoc
> states that it is only updated for hsch/csch if no prior
Dear Friend,
I am Ms Lisa Hugh work with the department of Audit and accounting manager here
in the Bank,
There is this fund that was keep in my custody years ago,please i need your
assistance for the transferring of thIs fund to your bank account for both of
us benefit for life time
On Mon, Sep 16, 2019 at 10:21 AM Theodore Y. Ts'o wrote:
>
> We could create a new flag, GRND_INSECURE, which never blocks. And
> that that allows us to solve the problem for silly applications that
> are using getrandom(2) for non-cryptographic use cases.
Note that getting "reasonably good
On Mon, 16 Sep 2019 09:54:41 PDT (-0700), pbonz...@redhat.com wrote:
Linus,
The following changes since commit e4427372398c31f57450565de277f861a4db5b3b:
selftests/kvm: make platform_info_test pass on AMD (2019-08-21 19:08:18 +0200)
are available in the git repository at:
On Mon, Sep 16, 2019 at 10:25 AM Linus Torvalds
wrote:
>
> On Mon, Sep 16, 2019 at 2:18 AM Rasmus Villemoes
> wrote:
> >
> > Eh, this benchmark doesn't seem to provide any hints on where to set the
> > cut-off for a compile-time constant n, i.e. the 32 in
>
> Yes, you'd need to use proper
On Mon, Sep 16, 2019 at 11:37:18AM +, Tony W Wang-oc wrote:
> Zhaoxin newer CPUs support LMCE that compatible with Intel's
> "Machine-Check Architecture", so add support for Zhaoxin LMCE
> in mce/core.c.
>
> Signed-off-by: Tony W Wang-oc
> ---
> arch/x86/kernel/cpu/mce/core.c | 35
On Mon, Sep 16, 2019 at 2:18 AM Rasmus Villemoes
wrote:
>
> Eh, this benchmark doesn't seem to provide any hints on where to set the
> cut-off for a compile-time constant n, i.e. the 32 in
Yes, you'd need to use proper fixed-size memset's with
__builtin_memset() to test that case. Probably easy
On Fri, Sep 13, 2019 at 2:18 AM Kirill A. Shutemov wrote:
>
> Adding fully unmapped pages into deferred split queue is not productive:
> these pages are about to be freed or they are pinned and cannot be split
> anyway.
This change looks good to me. Reviewed-by: Yang Shi
>
> Signed-off-by:
On Mon, Sep 16, 2019 at 09:17:10AM -0700, Linus Torvalds wrote:
> So the semantics that getrandom() should have had are:
>
> getrandom(0) - just give me reasonable random numbers for any of a
> million non-strict-long-term-security use (ie the old urandom)
>
> - the nonblocking flag makes
On Mon, Sep 16, 2019 at 9:23 AM Vitaly Kuznetsov wrote:
>
> KVM needs to know if SMT is theoretically possible, this means it is
> supported and not forcefully disabled ('nosmt=force'). Create and
> export cpu_smt_possible() answering this question.
It seems to me that KVM really just wants to
On 9/16/19 11:24 AM, Darrick J. Wong wrote:
> On Fri, Sep 06, 2019 at 02:26:46PM +0800, yu kuai wrote:
>> In commit d03a2f1b9fa8 ("xfs: include WARN, REPAIR build options in
>> XFS_BUILD_OPTIONS"), Eric pointed out that the XFS_BUILD_OPTIONS string,
>> shown at module init time and in modinfo
On Mon, Sep 16, 2019 at 01:08:45PM -0400, Martin K. Petersen wrote:
> Vendor driver submissions, however, are generally huge. Sometimes 50+
> patches per submission window. And during this window I often get on the
> order of 10 to 20 patches for the same driver in the fixes tree. It is
> not
On Mon, Sep 16, 2019 at 07:25:48AM -0700, Dave Hansen wrote:
> On 9/16/19 2:00 AM, Kirill A. Shutemov wrote:
> >>> I think we also need to make it clear that this is workaround for a broken
> >>> hardware: speculative execution must not trigger a halt.
> >> I think the word broken is a bit loaded
On Sat, Sep 14, 2019 at 08:24:37AM +0200, Markus Elfring wrote:
> I suggest to take another look at a similar patch.
>
> fs/omfs: make use of kmemdup
> https://lore.kernel.org/r/20190721112326.GA5927@hari-Inspiron-1545/
> https://lore.kernel.org/patchwork/patch/1102482/
>
Dan,
>> One pet peeve I have is that people are pretty bad at indicating the
>> intended target tree. I often ask for it in private mail but the
>> practice doesn't seem to stick. I spend a ton of time guessing whether a
>> patch is a fix for a new feature in the x+1 queue or a fix for the
>>
On Thu, 12 Sep 2019 19:46:01 -0700
Sean Christopherson wrote:
> Restore the fast invalidate flow for zapping shadow pages and use it
> whenever vCPUs can be active in the VM. This fixes (in theory, not yet
> confirmed) a regression reported by James Harvey where KVM can livelock
> in
On Mon, Sep 16, 2019 at 10:00 AM Theodore Y. Ts'o wrote:
>
> How /dev/random blocks is very different from how getrandom(2) blocks.
> Getrandom(2) blocks until the CRNG, and then it never blocks again.
Yes and no.
getrandom() very much blocks exactly like /dev/random, when you give
it the
On Sun, Sep 15, 2019 at 08:40:30PM -0700, Linus Torvalds wrote:
> On Sun, Sep 15, 2019 at 8:23 PM Theodore Y. Ts'o wrote:
> >
> > But not blocking is *precisely* what lead us to weak keys in network
> > devices that were sold by the millions to users in their printers,
> > wifi routers, etc.
>
>
On Thu, 2019-09-12 at 18:17 -0400, Joel Fernandes wrote:
> On Wed, Sep 11, 2019 at 05:57:29PM +0100, Scott Wood wrote:
> > rcutorture was generating some nesting scenarios that are not
> > reasonable. Constrain the state selection to avoid them.
> >
> > Example #1:
> >
> > 1. preempt_disable()
Linus,
The following changes since commit e4427372398c31f57450565de277f861a4db5b3b:
selftests/kvm: make platform_info_test pass on AMD (2019-08-21 19:08:18 +0200)
are available in the git repository at:
https://git.kernel.org/pub/scm/virt/kvm/kvm.git tags/for-linus
for you to fetch
Hi,
On 16/09/19 1:08 PM, Ramuthevar,Vadivel MuruganX wrote:
> patch 1: Add YAML for cadence-qspi devicetree cdocumentation.
> patch 2: cadence-qspi controller driver to support QSPI-NAND flash
> using existing spi-nand framework with legacy spi protocol.
Nope, you cannot have two drivers for the
On Mon, Sep 16, 2019 at 6:29 AM syzbot
wrote:
>
> Hello,
>
> syzbot found the following crash on:
>
> HEAD commit:f4b752a6 mlx4: fix spelling mistake "veify" -> "verify"
> git tree: net
> console output: https://syzkaller.appspot.com/x/log.txt?x=16cbebe660
> kernel config:
On 9/10/19 6:03 AM, Eugene Syromiatnikov wrote:
* tools/testing/selftests/Makefile (TARGETS): Add clone3.
Again. No filenames in the commit log. Please add more detail.
"Adding clone3() tests to kselftest default run and details
on what this tests"
This will be helpful to users.
On 9/10/19 6:03 AM, Eugene Syromiatnikov wrote:
clone3() is available on most architectures, so there's no reason to
restrict the respective self-tests to x86_64.
Is it missing on any? Please key off of the return value and exit with
skip if unsupported.
*
On Mon, Sep 16, 2019 at 11:22:18AM -0400, Alan Stern wrote:
> On Mon, 16 Sep 2019, Boqun Feng wrote:
>
> > > executes if Y is a store.) This is expressed by the visibility
> > > relation (vis), where X ->vis Y is defined to hold if there is an
> > > intermediate event Z such that:
> > >
> > >
On 9/10/19 6:03 AM, Eugene Syromiatnikov wrote:
* tools/testing/selftests/clone3/clone3.c (test_clone3): Change format
qualifier for printing size field from %d to %zu; place colon right
after the word "says".
Please drop the file name. The rest looks good. I am assuming there is
a reason for
On Mon, 16 Sep 2019, syzbot wrote:
> Hello,
>
> syzbot found the following crash on:
>
> HEAD commit:f0df5c1b usb-fuzzer: main usb gadget fuzzer driver
> git tree: https://github.com/google/kasan.git usb-fuzzer
> console output: https://syzkaller.appspot.com/x/log.txt?x=11512cd160
On 9/10/19 6:03 AM, Eugene Syromiatnikov wrote:
Flags parameter in both userspace and kernel clone args is 64-bit wide,
there's little reason to have it signed and 32-bit in tests.
So what are doing? You are stating the problem here, how are you
fixing it?
*
On Mon, Sep 16, 2019 at 3:40 PM Mark Brown wrote:
>
> Hi all,
>
> Today's linux-next merge of the vfs tree got a conflict in:
>
> fs/ubifs/super.c
>
> between commit:
>
> 9163e0184bd7d5f ("ubifs: Fix memory leak bug in alloc_ubifs_info() error
> path")
>
> from the ubifs tree and commit:
>
>
On 9/10/19 6:03 AM, Eugene Syromiatnikov wrote:
Check that the kernel fails calls with exit_signal with non-zero highest
32 bits.
Describe what you are testing:
"Add a test case for clone3() non-zero highest 32 bits behavior. It
should fail with exit_signal value??"
Add checks for
On Mon, Sep 16, 2019 at 9:23 AM Vitaly Kuznetsov wrote:
>
> Hyper-V 2019 doesn't expose MD_CLEAR CPUID bit to guests when it cannot
> guarantee that two virtual processors won't end up running on sibling SMT
> threads without knowing about it. This is done as an optimization as in
> this case
On Mon, 16 Sep 2019, Andrey Konovalov wrote:
> On Fri, Sep 13, 2019 at 10:35 PM Alan Stern wrote:
> >
> > On Fri, 13 Sep 2019, syzbot wrote:
> >
> > > syzbot has found a reproducer for the following crash on:
> > >
> > > HEAD commit:f0df5c1b usb-fuzzer: main usb gadget fuzzer driver
> > >
On Mon, Sep 16, 2019 at 5:50 PM Thierry Reding wrote:
> On Mon, Sep 16, 2019 at 08:43:36AM -0700, Guenter Roeck wrote:
> > On Mon, Sep 16, 2019 at 03:49:20PM +0200, Thierry Reding wrote:
> > > On Mon, Sep 16, 2019 at 06:17:01AM -0700, Guenter Roeck wrote:
> > > > On 9/16/19 12:49 AM, Arnd
On 9/10/19 6:03 AM, Eugene Syromiatnikov wrote:
* tools/testing/selftests/clone3/clone3.c (CLONE3_ARGS_NO_TEST,
CLONE3_ARGS_ALL_0, CLONE3_ARGS_ALL_1): Change into an enum.
(call_clone3): Change test_mode parameter type to enum test_mode;
use switch statement for actions that dependent on
* H. Nikolaus Schaller [190911 17:48]:
> CHANGES V3:
> * make omap36xx control the abb-ldo and properly switch mode
> (suggested by Adam Ford )
> * add a note about enabling the turbo-mode OPPs
Looks good to me, when applying, please provide a
minimal immutable branch maybe against v5.3 or
* H. Nikolaus Schaller [190911 17:48]:
> From: Adam Ford
>
> The AM3517 only lists 600MHz @ 1.2V, but the register values for
> 0x4830A204 = 1b86 802f, it seems like am3517 might be a derivative
> of the omap36 which OPPs would be OPP50 (300 MHz) and OPP100
> (600 MHz).
>
> This patch sets up
* H. Nikolaus Schaller [190911 17:48]:
> See DM3730,DM275 data sheet (SPRS685B) footnote (6) in Table 4-19
> which says that ABB must be switched to FBB mode when using the
> OPP1G.
>
> The LOD definition abb_mpu_iva already exists so that we need
> to add plumbing for vbb-supply = <_mpu_iva>
>
* H. Nikolaus Schaller [190911 17:48]:
> From: Adam Ford
>
> The AM3517 only lists 600MHz @ 1.2V, but the register values for
> 0x4830A204 = 1b86 802f, it seems like am3517 might be a derivative
> of the omap36 which OPPs would be OPP50 (300 MHz) and OPP100
> (600 MHz).
>
> This patch simply
* H. Nikolaus Schaller [190911 17:48]:
> In preparation for using the multi_regulator capability of
> this driver for handling the ABB LDO for OPP1G of the omap36xx
> we have to take care that the (legacy) vdd-supply name is
> cpu0-supply = <>;
>
> To do this we add another field to the SoC
On Fri, Sep 06, 2019 at 02:26:46PM +0800, yu kuai wrote:
> In commit d03a2f1b9fa8 ("xfs: include WARN, REPAIR build options in
> XFS_BUILD_OPTIONS"), Eric pointed out that the XFS_BUILD_OPTIONS string,
> shown at module init time and in modinfo output, does not currently
> include all available
[The series is KVM specific but the first patch of the series likely requires
someone else's ACK. hyperv-tlfs.h gets a small addition too.]
It was discovered that L2 guests on Hyper-V 2019 on KVM don't see MD_CLEAR
bit (and thus think they're MDS vulnerable) even when it is present on the
host.
The bit is supposed to be '1' when SMT is not supported or forcefully
disabled and '0' otherwise.
Signed-off-by: Vitaly Kuznetsov
---
.../selftests/kvm/x86_64/hyperv_cpuid.c | 27 +++
1 file changed, 27 insertions(+)
diff --git
KVM needs to know if SMT is theoretically possible, this means it is
supported and not forcefully disabled ('nosmt=force'). Create and
export cpu_smt_possible() answering this question.
Signed-off-by: Vitaly Kuznetsov
---
include/linux/cpu.h | 2 ++
kernel/cpu.c| 11 +--
2
Hyper-V 2019 doesn't expose MD_CLEAR CPUID bit to guests when it cannot
guarantee that two virtual processors won't end up running on sibling SMT
threads without knowing about it. This is done as an optimization as in
this case there is nothing the guest can do to protect itself against MDS
and
301 - 400 of 836 matches
Mail list logo
