Thanks,
applied to nvme-5.9.
From: zhuguangqing
In function thermal_cooling_device_stats_update(), if the input parameter
new_state is greater or equal to stats->max_states, then it will cause
slab-out-of-bounds error when execute the code as follows:
stats->trans_table[stats->state * stats->max_states + new_state]++;
Two
On Mon, 2020-09-14 at 17:23 -0600, Rob Herring wrote:
> On Sat, Sep 05, 2020 at 04:08:59PM +0800, Yong Wu wrote:
> > Convert MediaTek SMI to DT schema.
> >
> > Signed-off-by: Yong Wu
> > ---
> > .../mediatek,smi-common.txt | 49 --
> > .../mediatek,smi-common.yaml
On 9/14/20 10:41 PM, Mauro Carvalho Chehab wrote:
> Em Tue, 15 Sep 2020 00:25:07 +0900
> Masahiro Yamada escreveu:
>
>> On Sun, Sep 13, 2020 at 10:21 PM Maxim Levitsky wrote:
>>>
>>> I hate to say it, but xconfig got broken again.
>>>
>>> After commit 68fd110b3e7e2 ("kconfig: qconf: remove
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: fc4f28bb3daf3265d6bc5f73b497306985bb23ab
commit: e5fc436f06eef54ef512ea55a9db8eb9f2e76959 sparse: use static inline for
__chk_{user,io}_ptr()
date: 2 weeks ago
config: sh-randconfig-s031-20200913
On Mon, 2020-09-14 at 17:22 -0600, Rob Herring wrote:
> On Sat, Sep 05, 2020 at 04:08:58PM +0800, Yong Wu wrote:
> > Convert MediaTek IOMMU to DT schema.
> >
> > Signed-off-by: Yong Wu
> > ---
[...]
> > +properties:
> > + compatible:
> > +enum:
> > + - mediatek,mt2701-m4u #mt2701
Hello sir,
> > I hope the patch will get merged soon.
>
> No need to "hope"; you could split up Matthew's patch yourself, and test and
> send the resulting patches. From the above thread, it looks like the
> networking
> developers want one patch to fix the improper use of GFP_ATOMIC (which is
On 14/09/20 11:07 pm, Jiri Olsa wrote:
> On Mon, Sep 14, 2020 at 10:08:01AM -0700, Ian Rogers wrote:
>
> SNIP
>
>>>
>>> Using one of the MISC bits to resolve the union. Might actually bring
>>> benefit to everyone. Us normal people get to have a smaller MMAP record,
>>> while the buildid folks
8250 devices may modify iotype in their own earlycon setup. For example:
8250_mtk and 8250_uniphier force iotype to be MMIO32. Print earlycon info
after match->setup to reflect actual earlycon info.
Signed-off-by: Hsin-Yi Wang
---
Change:
v1->v2: rename function
---
To use mmio32, we also need to set regshift.
Signed-off-by: Hsin-Yi Wang
---
Change:
v1->v2: none
---
drivers/tty/serial/8250/8250_mtk.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/tty/serial/8250/8250_mtk.c
b/drivers/tty/serial/8250/8250_mtk.c
index
Jens,
can you pick this series up?
Am 15. September 2020 04:56:55 MESZ schrieb Masahiro Yamada
:
>On Tue, Sep 15, 2020 at 2:57 AM Frank Wunderlich
>> i try to use modules_install target after building kernel with
>KBUILD_OUTPUT set
>>
>> KBUILD_OUTPUT: /media/data_nvme/git/kernel/build #kernel source is in
Em Tue, 15 Sep 2020 00:25:07 +0900
Masahiro Yamada escreveu:
> On Sun, Sep 13, 2020 at 10:21 PM Maxim Levitsky wrote:
> >
> > I hate to say it, but xconfig got broken again.
> >
> > After commit 68fd110b3e7e2 ("kconfig: qconf: remove redundant help in the
> > info view")
> > help description
On Mon, Sep 14, 2020 at 05:01:47PM -0600, Mathieu Poirier wrote:
[700 lines of the fullquote deleted..]
> > + for (r = map; r->size; r++)
> > + num_ranges++;
> > +
> > + new_map = kmemdup(map, array_size(num_ranges + 1, sizeof(*map)),
> > + GFP_KERNEL);
> > +
On 15/09/20 1:00 am, Arnaldo Carvalho de Melo wrote:
> Em Mon, Sep 14, 2020 at 09:39:07PM +0200, Jiri Olsa escreveu:
>> On Mon, Sep 14, 2020 at 12:28:41PM -0300, Arnaldo Carvalho de Melo wrote:
>>> Em Mon, Sep 14, 2020 at 02:38:27PM +0900, Namhyung Kim escreveu:
On Mon, Sep 14, 2020 at 6:03
On 07:19 Tue 15 Sep 2020, Greg KH wrote:
On Tue, Sep 15, 2020 at 10:42:19AM +0530, Bhaskar Chowdhury wrote:
This patch removed the scrollback related lines from this file : vesafb.rst
In the effect of this commit hashes : 50145474f6ef4a9c19205b173da6264a644c7489
and
On Tue, Sep 15, 2020 at 10:43:31AM +0530, Anmol Karn wrote:
> On Mon, Sep 14, 2020 at 08:26:55PM +0100, Matthew Wilcox wrote:
> > On Tue, Sep 15, 2020 at 12:17:55AM +0530, Anmol Karn wrote:
> > > On Mon, Sep 14, 2020 at 12:08:03PM +0100, Matthew Wilcox wrote:
> > > > On Mon, Sep 14, 2020 at
On 2020-09-15 00:14, Stephen Boyd wrote:
Quoting Sai Prakash Ranjan (2020-09-14 04:12:59)
Cleanup qcom_llcc_cfg_program() by moving llcc attribute
configuration to a separate function of its own. Also
correct misspelled 'instance' caught by checkpatch.
Suggested-by: Stephen Boyd
On Tue, Sep 15, 2020 at 12:08:38PM +0800, Wu, Hao wrote:
> > On Tue, Sep 15, 2020 at 11:27:51AM +0800, Xu Yilun wrote:
> > > Device Feature List (DFL) is a linked list of feature headers within the
> > > device MMIO space. It is used by FPGA to enumerate multiple sub features
> > > within it. Each
On 2020-09-15 00:16, Stephen Boyd wrote:
Quoting Sai Prakash Ranjan (2020-09-14 04:13:00)
From: "Isaac J. Manjarres"
Older chipsets may not be allowed to configure certain LLCC registers
as that is handled by the secure side software. However, this is not
the case for newer chipsets and they
On Tue, Sep 15, 2020 at 10:42:19AM +0530, Bhaskar Chowdhury wrote:
> This patch removed the scrollback related lines from this file : vesafb.rst
>
> In the effect of this commit hashes : 50145474f6ef4a9c19205b173da6264a644c7489
> and 973c096f6a85e5b5f2a295126ba6928d9a6afd45
When referencing git
On 9/15/20 11:41 AM, Paul E. McKenney wrote:
On Tue, Sep 15, 2020 at 03:18:23AM +, Zhang, Qiang wrote:
发件人: Paul E. McKenney
发送时间: 2020年9月15日 4:56
收件人: Joel Fernandes
抄送: Zhang, Qiang; Uladzislau Rezki; j...@joshtriplett.org;
On Mon, Sep 14, 2020 at 8:18 PM Namhyung Kim wrote:
>
> Hello,
>
> I've found and fixed a bunch of memory leaks during perf pmu and
> metric tests with address sanitizer. Before this, the tests were
> mostly failed due to the leaks since ASAN makes it return non-zero.
>
> Now I'm seeing no error
This patch removed the scrollback related lines from this file : vesafb.rst
In the effect of this commit hashes : 50145474f6ef4a9c19205b173da6264a644c7489
and 973c096f6a85e5b5f2a295126ba6928d9a6afd45
Signed-off-by: Bhaskar Chowdhury
---
Documentation/fb/vesafb.rst | 2 --
1 file changed, 2
On Mon, Sep 14, 2020 at 08:26:55PM +0100, Matthew Wilcox wrote:
> On Tue, Sep 15, 2020 at 12:17:55AM +0530, Anmol Karn wrote:
> > On Mon, Sep 14, 2020 at 12:08:03PM +0100, Matthew Wilcox wrote:
> > > On Mon, Sep 14, 2020 at 12:47:24PM +0530, Anmol Karn wrote:
> > > > idr_get_next() gives
Hi Steven,
thanks for reply.
On 9/14/2020 9:49 PM, Steven Rostedt wrote:
> On Mon, 14 Sep 2020 10:00:50 +0530
> Gaurav Kohli wrote:
>
>> Hi Steven,
>>
>> Please let us know, if below change looks good.
>> Or let us know some other way to solve this.
>>
>> Thanks,
>> Gaurav
>>
>>
>
> Hmm, for
On Mon, 2020-09-14 at 20:06 +0800, Huazhong Tan wrote:
> From: Yunsheng Lin
>
> Use napi_consume_skb() to batch consuming skb when cleaning
> tx desc in NAPI polling.
>
> Signed-off-by: Yunsheng Lin
> Signed-off-by: Huazhong Tan
> ---
> drivers/net/ethernet/hisilicon/hns3/hns3_enet.c| 27
On 9/10/2020 3:01 PM, Kirill A. Shutemov wrote:
On Thu, Sep 10, 2020 at 01:47:39PM -0700, Vijay Balakrishna wrote:
When memory is hotplug added or removed the min_free_kbytes must be
recalculated based on what is expected by khugepaged. Currently
after hotplug, min_free_kbytes will be set
Hi Peter,
thanks for your comments!
On Tue, Sep 15, 2020 at 02:55:06AM +, Peter Chen wrote:
> On 20-09-14 11:27:49, Matthias Kaehlcke wrote:
> > The main issue this driver addresses is that a USB hub needs to be
> > powered before it can be discovered. For onboard hubs this is often
> >
Hello,
syzbot found the following issue on:
HEAD commit:7fe10096 Merge branch 'linus' of git://git.kernel.org/pub/..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=140b085390
kernel config: https://syzkaller.appspot.com/x/.config?x=a9075b36a6ae26c9
set_recommended_min_free_kbytes need to honor min_free_kbytes set by the
user. Post start-of-day THP enable or memory hotplug operations can
lose user specified min_free_kbytes, in particular when it is higher than
calculated recommended value.
Signed-off-by: Vijay Balakrishna
Cc:
This patch remove the stanza related to framebuffer scrollback effect.
It is the the effect of commit hashes :
50145474f6ef4a9c19205b173da6264a644c7489
and 973c096f6a85e5b5f2a295126ba6928d9a6afd45
Signed-off-by: Bhaskar Chowdhury
---
Documentation/fb/sstfb.rst | 3 ---
1 file changed, 3
On Thu, Sep 03, 2020 at 11:55:28PM -0400, Theodore Y. Ts'o wrote:
> Worse, right now, -rc1 and -rc2 is causing random crashes in my
> gce-xfstests framework. Sometimes it happens before we've run even a
> single xfstests; sometimes it happens after we have successfully
> completed all of the
On Tue 01 Sep 01:00 CDT 2020, Bao D. Nguyen wrote:
> UFS's specifications supports a range of Vcc operating
> voltage levels. Add documentation for the UFS's Vcc voltage
> levels setting.
>
> Signed-off-by: Can Guo
> Signed-off-by: Asutosh Das
> Signed-off-by: Bao D. Nguyen
> ---
>
> On Tue, Sep 15, 2020 at 11:27:52AM +0800, Xu Yilun wrote:
> > The description of feature_id in struct dfl_device is not accurate. In
> > DFL specification the feature_id is the 12 bits field. The description
> > in struct dfl_device_id is more clear so we make them aligned. We also
> > made the
This patch remove stale information lines from this file : matroxfb.rst
In effect of the the commit hashes : 50145474f6ef4a9c19205b173da6264a644c7489
and
973c096f6a85e5b5f2a295126ba6928d9a6afd45
Signed-off-by: Bhaskar Chowdhury
---
Documentation/fb/matroxfb.rst | 2 --
1 file changed, 2
On Mon, 2020-09-14 at 21:22 -0700, Nathan Chancellor wrote:
> It would be nice to get this into mainline sooner rather than later so
> that it can start filtering into the stable trees. ToT LLVM builds have
> been broken for a month now.
People that build stable trees with new compilers
On Mon, Sep 14, 2020 at 6:51 PM Josh Poimboeuf wrote:
> > > On Tue, Sep 08 2020 at 13:16, syzbot wrote:
> > >
> > > > Hello,
> > > >
> > > > syzbot found the following issue on:
> > > >
> > > > HEAD commit:f4d51dff Linux 5.9-rc4
> > > > git tree: upstream
> > > > console output:
Replace an instance of kmemdup() with the devres counted version
instead.
Signed-off-by: Moritz Fischer
---
drivers/net/ethernet/dec/tulip/de2104x.c | 5 ++---
1 file changed, 2 insertions(+), 3 deletions(-)
diff --git a/drivers/net/ethernet/dec/tulip/de2104x.c
Replace pci_enable_device() with its devres counterpart
pcim_enable_device().
Signed-off-by: Moritz Fischer
---
Note: Please check my logic on this, it would seem to me
calling pci_disable_device() on devices enabled with
pcim_enable_device() *should* be fine.
Changes from v1:
- Fixed missing
Replace devm_alloc_etherdev() with its devres version.
Signed-off-by: Moritz Fischer
---
drivers/net/ethernet/dec/tulip/de2104x.c | 7 ++-
1 file changed, 2 insertions(+), 5 deletions(-)
diff --git a/drivers/net/ethernet/dec/tulip/de2104x.c
b/drivers/net/ethernet/dec/tulip/de2104x.c
index
This series is the first bunch of minor cleanups for the de2104x driver
to make it look and behave more like a modern driver.
These changes replace some of the non-devres versions with devres
versions of functions to simplify the error paths.
Next up after this will be the ioremap part.
Changes
On Mon, Sep 14, 2020 at 11:17 PM Michal Hocko wrote:
>
> On Mon 14-09-20 23:02:15, Chunxin Zang wrote:
> > On Mon, Sep 14, 2020 at 9:47 PM Michal Hocko wrote:
> >
> > > On Mon 14-09-20 21:25:59, Chunxin Zang wrote:
> > > > On Mon, Sep 14, 2020 at 5:30 PM Michal Hocko wrote:
> > > >
> > > > >
Invoke ntb_link_enable() to enable the NTB/PCIe link on the local
or remote side of the bridge.
Signed-off-by: Kishon Vijay Abraham I
---
drivers/ntb/test/ntb_tool.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/ntb/test/ntb_tool.c b/drivers/ntb/test/ntb_tool.c
index
Add binding documentation for pci-ntb endpoint function that helps in
adding and configuring pci-ntb endpoint function.
Signed-off-by: Kishon Vijay Abraham I
---
.../PCI/endpoint/function/binding/pci-ntb.rst | 38 +++
Documentation/PCI/endpoint/index.rst | 1 +
2 files
In addition to the attributes that are generic across function drivers
documented in Documentation/PCI/endpoint/pci-endpoint-cfs.rst, there
could be function specific attributes that has to be exposed by the
function driver to be configured by the user. Add ->add_cfs()
in pci_epf_ops to be
Add documentation to help users use pci-epf-ntb function driver and
existing host side NTB infrastructure for NTB functionality.
Signed-off-by: Kishon Vijay Abraham I
---
Documentation/PCI/endpoint/index.rst | 1 +
Documentation/PCI/endpoint/pci-ntb-howto.rst | 160 +++
Implement ->msi_map_irq() ops in order to map physical address to
MSI address and return MSI data.
Signed-off-by: Kishon Vijay Abraham I
---
.../pci/controller/cadence/pcie-cadence-ep.c | 50 +++
drivers/pci/endpoint/pci-epc-core.c | 7 ++-
include/linux/pci-epc.h
Add support for EPF PCI-Express Non-Transparent Bridge (NTB) device.
This driver is platform independent and could be used by any platform
which have multiple PCIe endpoint instances configured using the
pci-epf-ntb driver. The driver connnects to the standard NTB sub-system
interface. The EPF NTB
On Mon, Sep 14, 2020 at 09:16:43AM -0700, Nick Desaulniers wrote:
> LLVM implemented a recent "libcall optimization" that lowers calls to
> `sprintf(dest, "%s", str)` where the return value is used to
> `stpcpy(dest, str) - dest`. This generally avoids the machinery involved
> in parsing format
Add TI J721E device to the pci id database. Since this device has
a configurable PCIe endpoint, it could be used with different
drivers.
Signed-off-by: Kishon Vijay Abraham I
---
drivers/misc/pci_endpoint_test.c | 1 -
include/linux/pci_ids.h | 1 +
2 files changed, 1 insertion(+), 1
Add pci_epc_ops to map physical address to MSI address and return MSI
data. The physical address is an address in the outbound region. This is
required to implement doorbell functionality of NTB (non transparent
bridge) wherein EPC on either side of the interface (primary and
secondary) can
Now that PCI endpoint core supports to add secondary endpoint
controller (EPC) with endpoint function (EPF), Add support in configfs
to associate two EPCs with EPF. This creates "primary" and "secondary"
directory inside the directory created by users for EPF device. Users
have to add a symlink of
Add a new endpoint function driver to provide NTB functionality
using multiple PCIe endpoint instances.
Signed-off-by: Kishon Vijay Abraham I
---
drivers/pci/endpoint/functions/Kconfig | 12 +
drivers/pci/endpoint/functions/Makefile |1 +
Documentation/PCI/endpoint/pci-endpoint-cfs.rst explains how a user
has to create a directory in-order to create a 'EPF Device' that
can be configured/probed by 'EPF Driver'.
Allow user to create a sub-directory of 'EPF Device' directory for
any function specific attributes that has to be exposed
Modify pci_epc_get_next_free_bar() and pci_epc_get_first_free_bar() to
return error values if there are no free BARs available.
Signed-off-by: Kishon Vijay Abraham I
---
drivers/pci/endpoint/functions/pci-epf-test.c | 2 ++
drivers/pci/endpoint/pci-epc-core.c | 12 ++--
This series is about implementing SW defined NTB using
multiple endpoint instances. This series has been tested using
2 endpoint instances in J7 connected to J7 board on one end and DRA7 board
on the other end. However there is nothing platform specific for the NTB
functionality.
This was
Add specification for the *PCI NTB* function device. The endpoint function
driver and the host PCI driver should be created based on this
specification.
Signed-off-by: Kishon Vijay Abraham I
---
Documentation/PCI/endpoint/index.rst | 1 +
.../PCI/endpoint/pci-ntb-function.rst
In the case of standard endpoint functions, only one endpoint
controller (EPC) will be associated with an endpoint function
(EPF). However for providing NTB (non transparent bridge)
functionality, two EPCs should be associated with a single EPF.
Add support to associate secondary EPC with EPF.
Add an API to get the next unreserved BAR starting from a given BAR
number that can be used by the endpoint function.
Signed-off-by: Kishon Vijay Abraham I
---
drivers/pci/endpoint/pci-epc-core.c | 26 ++
include/linux/pci-epc.h | 2 ++
2 files changed, 24
Remove unused pci_epf_match_device() function added in pci-epf-core.c
Signed-off-by: Kishon Vijay Abraham I
---
drivers/pci/endpoint/pci-epf-core.c | 16
include/linux/pci-epf.h | 2 --
2 files changed, 18 deletions(-)
diff --git
pci_epc_get_first_free_bar() uses only "reserved_bar" member in
epc_features to get the first unreserved BAR. However if the
reserved BAR is also a 64-bit BAR, then the next BAR shouldn't be
returned (since 64-bit BAR uses two BARs).
Make pci_epc_get_first_free_bar() take into account 64 bit BAR
Hi David,
On Tue, 15 Sep 2020 12:03:08 +0800 David Gow wrote:
>
> > drivers/mtd/nand/raw/gpmi-nand/gpmi-nand.c: In function
> > 'common_nfc_set_geometry':
> > drivers/mtd/nand/raw/gpmi-nand/gpmi-nand.c:514:3: warning: initialization
> > discards 'const' qualifier from pointer target type
[+kasan-dev, +kunit-dev]
On Mon, Sep 14, 2020 at 3:01 PM Stephen Rothwell wrote:
>
> Hi all,
>
> After merging the akpm-current tree, today's linux-next build (x86_64
> allmodconfig) produced this warning:
>
> In file included from lib/test_kasan_module.c:16:
> lib/../mm/kasan/kasan.h:232:6:
From: Patricia Alfonso
Integrate KASAN into KUnit testing framework.
- Fail tests when KASAN reports an error that is not expected
- Use KUNIT_EXPECT_KASAN_FAIL to expect a KASAN error in KASAN
tests
- Expected KASAN reports pass tests and are still printed when
On Tue, Sep 15, 2020 at 11:27:52AM +0800, Xu Yilun wrote:
> The description of feature_id in struct dfl_device is not accurate. In
> DFL specification the feature_id is the 12 bits field. The description
> in struct dfl_device_id is more clear so we make them aligned. We also
> made the similar
On Tue, Sep 15, 2020 at 11:27:51AM +0800, Xu Yilun wrote:
> Device Feature List (DFL) is a linked list of feature headers within the
> device MMIO space. It is used by FPGA to enumerate multiple sub features
> within it. Each feature can be uniquely identified by DFL type and
> feature id, which
From: Patricia Alfonso
Transfer all previous tests for KASAN to KUnit so they can be run
more easily. Using kunit_tool, developers can run these tests with their
other KUnit tests and see "pass" or "fail" with the appropriate KASAN
report instead of needing to parse each KASAN report to test
On Tue, Sep 15, 2020 at 11:27:50AM +0800, Xu Yilun wrote:
> In order to support MODULE_DEVICE_TABLE() for dfl device driver, this
> patch moves struct dfl_device_id to mod_devicetable.h
>
> Signed-off-by: Xu Yilun
> Signed-off-by: Wu Hao
> Signed-off-by: Matthew Gerlach
> Signed-off-by: Russ
This patchset contains everything needed to integrate KASAN and KUnit.
KUnit will be able to:
(1) Fail tests when an unexpected KASAN error occurs
(2) Pass tests when an expected KASAN error occurs
Convert KASAN tests to KUnit with the exception of copy_user_test
because KUnit is unable to test
KASAN errors will currently trigger a panic when panic_on_warn is set.
This renders kasan_multishot useless, as further KASAN errors won't be
reported if the kernel has already paniced. By making kasan_multishot
disable this behaviour for KASAN errors, we can still have the benefits
of
From: Patricia Alfonso
In order to integrate debugging tools like KASAN into the KUnit
framework, add KUnit struct to the current task to keep track of the
current KUnit test.
Signed-off-by: Patricia Alfonso
Reviewed-by: Brendan Higgins
Tested-by: Andrey Konovalov
Signed-off-by: David Gow
From: Patricia Alfonso
Include documentation on how to test KASAN using CONFIG_TEST_KASAN_KUNIT
and CONFIG_TEST_KASAN_MODULE.
Signed-off-by: Patricia Alfonso
Signed-off-by: David Gow
Reviewed-by: Andrey Konovalov
Reviewed-by: Dmitry Vyukov
Acked-by: Brendan Higgins
Tested-by: Andrey
Palmer Dabbelt 於 2020年8月5日 週三 上午10:03寫道：
>
> On Mon, 03 Aug 2020 20:29:32 PDT (-0700), a...@brainfault.org wrote:
> > On Tue, Aug 4, 2020 at 8:32 AM Greentime Hu wrote:
> >>
> >> This patch addes local_flush_tlb_page(addr) to use sfence.vma after the
> >
> > s/addes/adds
> >
> >> page table
This patch is the effect of commit hashes:
50145474f6ef4a9c19205b173da6264a644c7489 and
973c096f6a85e5b5f2a295126ba6928d9a6afd45
fbcon: remove soft scrollback code
And adjusted the numbering for boot options too.
Signed-off-by: Bhaskar Chowdhury
---
Documentation/fb/fbcon.rst | 21
This patch implements the basic functions of the BMC chip for some Intel
FPGA PCIe Acceleration Cards (PAC). The BMC is implemented using the
Intel MAX 10 CPLD.
This BMC chip is connected to the FPGA by a SPI bus. To provide direct
register access from the FPGA, the "SPI slave to Avalon Master
Hi all,
On Wed, 9 Sep 2020 10:06:20 -0600 Rob Herring wrote:
>
> On Tue, Sep 8, 2020 at 8:37 PM Stephen Rothwell wrote:
> >
> > After merging the pci tree, today's linux-next build (arm
> > multi_v7_defconfig) produced this warning:
>
> Uggg. I guess 0-day just doesn't do arm32 builds
On Tue, Sep 15, 2020 at 12:25 PM Bjorn Andersson
wrote:
>
> On Tue 15 Sep 01:29 UTC 2020, Alexandre Courbot wrote:
>
> > This will improve this driver's build coverage.
> >
> > Reported-by: Ezequiel Garcia
> > Signed-off-by: Alexandre Courbot
> > ---
> > Hi remoteproc maintainers,
> >
> >
Hi All,
On Wed, 9 Sep 2020 12:38:43 +1000 Stephen Rothwell
wrote:
>
> After merging the pci tree, today's linux-next build (arm
> multi_v7_defconfig) produced this warning:
>
> WARNING: modpost: "dw_pcie_link_set_max_speed" [vmlinux] is a static
> EXPORT_SYMBOL_GPL
>
> Introduced by commit
>
On Tue, Sep 15, 2020 at 03:18:23AM +, Zhang, Qiang wrote:
>
>
>
> 发件人: Paul E. McKenney
> 发送时间: 2020年9月15日 4:56
> 收件人: Joel Fernandes
> 抄送: Zhang, Qiang; Uladzislau Rezki; j...@joshtriplett.org;
> rost...@goodmis.org; mathieu.desnoy...@efficios.com;
Hi Rob,
Thanks a lot for your review and ack!
Regards,
Zhiqiang
> -Original Message-
> From: Rob Herring
> Sent: 2020年9月15日 9:31
> To: Z.q. Hou
> Cc: linux-...@vger.kernel.org; linux-kernel@vger.kernel.org; M.h. Lian
> ; devicet...@vger.kernel.org;
> gustavo.pimen...@synopsys.com;
Hi Rob,
Thanks a lot for your review and ack!
Regards,
Zhiqiang
> -Original Message-
> From: Rob Herring
> Sent: 2020年9月15日 9:31
> To: Z.q. Hou
> Cc: bhelg...@google.com; linux-kernel@vger.kernel.org;
> shawn...@kernel.org; Leo Li ;
> linux-...@vger.kernel.org; M.h. Lian ;
>
Hi Rob,
Thanks a lot for your review!
Regards,
Zhiqiang
> -Original Message-
> From: Rob Herring
> Sent: 2020年9月15日 9:16
> To: Z.q. Hou
> Cc: linux-...@vger.kernel.org; devicet...@vger.kernel.org;
> linux-kernel@vger.kernel.org; bhelg...@google.com;
> shawn...@kernel.org; Leo Li ;
>
The description of feature_id in struct dfl_device is not accurate. In
DFL specification the feature_id is the 12 bits field. The description
in struct dfl_device_id is more clear so we make them aligned. We also
made the similar fix for the type field.
Signed-off-by: Xu Yilun
---
The patch moves dfl-bus related APIs to include/linux/fpga/dfl.h
Now the DFL device drivers could be made as independent modules and put
in different folders according to their functionality. In order for
scattered DFL device drivers to include dfl bus APIs, move the dfl bus
APIs to a new header
Device Feature List (DFL) is a linked list of feature headers within the
device MMIO space. It is used by FPGA to enumerate multiple sub features
within it. Each feature can be uniquely identified by DFL type and
feature id, which can be read out from feature headers.
A dfl bus helps DFL
In order to support MODULE_DEVICE_TABLE() for dfl device driver, this
patch moves struct dfl_device_id to mod_devicetable.h
Signed-off-by: Xu Yilun
Signed-off-by: Wu Hao
Signed-off-by: Matthew Gerlach
Signed-off-by: Russ Weight
Reviewed-by: Tom Rix
Acked-by: Wu Hao
---
v2: fix the order for
Patch #1 and #2 add dfl bus support to MODULE_DEVICE_TABLE(), so that
dfl driver modules could be auto-loaded when dfl devices are added.
Patch #3 is a fix of the description of fields in struct dfl_device.
Patch #4 moves the dfl bus APIs to a new header file in the public
folder so that
I trimmed the cc as the mailing lists appear to be blocking this
email because of it.
On Mon, Sep 14, 2020 at 03:37:49PM -0700, Linus Torvalds wrote:
>
> So it _looks_ like this code started using kmap() - probably back when
> kmap_atomic() was so cumbersome to use - and was then converted
>
On Thu, Sep 14, 2020 at 22:36, Rob Herring wrote:
> -Original Message-
> From: Rob Herring
> Sent: 2020年9月14日 22:36
> To: Qiang Zhao
> Cc: a.zu...@towertech.it; alexandre.bell...@bootlin.com;
> linux-...@vger.kernel.org; devicet...@vger.kernel.org;
> linux-kernel@vger.kernel.org
>
On Tue 15 Sep 01:29 UTC 2020, Alexandre Courbot wrote:
> This will improve this driver's build coverage.
>
> Reported-by: Ezequiel Garcia
> Signed-off-by: Alexandre Courbot
> ---
> Hi remoteproc maintainers,
>
> Second resend as I got no reaction for almost 1 month on this one-liner.
Sorry
Excerpts from David Miller's message of September 15, 2020 5:59 am:
> From: Nicholas Piggin
> Date: Mon, 14 Sep 2020 14:52:18 +1000
>
> ...
>> The basic fix for sparc64 is to remove its mm_cpumask clearing code. The
>> optimisation could be effectively restored by sending IPIs to mm_cpumask
>>
The aliases were never released causing the following leaks:
Indirect leak of 1224 byte(s) in 9 object(s) allocated from:
#0 0x7feefb830628 in malloc (/lib/x86_64-linux-gnu/libasan.so.5+0x107628)
#1 0x56332c8f1b62 in __perf_pmu__new_alias util/pmu.c:322
#2 0x56332c8f401f in
The following leaks were detected by ASAN:
Indirect leak of 360 byte(s) in 9 object(s) allocated from:
#0 0x7fecc305180e in calloc (/lib/x86_64-linux-gnu/libasan.so.5+0x10780e)
#1 0x560578f6dce5 in perf_pmu__new_format util/pmu.c:1333
#2 0x560578f752fc in perf_pmu_parse
The test_generic_metric() missed to release entries in the pctx.
Asan reported following leak (and more):
Direct leak of 128 byte(s) in 1 object(s) allocated from:
#0 0x7f4c9396980e in calloc (/lib/x86_64-linux-gnu/libasan.so.5+0x10780e)
#1 0x55f7e748cc14 in hashmap_grow
The metricgroup__add_metric() can find multiple match for a metric
group and it's possible to fail. Also it can fail in the middle like
in resolve_metric() even for single metric.
In those cases, the intermediate list and ids will be leaked like:
Direct leak of 3 byte(s) in 1 object(s)
The evsel->unit borrows a pointer of pmu event or alias instead of
owns a string. But tool event (duration_time) passes a result of
strdup() caused a leak.
It was found by ASAN during metric test:
Direct leak of 210 byte(s) in 70 object(s) allocated from:
#0 0x7fe366fca0b5 in strdup
It's dangerous to free the original metric when it's called from
resolve_metric() as it's already in the metric_list and might have
other resources too. Instead, it'd better let them bail out and be
released properly at the later stage.
So add a check when it's called from
发件人: Paul E. McKenney
发送时间: 2020年9月15日 4:56
收件人: Joel Fernandes
抄送: Zhang, Qiang; Uladzislau Rezki; j...@joshtriplett.org; rost...@goodmis.org;
mathieu.desnoy...@efficios.com; Lai Jiangshan; r...@vger.kernel.org; LKML
主题: Re: RCU: Question on
Like evlist cpu map, evsel's cpu map should have proper refcount by
releasing the original count after creation.
This fixes the following ASAN report:
Direct leak of 840 byte(s) in 70 object(s) allocated from:
#0 0x7fe36703f628 in malloc (/lib/x86_64-linux-gnu/libasan.so.5+0x107628)
#1
1 - 100 of 1601 matches
Mail list logo
