On Fri, Mar 12, 2021 at 12:43:31PM +, Matthew Wilcox wrote:
> On Wed, Mar 10, 2021 at 10:46:15AM +, Mel Gorman wrote:
> > +int __alloc_pages_bulk_nodemask(gfp_t gfp_mask, int preferred_nid,
> > + nodemask_t *nodemask, int nr_pages,
> > + s
LOTTO.NL,
2391 Beds 152 Koningin Julianaplein 21,
Den Haag-Netherlands.
(Lotto affiliate with Subscriber Agents).
From: Susan Console
(Lottery Coordinator)
Website: www.lotto.nl
Sir/Madam,
CONGRATULATIONS!!!
We are pleased to inform you of the result of the Lotto NL Winners
International progr
There are a couple of issues in qat error handling. Those drivers tries to
release resources that is not initialized. This patch series tries to fix
crashes caused by incorrect error handling.
v2: removed excessive dump in commit log
Tong Zhang (2):
crypto: qat - dont release uninitialized reso
ADF_STATUS_PF_RUNNING is (only) used and checked by adf_vf2pf_shutdown()
before calling adf_iov_putmsg()->mutex_lock(vf2pf_lock), however the
vf2pf_lock is initialized in adf_dev_init(), which can fail and when it
fail, the vf2pf_lock is either not initialized or destroyed, a subsequent
use of vf2
adf_vf_isr_resource_alloc() is not unwinding correctly when error
happens and it trys to release uninitialized resources.
To fix this, only release initialized resources.
[1.792845] Trying to free already-free IRQ 11
[1.793091] WARNING: CPU: 0 PID: 182 at kernel/irq/manage.c:1821
free_irq
On Tue, Mar 02, 2021 at 08:57:51PM +0800, Yanan Wang wrote:
> This test serves as a performance tester and a bug reproducer for
> kvm page table code (GPA->HPA mappings), so it gives guidance for
> people trying to make some improvement for kvm.
>
> The function guest_code() can cover the conditio
Hi Andy, Thanks for the suggestion.
I have removed excessive lines in the commit log and sent out a v2 patch.
Thanks again.
- Tong
On Fri, Mar 12, 2021 at 3:56 AM Andy Shevchenko
wrote:
>
> On Fri, Mar 12, 2021 at 9:50 AM Tong Zhang wrote:
> >
> > ADF_STATUS_PF_RUNNING is (only) used and checked
MTE provides an asynchronous mode for detecting tag exceptions. In
particular instead of triggering a fault the arm64 core updates a
register which is checked by the kernel after the asynchronous tag
check fault has occurred.
Add support for MTE asynchronous mode.
The exception handling mechanism
This patchset implements the asynchronous mode support for ARMv8.5-A
Memory Tagging Extension (MTE), which is a debugging feature that allows
to detect with the help of the architecture the C and C++ programmatic
memory errors like buffer overflow, use-after-free, use-after-return, etc.
MTE is bui
Commit a23c4134955e added the clock controller nodes, incorrectly changing the
syscon reboot nodes addresses.
- Fix syscon reboot nodes addresses (commit a23c4134955e added the clock
controller nodes, incorrectly changing the syscon reboot nodes addresses).
- Rename periph_cntl to pll_cntl and tim
KASAN provides an asynchronous mode of execution.
Add reporting functionality for this mode.
Cc: Dmitry Vyukov
Cc: Andrey Ryabinin
Cc: Alexander Potapenko
Cc: Andrey Konovalov
Reviewed-by: Andrey Konovalov
Signed-off-by: Vincenzo Frascino
Signed-off-by: Andrey Konovalov
---
include/linux/
load_unaligned_zeropad() and __get/put_kernel_nofault() functions can
read past some buffer limits which may include some MTE granule with a
different tag.
When MTE async mode is enabled, the load operation crosses the boundaries
and the next granule has a different tag the PE sets the TFSR_EL1.TF
MTE provides a mode that asynchronously updates the TFSR_EL1 register
when a tag check exception is detected.
To take advantage of this mode the kernel has to verify the status of
the register at:
1. Context switching
2. Return to user/EL0 (Not required in entry from EL0 since the kernel
did
When MTE async mode is enabled TFSR_EL1 contains the accumulative
asynchronous tag check faults for EL1 and EL0.
During the suspend/resume operations the firmware might perform some
operations that could change the state of the register resulting in
a spurious tag check fault report.
Report async
From: Andrey Konovalov
This change adds KASAN-KUnit tests support for the async HW_TAGS mode.
In async mode, tag fault aren't being generated synchronously when a
bad access happens, but are instead explicitly checked for by the kernel.
As each KASAN-KUnit test expect a fault to happen before t
arch_enable_tagging() was left in memory.h after the introduction of
async mode to not break the bysectability of the KASAN KUNIT tests.
Remove the function now that KASAN has been fully converted.
Cc: Catalin Marinas
Cc: Will Deacon
Acked-by: Catalin Marinas
Signed-off-by: Vincenzo Frascino
Architectures supported by KASAN_HW_TAGS can provide a sync or async mode
of execution. On an MTE enabled arm64 hw for example this can be identified
with the synchronous or asynchronous tagging mode of execution.
In synchronous mode, an exception is triggered if a tag check fault occurs.
In asynch
On Fri, Mar 12, 2021 at 11:46:27AM +0100, Dmitry Vyukov wrote:
> On Fri, Mar 12, 2021 at 11:26 AM syzbot
> wrote:
> >
> > Hello,
> >
> > syzbot found the following issue on:
> >
> > HEAD commit:f78d76e7 Merge tag 'drm-fixes-2021-03-12-1' of git://anong..
> > git tree: upstream
> > consol
On 3/12/21 12:06 PM, He Ying wrote:
> The variable 'uaccess_fulsh' is not referenced outside the file. Perhaps we
> should define it as static to avoid the warning as follows:
>
> arch/powerpc/kernel/setup_64.c:953:6: warning: symbol 'uaccess_flush'
> was not declared. Should it be static?
>
> Re
On Fri, 12 Mar 2021 02:12:05 +0300, Dmitry Osipenko wrote:
> All NVIDIA Tegra SoCs have a core power domain where majority of hardware
> blocks reside. Add binding for the core power domain.
>
> Signed-off-by: Dmitry Osipenko
> ---
> .../power/nvidia,tegra20-core-domain.yaml | 52 +++
On Fri, 12 Mar 2021 11:27:12 +0100, Martin Devera wrote:
> Add new rx-tx-swap property to allow for RX & TX pin swapping.
>
> Signed-off-by: Martin Devera
> Acked-by: Fabrice Gasnier
> ---
> v6:
> - add version changelog
> v5:
> - yaml fixes based on Rob Herring comments
> - add serial.y
On Fri, Mar 12, 2021 at 02:37:30PM +0200, Daniel Baluta wrote:
> On Fri, Mar 12, 2021 at 1:59 PM Mark Brown wrote:
> > No, just the opposite! If there's an explict name configured why do you
> > want to ignore it?
> Because the initial assignment:
> dai_link->platforms->name = component->name;
Em Thu, Mar 11, 2021 at 06:02:57PM -0800, Song Liu escreveu:
> perf uses performance monitoring counters (PMCs) to monitor system
> performance. The PMCs are limited hardware resources. For example,
> Intel CPUs have 3x fixed PMCs and 4x programmable PMCs per cpu.
>
> Modern data center systems us
Update KASAN documentation:
- Give some sections clearer names.
- Remove unneeded subsections in the "Tests" section.
- Move the "For developers" section and split into subsections.
Signed-off-by: Andrey Konovalov
---
Changes v1->v2:
- Rename "By default" section to "Default behaviour".
---
D
Update the "Overview" section in KASAN documentation:
- Outline main use cases for each mode.
- Mention that HW_TAGS mode need compiler support too.
- Move the part about SLUB/SLAB support from "Usage" to "Overview".
- Punctuation, readability, and other minor clean-ups.
Signed-off-by: Andrey Kon
Update the "Boot parameters" section in KASAN documentation:
- Mention panic_on_warn.
- Mention kasan_multi_shot and its interaction with panic_on_warn.
- Clarify kasan.fault=panic interaction with panic_on_warn.
- A readability clean-up.
Signed-off-by: Andrey Konovalov
---
Documentation/dev-to
Update the "Usage" section in KASAN documentation:
- Add inline code snippet markers.
- Reword the part about stack traces for clarity.
- Other minor clean-ups.
Signed-off-by: Andrey Konovalov
---
Documentation/dev-tools/kasan.rst | 23 +++
1 file changed, 11 insertions(+),
Update the "Error reports" section in KASAN documentation:
- Mention that bug titles are best-effort.
- Move and reword the part about auxiliary stacks from
"Implementation details".
- Punctuation, readability, and other minor clean-ups.
Signed-off-by: Andrey Konovalov
---
Documentation/dev-t
Update the "Implementation details" section for generic KASAN:
- Don't mention kmemcheck, it's not present in the kernel anymore.
- Don't mention GCC as the only supported compiler.
- Update kasan_mem_to_shadow() definition to match actual code.
- Punctuation, readability, and other minor clean-up
Update the "Implementation details" section for SW_TAGS KASAN:
- Clarify the introduction sentence.
- Punctuation, readability, and other minor clean-ups.
Signed-off-by: Andrey Konovalov
---
Documentation/dev-tools/kasan.rst | 39 +++
1 file changed, 19 insertions(+)
Update the "Ignoring accesses" section in KASAN documentation:
- Mention __no_sanitize_address/noinstr.
- Mention kasan_disable/enable_current().
- Mention kasan_reset_tag()/page_kasan_tag_reset().
- Readability and punctuation clean-ups.
Signed-off-by: Andrey Konovalov
---
Changes in v1->v2:
Update the "Shadow memory" section in KASAN documentation:
- Rearrange the introduction paragraph do it doesn't give a
"KASAN has an issue" impression.
- Update the list of architectures with vmalloc support.
- Punctuation, readability, and other minor clean-ups.
Signed-off-by: Andrey Konovalov
Update the "Implementation details" section for HW_TAGS KASAN:
- Punctuation, readability, and other minor clean-ups.
Signed-off-by: Andrey Konovalov
---
Documentation/dev-tools/kasan.rst | 26 +-
1 file changed, 13 insertions(+), 13 deletions(-)
diff --git a/Documentat
Update the "Tests" section in KASAN documentation:
- Add an introductory sentence.
- Add proper indentation for the list of ways to run KUnit tests.
- Punctuation, readability, and other minor clean-ups.
Signed-off-by: Andrey Konovalov
---
Changes v1->v2:
- Fix missing snippet delimeter around
On 3/12/21 3:24 AM, Luo Jiaxing wrote:
> From: Xingui Yang
>
> On Hisilicon Kunpeng920, ESP is set to 1 by default for all ports of
> SATA controller. In some scenarios, some ports are not external SATA ports,
> and it cause disks connected to these ports to be identified as removable
> disks. So
On 3/12/21 1:57 AM, Bhaskar Chowdhury wrote:
>
> Trivial spelling fixes.
Applied, thanks.
--
Jens Axboe
On Thu, Mar 11, 2021 at 07:03:54AM -0800, Lv Yunlong wrote:
> In the implementation of usbtmc_free_int(), it already calls
> kref_put() to free the data as shown below. So, in
> usbtmc_disconnect, call an extra kref_put() is redundant.
>
> """
> static void usbtmc_free_int(struct usbtmc_device_dat
On Fri, Mar 12, 2021 at 1:00 PM Peter Zijlstra wrote:
>
> Hi!
>
> A while ago Steve complained about x86 being weird for having different NOPs
> [1]
>
> Having cursed the same thing before, I figured it was time to look at the NOP
> situation.
>
> 32bit simply isn't a performance target anymore,
On Thu, Mar 11, 2021 at 6:45 AM Andrew Morton wrote:
>
> On Thu, 11 Mar 2021 09:32:45 +0800 Walter Wu
> wrote:
>
> >
> > Hi Andrew,
> >
> > I see my v4 patch is different in the next tree now. please see below
> > information.
> > https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.g
On Fri, 2021-03-12 at 10:55 +0100, Johannes Berg wrote:
> CONFIG_GCOV is fairly useful for ARCH=um (e.g. with kunit, though
> my main use case is a bit different) since it writes coverage data
> directly out like a normal userspace binary. Theoretically, that
> is.
>
> Unfortunately, it's broken i
On Fri, Mar 12, 2021 at 6:59 AM Jiri Olsa wrote:
>
> On Wed, Mar 10, 2021 at 05:08:31PM -0700, Rob Herring wrote:
>
> SNIP
>
> > +
> > static int
> > sys_perf_event_open(struct perf_event_attr *attr,
> > pid_t pid, int cpu, int group_fd,
> > @@ -137,6 +147,8 @@ void perf_evsel_
As you can see, if we're doing like the below.
sbi->compr_written_block += blocks;
Let's assume the initial value as 0.
sbi->compr_written_block = 0;
sbi->compr_written_block = 0;
+blocks(3);
On Sun, Mar 07, 2021 at 08:58:39PM +0300, Arseny Krasnov wrote:
This prepares af_vsock.c for SEQPACKET support: some functions such
as setsockopt(), getsockopt(), connect(), recvmsg(), sendmsg() are
shared between both types of sockets, so rename them in general
manner.
Signed-off-by: Arseny Kra
LOTTO.NL,
2391 Beds 152 Koningin Julianaplein 21,
Den Haag-Netherlands.
(Lotto affiliate with Subscriber Agents).
From: Susan Console
(Lottery Coordinator)
Website: www.lotto.nl
Sir/Madam,
CONGRATULATIONS!!!
We are pleased to inform you of the result of the Lotto NL Winners
International progr
On Sun, Mar 07, 2021 at 08:59:01PM +0300, Arseny Krasnov wrote:
This moves wait loop for data to dedicated function, because later it
will be used by SEQPACKET data receive loop. While moving the code
around, let's update an old comment.
Signed-off-by: Arseny Krasnov
---
net/vmw_vsock/af_vsock.
So, do you want we protect the values here with spin_lock and just
read without spin_lock in sysfs read part?
2021년 3월 12일 (금) 오후 11:37, Daeho Jeong 님이 작성:
>
> As you can see, if we're doing like the below.
>
> sbi->compr_written_block += blocks;
>
> Let's assume the initial value as 0.
>
>
On 10/03/2021 19:39, Pierre-Louis Bossart wrote:
> When DMI information is not present, trying to assign the card long
> name results in the following warning.
>
> WARNING KERN tegra-audio-graph-card sound: ASoC: no DMI vendor name!
>
> The initial solution suggested was to test if the card dev
On Fri, 12 Mar 2021 at 15:10, Sebastian Andrzej Siewior
wrote:
>
> CHARGER_MAX8997 fails to compile without CONFIG_EXTCON. There are stubs
> already present for *extcon_*_notifier() but are missing for the _all()
> variant.
>
> Add *extcon_*_notifier_all() stubs for !CONFIG_EXTCON.
>
> Fixes: f384
A: http://en.wikipedia.org/wiki/Top_post
Q: Were do I find info about this thing called top-posting?
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?
A: No.
Q: Should I includ
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: f78d76e72a4671ea52d12752d92077788b4f5d50
commit: 4ef873226ceb9c7bf11a922caddc5698a24bcfaf mm: introduce
fault_signal_pending()
date: 11 months ago
config: mips-randconfig-r033-20210312 (attached as
On Fri, Mar 12, 2021 at 03:29:48PM +0100, Sedat Dilek wrote:
> What does this change exactly mean to/for me?
Probably nothing.
I would be very surprised if it would be at all noticeable for you -
it's not like the kernel is executing long streams of NOPs in fast
paths.
--
Regards/Gruss,
Bor
> -原始邮件-
> 发件人: "Tom Parkin"
> 发送时间: 2021-03-12 18:12:58 (星期五)
> 收件人: lyl2...@mail.ustc.edu.cn
> 抄送: pau...@samba.org, da...@davemloft.net, linux-...@vger.kernel.org,
> net...@vger.kernel.org, linux-kernel@vger.kernel.org
> 主题: Re: [BUG] net/ppp: A use after free in ppp_unregister_chan
On Fri, Mar 12, 2021 at 11:42:04PM +0900, Daeho Jeong wrote:
> So, do you want we protect the values here with spin_lock and just
> read without spin_lock in sysfs read part?
I would not use any lock at all if this were my code. Remember, this is
for debugging/information only, right? And the da
On Fri, Mar 12, 2021 at 01:38:14PM +0100, Uladzislau Rezki wrote:
> Hello, Paul.
>
> Please do not consider this patch. It is buggy :)
Consider it formally withdrawn, and thank you for letting me know!
Thanx, Paul
> --
> Vlad Rezki
>
> On
On Fri, Mar 12, 2021 at 3:22 PM Vincenzo Frascino
wrote:
>
> From: Andrey Konovalov
>
> This change adds KASAN-KUnit tests support for the async HW_TAGS mode.
>
> In async mode, tag fault aren't being generated synchronously when a
> bad access happens, but are instead explicitly checked for by t
On Fri, Mar 12, 2021 at 3:22 PM Vincenzo Frascino
wrote:
>
> This patchset implements the asynchronous mode support for ARMv8.5-A
> Memory Tagging Extension (MTE), which is a debugging feature that allows
> to detect with the help of the architecture the C and C++ programmatic
> memory errors like
LOTTO.NL,
2391 Beds 152 Koningin Julianaplein 21,
Den Haag-Netherlands.
(Lotto affiliate with Subscriber Agents).
From: Susan Console
(Lottery Coordinator)
Website: www.lotto.nl
Sir/Madam,
CONGRATULATIONS!!!
We are pleased to inform you of the result of the Lotto NL Winners
International progr
On 2021-03-12 15:45:48 [+0100], Krzysztof Kozlowski wrote:
> Did you base your work on next?
no, -rc2.
> Best regards,
> Krzysztof
Sebastian
On 12/03/2021 15:53, Sebastian Andrzej Siewior wrote:
> On 2021-03-12 15:45:48 [+0100], Krzysztof Kozlowski wrote:
>> Did you base your work on next?
>
> no, -rc2.
Yeah, it missed the merge window...
Best regards,
Krzysztof
On Thu, Mar 11, 2021 at 02:55:34PM -0800, Jacob Pan wrote:
> Hi Jason,
>
> Thanks for the review.
>
> On Wed, 10 Mar 2021 15:23:01 -0400, Jason Gunthorpe wrote:
>
> > On Sat, Feb 27, 2021 at 02:01:26PM -0800, Jacob Pan wrote:
> >
> > > +/* IOCTLs for IOASID file descriptor (/dev/ioasi
On 3/11/21 11:36 PM, Dominique MARTINET wrote:
> Hi,
>
> Guenter Roeck wrote on Thu, Sep 17, 2020 at 07:16:17PM -0700:
>> On 9/17/20 5:47 AM, Laurent Pinchart wrote:
>>> On Wed, Sep 16, 2020 at 07:25:42PM -0700, Guenter Roeck wrote:
Something seems to have gone wrong with v3 of this patch ser
On Fri, Mar 12, 2021 at 4:08 AM Lee Jones wrote:
>
> Fixes the following W=1 kernel build warning(s):
>
> drivers/of/device.c:72: warning: expecting prototype for of_dma_configure().
> Prototype was for of_dma_configure_id() instead
> drivers/of/device.c:263: warning: Function parameter or memb
On 2021-03-12 15:53:53 [+0100], Krzysztof Kozlowski wrote:
> Yeah, it missed the merge window...
Could you please send it for -rc3?
> Best regards,
> Krzysztof
Sebastian
From: Matthias Brugger
Having a separate compatible for the regulator node is redundant and not
needed. Delete the corresponding requierement.
Signed-off-by: Matthias Brugger
---
Documentation/devicetree/bindings/mfd/mt6397.txt | 3 ---
1 file changed, 3 deletions(-)
diff --git a/Documentati
From: Matthias Brugger
The regulator does not need to have a device tree compatible, if it's
part of an MFD. We leave the node name to the SoC specific name (e.g.
mt6323regulator) to allow older kernels to work with the new binding.
Signed-off-by: Matthias Brugger
---
.../bindings/regulator/mt
From: Matthias Brugger
For regulators a compatible string is superfluous. Drop the string.
Signed-off-by: Matthias Brugger
---
drivers/mfd/mt6397-core.c | 3 ---
1 file changed, 3 deletions(-)
diff --git a/drivers/mfd/mt6397-core.c b/drivers/mfd/mt6397-core.c
index 7518d74c3b4c3..13037f4bc54e
On 3/12/21 2:49 PM, Andrey Konovalov wrote:
> On Fri, Mar 12, 2021 at 3:22 PM Vincenzo Frascino
> wrote:
>>
>> From: Andrey Konovalov
>>
>> This change adds KASAN-KUnit tests support for the async HW_TAGS mode.
>>
>> In async mode, tag fault aren't being generated synchronously when a
>> bad a
From: Matthias Brugger
The regulator framework does not need compatible, it's acutall
superfluous. Drop it from the DT.
Signed-off-by: Matthias Brugger
---
arch/arm/boot/dts/mt6323.dtsi | 4 +---
1 file changed, 1 insertion(+), 3 deletions(-)
diff --git a/arch/arm/boot/dts/mt6323.dtsi b/arch/
From: Matthias Brugger
Define the regulator node under which the regulators are described.
Signed-off-by: Matthias Brugger
---
drivers/regulator/mt6323-regulator.c | 3 +++
drivers/regulator/mt6358-regulator.c | 4
drivers/regulator/mt6397-regulator.c | 10 +++---
3 files changed, 1
From: Matthias Brugger
The regulator framework does not need compatible, it's actually
superfluous. Drop it from the DT.
Signed-off-by: Matthias Brugger
Series-to: lee.jo...@linaro.org
Series-to: robh...@kernel.org
Series-to: matthias@gmail.com
Series-to: lgirdw...@gmail.com
Series-to: bro
From: Matthias Brugger
The regulator framework does not need compatible, it's actually
superfluous. Drop it from the DT.
Signed-off-by: Matthias Brugger
---
arch/arm64/boot/dts/mediatek/mt6358.dtsi | 4 +---
1 file changed, 1 insertion(+), 3 deletions(-)
diff --git a/arch/arm64/boot/dts/media
On 3/12/21 2:50 PM, Andrey Konovalov wrote:
> On Fri, Mar 12, 2021 at 3:22 PM Vincenzo Frascino
> wrote:
>>
>> This patchset implements the asynchronous mode support for ARMv8.5-A
>> Memory Tagging Extension (MTE), which is a debugging feature that allows
>> to detect with the help of the archi
On Fri, Mar 12, 2021 at 12:46:09PM +0100, Jesper Dangaard Brouer wrote:
> In my page_pool patch I'm bulk allocating 64 pages. I wanted to ask if
> this is too much? (PP_ALLOC_CACHE_REFILL=64).
>
> The mlx5 driver have a while loop for allocation 64 pages, which it
> used in this case, that is why
On 3/12/21 3:23 PM, Rob Herring wrote:
On Fri, 12 Mar 2021 11:27:12 +0100, Martin Devera wrote:
Add new rx-tx-swap property to allow for RX & TX pin swapping.
Signed-off-by: Martin Devera
Acked-by: Fabrice Gasnier
---
v6:
- add version changelog
v5:
- yaml fixes based on Rob Herring com
On 3/12/21 3:32 PM, Michael Walle wrote:
> EXTERNAL EMAIL: Do not click links or open attachments unless you know the
> content is safe
>
> Am 2021-03-11 20:12, schrieb Pratyush Yadav:
>> The main problem here is telling the controller where to find the
>> pattern and how to read it. This RFC use
On Sun, Mar 07, 2021 at 08:59:45PM +0300, Arseny Krasnov wrote:
This adds receive loop for SEQPACKET. It looks like receive loop for
STREAM, but there is a little bit difference:
1) It doesn't call notify callbacks.
2) It doesn't care about 'SO_SNDLOWAT' and 'SO_RCVLOWAT' values, because
there
On Fri, Mar 12, 2021 at 4:08 AM Lee Jones wrote:
>
> Fixes the following W=1 kernel build warning(s):
>
> drivers/of/fdt.c:478: warning: Function parameter or member 'node' not
> described in '__reserved_mem_reserve_reg'
> drivers/of/fdt.c:478: warning: Function parameter or member 'uname' not
On Sun, Mar 07, 2021 at 07:28:30PM +, Paul Cercueil wrote:
> The NT39016 panel is a fun beast, even though the documentation states
> that the CS line is active-low, it will work just fine if the CS line is
> configured as active-high, but it won't work if the CS line is forced
> low or forced
On Sun, Mar 07, 2021 at 07:28:29PM +, Paul Cercueil wrote:
> The NT39016 panel is a fun beast, even though the documentation states
> that the CS line is active-low, it will work just fine if the CS line is
> configured as active-high, but it won't work if the CS line is forced
> low or forced
On Mon, Mar 08, 2021 at 10:03:15AM +0100, Rafał Miłecki wrote:
> From: Rafał Miłecki
>
> This patchset refactors driver part finding and reading NVRAM.
>
> It been tested on BCM4706. Updated code checks the same offsets as
> before. Driver still finds & copies NVRAM content.
>
> It's a new patc
On 3/12/21 3:56 PM, Martin DEVERA wrote:
On 3/12/21 3:23 PM, Rob Herring wrote:
On Fri, 12 Mar 2021 11:27:12 +0100, Martin Devera wrote:
Add new rx-tx-swap property to allow for RX & TX pin swapping.
Signed-off-by: Martin Devera
Acked-by: Fabrice Gasnier
---
v6:
- add version changelog
v5
Hi Hassan Shahbazi,
I also tested your patch locally with qemu, but it did not fix the crashing.
I sent test command to syzbot on upstream linux and am waiting for result.
Regards,
Du Cheng
On Fri, Mar 12, 2021 at 03:24PM +0100, Andrey Konovalov wrote:
> Update KASAN documentation:
>
> - Give some sections clearer names.
> - Remove unneeded subsections in the "Tests" section.
> - Move the "For developers" section and split into subsections.
>
> Signed-off-by: Andrey Konovalov
Revi
LOTTO.NL,
2391 Beds 152 Koningin Julianaplein 21,
Den Haag-Netherlands.
(Lotto affiliate with Subscriber Agents).
From: Susan Console
(Lottery Coordinator)
Website: www.lotto.nl
Sir/Madam,
CONGRATULATIONS!!!
We are pleased to inform you of the result of the Lotto NL Winners
International progr
On Fri, 12 Mar 2021, Rob Herring wrote:
> On Fri, Mar 12, 2021 at 4:08 AM Lee Jones wrote:
> >
> > Fixes the following W=1 kernel build warning(s):
> >
> > drivers/of/device.c:72: warning: expecting prototype for
> > of_dma_configure(). Prototype was for of_dma_configure_id() instead
> > drive
On Fri, Mar 12, 2021 at 03:24PM +0100, Andrey Konovalov wrote:
> Update the "Overview" section in KASAN documentation:
>
> - Outline main use cases for each mode.
> - Mention that HW_TAGS mode need compiler support too.
> - Move the part about SLUB/SLAB support from "Usage" to "Overview".
> - Punc
On Fri, Mar 12, 2021 at 03:24PM +0100, Andrey Konovalov wrote:
> Update the "Usage" section in KASAN documentation:
>
> - Add inline code snippet markers.
> - Reword the part about stack traces for clarity.
> - Other minor clean-ups.
>
> Signed-off-by: Andrey Konovalov
Reviewed-by: Marco Elver
On Fri, Mar 12, 2021 at 03:24PM +0100, Andrey Konovalov wrote:
> Update the "Error reports" section in KASAN documentation:
>
> - Mention that bug titles are best-effort.
> - Move and reword the part about auxiliary stacks from
> "Implementation details".
> - Punctuation, readability, and other
On Fri, Mar 12, 2021 at 03:24PM +0100, Andrey Konovalov wrote:
> Update the "Boot parameters" section in KASAN documentation:
>
> - Mention panic_on_warn.
> - Mention kasan_multi_shot and its interaction with panic_on_warn.
> - Clarify kasan.fault=panic interaction with panic_on_warn.
> - A readab
On Fri, Mar 12, 2021 at 03:24PM +0100, Andrey Konovalov wrote:
> Update the "Implementation details" section for generic KASAN:
>
> - Don't mention kmemcheck, it's not present in the kernel anymore.
> - Don't mention GCC as the only supported compiler.
> - Update kasan_mem_to_shadow() definition t
On Fri, 12 Mar 2021, Rob Herring wrote:
> On Fri, Mar 12, 2021 at 4:08 AM Lee Jones wrote:
> >
> > Fixes the following W=1 kernel build warning(s):
> >
> > drivers/of/fdt.c:478: warning: Function parameter or member 'node' not
> > described in '__reserved_mem_reserve_reg'
> > drivers/of/fdt.c:
On Fri, Mar 12, 2021 at 03:24PM +0100, Andrey Konovalov wrote:
> Update the "Implementation details" section for SW_TAGS KASAN:
>
> - Clarify the introduction sentence.
> - Punctuation, readability, and other minor clean-ups.
>
> Signed-off-by: Andrey Konovalov
Reviewed-by: Marco Elver
> ---
On Mon, Dec 21, 2020 at 04:00:26PM +0900, Namhyung Kim wrote:
> Hello,
>
> This is to optimize the event synthesis during perf record.
>
> The first patch is to reduce memory usage when many threads are used.
> The second is to avoid unncessary syscalls for kernel threads. And
> the last one is
On Fri, Mar 12, 2021 at 03:24PM +0100, Andrey Konovalov wrote:
> Update the "Implementation details" section for HW_TAGS KASAN:
>
> - Punctuation, readability, and other minor clean-ups.
>
> Signed-off-by: Andrey Konovalov
Reviewed-by: Marco Elver
> ---
> Documentation/dev-tools/kasan.rst |
On Fri, Mar 12, 2021 at 03:24PM +0100, Andrey Konovalov wrote:
> Update the "Shadow memory" section in KASAN documentation:
>
> - Rearrange the introduction paragraph do it doesn't give a
> "KASAN has an issue" impression.
> - Update the list of architectures with vmalloc support.
> - Punctuatio
On Sun, Mar 07, 2021 at 09:00:26PM +0300, Arseny Krasnov wrote:
This adds some logic to current stream enqueue function for SEQPACKET
support:
1) Use transport's seqpacket enqueue callback.
2) Return value from enqueue function is whole record length or error
for SOCK_SEQPACKET.
Signed-off-by:
On Fri, Mar 12, 2021 at 03:24PM +0100, Andrey Konovalov wrote:
> Update the "Ignoring accesses" section in KASAN documentation:
>
> - Mention __no_sanitize_address/noinstr.
> - Mention kasan_disable/enable_current().
> - Mention kasan_reset_tag()/page_kasan_tag_reset().
> - Readability and punctua
On Thu, Mar 11, 2021 at 08:48:27AM +, Mel Gorman wrote:
> I don't have that information unfortunately. It's a chicken and egg
> problem because without the API, there is no point creating new users.
> For example, fault around or readahead could potentially batch pages
> but whether it is actua
On Fri, Mar 12, 2021 at 03:24PM +0100, Andrey Konovalov wrote:
> Update the "Tests" section in KASAN documentation:
>
> - Add an introductory sentence.
> - Add proper indentation for the list of ways to run KUnit tests.
> - Punctuation, readability, and other minor clean-ups.
>
> Signed-off-by: A
On Fri, 12 Mar 2021 10:44:23 +0900
Masami Hiramatsu wrote:
> > Why is this using boot_command_line instead of what is passed in, which
> > might be different?
>
> I think you may know the reason...
>
> commit f61872bb58a1cd8f0422aab19408be579d38
> Author: Steven Rostedt (VMware)
> Date:
601 - 700 of 1517 matches
Mail list logo
