From: Pavel Begunkov
> Sent: 27 January 2021 15:48
>
> On 16/01/2021 05:18, Al Viro wrote:
> > On Sat, Jan 09, 2021 at 10:11:09PM +, Pavel Begunkov wrote:
> >
> >>> Does any code actually look at the fields as a pair?
> >>> Would it even be better to use separate bytes?
> >>> Even growing the
From: Richard Neumann
Added Richard Neumann (me) to the list of maintainers for the
AMD Sensor Fusion Hub driver.
Signed-off-by: Richard Neumann
---
MAINTAINERS | 1 +
1 file changed, 1 insertion(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index 992fe3b0900a..de28236a08fe 100644
---
From: Richard Neumann
Outsourced the mask definitions of the four sensors into
the PCI device driver header file for later use with the quirks.
Also renamed the values from *_EN to *_MASK to emphasize that
they are actually sensor bitmasks for matching against activestatus.
Signed-off-by:
From: Richard Neumann
Added quirks file to determine the sensor masks for systems
that do not have it stored in the corresponding P2C register.
Values are based upon user reports from:
https://bugzilla.kernel.org/show_bug.cgi?id=199715
Signed-off-by: Richard Neumann
---
From: Richard Neumann
This patch adds quirks to the upstream (v8) version of the
AMD Sensor Fusion Hub driver.
The quirks provide a function to detect the sensor mask for systems
that do not have it stored in the AMD_P2C_MSG3 register.
The information about the systems IDs and available sensors
Hi Vincent,
On Wed, Jan 27, 2021 at 05:21:15PM +0100, Vincent Guittot wrote:
> Hi Cristian,
>
>
> On Tue, 12 Jan 2021 at 20:20, Cristian Marussi
> wrote:
> >
> > Hi all,
> >
> > The current SCMI implementation does not provide an interface to easily
> > develop and include a custom vendor
On Wed, Jan 27, 2021 at 05:42:47PM +0530, Anant Thazhemadam wrote:
> The newer usb_control_msg_{send|recv}() API are an improvement on the
> existing usb_control_msg() as it ensures that a short read/write is treated
> as an error, data can be used off the stack, and raw usb pipes need not be
>
On Wed 27 Jan 09:15 CST 2021, Greg KH wrote:
> On Wed, Jan 13, 2021 at 08:56:25PM +0530, Manivannan Sadhasivam wrote:
> > Hi Greg,
> >
> > On Wed, Jan 06, 2021 at 10:44:13AM -0800, Hemant Kumar wrote:
> > > This patch series adds support for UCI driver. UCI driver enables
> > > userspace
> > >
From: Ard Biesheuvel
commit 7bc1a0f9e1765830e945669c99c59c35cf9bca82 upstream.
On arm64, the global variable memstart_addr represents the physical
address of PAGE_OFFSET, and so physical to virtual translations or
vice versa used to come down to simple additions or subtractions
involving the
Hi Cristian,
On Tue, 12 Jan 2021 at 20:20, Cristian Marussi wrote:
>
> Hi all,
>
> The current SCMI implementation does not provide an interface to easily
> develop and include a custom vendor protocol implementation as prescribed
> by the SCMI standard, also because, there is not currently any
On Tue, Jan 26, 2021 at 08:50:02AM +0800, brookxu wrote:
>
> trace point, eBPF and other hook technologies are better for production
> environments. But for pure debugging work, adding hook points feels a bit
> heavy. However, your suggestion is very valuable, thank you very much.
What feels
On Wed, Jan 27, 2021 at 09:59:14AM -0600, Josh Poimboeuf wrote:
> On Wed, Jan 27, 2021 at 12:27:09PM +0100, Peter Zijlstra wrote:
> > On Wed, Jan 27, 2021 at 10:13:47AM +0100, Peter Zijlstra wrote:
> > > On Tue, Jan 26, 2021 at 05:57:30PM -0600, Josh Poimboeuf wrote:
> >
> > > > Well, I hate it,
On Wed, 27 Jan 2021, Andy Shevchenko wrote:
> On Wednesday, January 27, 2021, Lee Jones wrote:
>
> > Fixes the following W=1 kernel build warning(s):
> >
> > drivers/thunderbolt/dma_port.c: In function ‘dma_port_flash_write_block’:
> > drivers/thunderbolt/dma_port.c:331:6: warning: variable
Thanks,
applied.
On Wed, 27 Jan 2021 12:37:16 +0100
Peter Zijlstra wrote:
> And that's just really daft.. why are you adding two unconditional
> function calls to __schedule() that are a complete waste of time
> 99.99% of the time?
>
> If anything, this should be fixed in schedule_idle().
Note, those two
Grab kvm->lock before pinning memory when registering an encrypted
region; sev_pin_memory() relies on kvm->lock being held to ensure
correctness when checking and updating the number of pinned pages.
Add a lockdep assertion to help prevent future regressions.
Cc: Thomas Gleixner
Cc: Ingo Molnar
On 1/26/21 12:59 PM, Maxim Mikityanskiy wrote:
> The cited commit introduced a serious regression with SATA write speed,
> as found by bisecting. This patch reverts this commit, which restores
> write speed back to the values observed before this commit.
>
> The performance tests were done on a
Hi Stefan,
In the recommendations from SafeCurves (https://safecurves.cr.yp.to/twist.html)
there are a number of attacks against ECC twists. Two of those attacks are
relevant against NIST P192: invalid-curve attacks and invalid-curve attacks
against ladders.
Both attacks can be mitigated by
On Wed, Jan 27, 2021 at 11:21:18PM +1100, Stephen Rothwell wrote:
> Caused by commit
>
> 5567a1a4b1c3 ("ramfs: support O_TMPFILE")
Can this be merged or sent to Al, please? It's ancient patch.
On Wed, 27 Jan 2021, Andy Shevchenko wrote:
> On Wednesday, January 27, 2021, Lee Jones wrote:
>
> > Fixes the following W=1 kernel build warning(s):
> >
> > drivers/thunderbolt/path.c:476: warning: Function parameter or member
> > 'path' not described in 'tb_path_activate'
> >
On Tue, Jan 26, 2021 at 3:09 PM Jens Axboe wrote:
>
> On 1/26/21 7:46 AM, Pavel Tatashin wrote:
> > Currently, loop device has only one global lock: loop_ctl_mutex.
> >
> > This becomes hot in scenarios where many loop devices are used.
> >
> > Scale it by introducing per-device lock: lo_mutex
In order to support Qualcomm ISP hardware architectures that diverge
from older architectures, the CSID subdevice drivers needs to be refactored
to better abstract the different ISP hardware architectures.
Signed-off-by: Robert Foss
---
Changes since v1
- kernel test robot: Add missing
On Wed, Jan 27, 2021 at 10:59 AM Will Deacon wrote:
>
> On Mon, 25 Jan 2021 14:19:05 -0500, Pavel Tatashin wrote:
> > Changelog:
> > v10:
> > - Addressed a lot of comments form James Morse and from Marc Zyngier
> > - Added review-by's
> > - Synchronized with mainline
> >
> >
While this code is gross, I think we need to add it back for now:
Acked-by: Christoph Hellwig
I'll put converting the block device buffered I/O path to iomap or
an iomap lookalike on the backburner to fix this..
Add bindings for qcom,msm8996-camss in order to support the camera
subsystem on MSM8996.
Signed-off-by: Robert Foss
---
Changes since v2
- Rob: Add new line at end of file
- Rob: Remove redundant descriptions
- Rob: Add power domain description
- Rob: Make clock-lanes a constant
- Rob:
Add bindings for qcom,sdm660-camss in order to support the camera
subsystem on SDM630/660 and SDA variants.
Signed-off-by: Robert Foss
---
Changes since v2
- Rob: Add new line at end of file
- Rob: Remove redundant descriptions
- Rob: Add power domain description
- Rob: Make clock-lanes a
On 10/24/20 6:20 PM, Adam Ford wrote:
This driver is intended to work with the multimedia block which
contains display and camera subsystems:
LCDIF
ISI
MIPI CSI
MIPI DSI
Signed-off-by: Adam Ford
---
drivers/clk/imx/clk-blk-ctl-imx8mn.c | 80
You seem
Add bindings for qcom,msm8916-camss in order to support the camera
subsystem on MSM8916.
Signed-off-by: Robert Foss
---
Changes since v2:
- Remove redundant descriptions
- Add power domain description
- Make clock-lanes a constant
- Add max & minItems to data-lanes
- Remove ports
Add bindings for qcom,sdm845-camss in order to support the camera
subsystem for SDM845.
Signed-off-by: Robert Foss
---
Changes since v2
- Rob: Removed extra empty lines at end of file
- Rob: Add new line at end of file
- Rob: Remove redundant descriptions
- Rob: Add power domain description
On 20:50-20210127, Aswath Govindraju wrote:
> Hi Nishanth,
>
> On 27/01/21 8:44 pm, Nishanth Menon wrote:
> > On 20:38-20210127, Aswath Govindraju wrote:
> >> The following speed modes are now supported in J7200 SoC,
> >> - HS200 and HS400 modes at 1.8 V car
From: Bjorn Helgaas
This reverts commit 4257f7e008ea394fcecc050f1569c3503b8bcc15.
Kenneth reported that after 4257f7e008ea, he sees a torrent of disk I/O
errors on his NVMe device, and possibly other devices, until a reboot.
Link:
On Wed, 27 Jan 2021 at 16:33, Kalle Valo wrote:
> ...
> Forgot to mention that I can remove the Fixes tags during commit, so no
> need to resend just because of those.
Cool, thanks.
> > I can definitely see how you can reasonably disagree, but I would not
> > be comfortable having code that
On Wed, 27 Jan 2021, Bjorn Helgaas wrote:
> > Any new news on this? Disabling "tlp" (which just shifts the problem around
> > on my machine) shouldn't be a solution for this issue.
>
> Agreed; disabling "tlp" is a workaround but not a solution.
Actually, disabling "tlp" doesn't fix the issue;
On Wed, Jan 27, 2021 at 12:27:09PM +0100, Peter Zijlstra wrote:
> On Wed, Jan 27, 2021 at 10:13:47AM +0100, Peter Zijlstra wrote:
> > On Tue, Jan 26, 2021 at 05:57:30PM -0600, Josh Poimboeuf wrote:
>
> > > Well, I hate it, but I'm not sure I have any better ideas. It should be
> > > possible to
On Wed, 27 Jan 2021, Bjorn Helgaas wrote:
> Do you have a URL for your initial report that I could include in the
> revert commit log?
I don't, as I'd emailed the committers first and that was then CCed to the
mailing list, but here's what I'd sent:
Date: Fri, 25 Dec 2020 16:38:56
From:
Hi David,
On 27.01.2021 18:25, Dave Stevenson wrote:
Hi Andrey
On Tue, 26 Jan 2021 at 15:55, Andrey Konovalov
wrote:
Hi Dave,
On 26.01.2021 16:01, Dave Stevenson wrote:
Hi Andrey
On Tue, 26 Jan 2021 at 07:50, Andrey Konovalov
wrote:
This control is needed for imx219 driver, as the
On Wed, Jan 27, 2021 at 12:29:08AM +0100, Ricardo Ribalda wrote:
> - Is there any platform where dma_alloc_noncontiguos can fail?
> This is, !ops->alloc_noncontiguous and !dev->coherent_dma_mask
> If yes then we need to add a function to let the driver know in
> advance that it has to use the
On Mon, 25 Jan 2021 14:19:05 -0500, Pavel Tatashin wrote:
> Changelog:
> v10:
> - Addressed a lot of comments form James Morse and from Marc Zyngier
> - Added review-by's
> - Synchronized with mainline
>
> [...]
Applied the first 12 patches to arm64 (for-next/kexec), thanks!
Hi Linus,
please pull two fixes for the parisc architecture for kernel 5.11-rc6 from:
http://git.kernel.org/pub/scm/linux/kernel/git/deller/parisc-linux.git
parisc-5.11-2
Two small fixes:
* Fix linking error with 64-bit kernel when modules are disabled,
reported by kernel test robot.
*
27.01.2021 13:02, Viresh Kumar пишет:
> On 27-01-21, 14:40, Viresh Kumar wrote:
>> dev_pm_opp_set_bw() is getting removed and dev_pm_opp_set_opp() should
>> be used instead. Migrate to the new API.
>>
>> We don't want the OPP core to manage the clk for this driver, migrate to
>>
On 27/01/2021 15:42, Pavel Begunkov wrote:
> On 27/01/2021 15:00, Kanchan Joshi wrote:
>> This RFC patchset adds asynchronous ioctl capability for NVMe devices.
>> Purpose of RFC is to get the feedback and optimize the path.
>>
>> At the uppermost io-uring layer, a new opcode IORING_OP_IOCTL_PT is
On 27 Jan 2021, at 5:18, David Hildenbrand wrote:
> Right now, if activation fails, we might already have exposed some pages to
> the buddy for CMA use (although they will never get actually used by CMA),
> and some pages won't be exposed to the buddy at all.
>
> Let's check for "single zone"
Task-work infra is required to introduce async-ioctl in nvme driver.
Without this being exported, NVMe needs to be built statically.
Signed-off-by: Kanchan Joshi
---
kernel/task_work.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/kernel/task_work.c b/kernel/task_work.c
Add a new block-dev operation for async-ioctl.
Driver managing the block-dev can choose to implement it.
Signed-off-by: Kanchan Joshi
---
include/linux/blkdev.h | 12
1 file changed, 12 insertions(+)
diff --git a/include/linux/blkdev.h b/include/linux/blkdev.h
index
On 20:56-20210127, Aswath Govindraju wrote:
> Hi Nishanth,
>
> On 27/01/21 8:42 pm, Nishanth Menon wrote:
> > On 20:38-20210127, Aswath Govindraju wrote:
> >> Add support for the zeroth instance of GPIO subsystem in the main domain.
> >>
> >> Signed-
On Wed, Jan 27, 2021 at 02:37:34PM +, Stefan Chulski wrote:
> Your mcbin-ss is A8K AX or A8K B0? On AX revisions we do not have FC support
> in firmware.
How do I tell? I don't want to remove the heatsink, and I don't see
anything in MV-S88-00E. I didn't grab a copy of the Errata before
On Wed, 27 Jan 2021 09:23:04 -0500
Matthew Rosato wrote:
> On 1/26/21 6:18 PM, Alex Williamson wrote:
> > On Mon, 25 Jan 2021 09:40:38 -0500
> > Matthew Rosato wrote:
> >
> >> On 1/22/21 6:48 PM, Alex Williamson wrote:
> >>> On Tue, 19 Jan 2021 15:02:30 -0500
> >>> Matthew Rosato wrote:
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 867157311dc8..ecd988b4a838 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -7788,6 +7788,8 @@ F:include/linux/freezer.h
> F: include/linux/pm.h
> F: include/linux/suspend.h
> F: kernel/power/
> +F:
From: Lai Jiangshan
TSS_entry2task_stack is used to refer to tss.sp1 which is stored the value
of thread.sp0.
At the code where TSS_entry2task_stack is used in SWITCH_TO_KERNEL_STACK,
the CR3 is already kernel CR3 and kernel segments is loaded.
So we can directly use the percpu to get
Hi Sai,
On 27-01-21, 18:37, Sai Prakash Ranjan wrote:
> Hi Vinod,
>
> On 2021-01-27 18:00, Vinod Koul wrote:
> > + timer {
> > + compatible = "arm,armv8-timer";
> > + interrupts = > IRQ_TYPE_LEVEL_LOW)>,
> > + > IRQ_TYPE_LEVEL_LOW)>,
> > +
From: Lai Jiangshan
Like the way x86_64 uses the "old" stack, we can save the entry stack
pointer to a register and switch to the task stack. So that we have
space on the "old" stack to save more things or scratch registers.
Signed-off-by: Lai Jiangshan
---
arch/x86/entry/entry_32.S | 11
On Fri, Jan 22, 2021 at 11:27:16AM -0800, Elliot Berman wrote:
> This series was developed after discussion in
> https://lkml.org/lkml/2021/1/19/850
>
> The motivation for this series is an out-of-tree module which contains a large
> number of source files. This causes Kbuild to exceed the
On 16/01/2021 05:18, Al Viro wrote:
> On Sat, Jan 09, 2021 at 10:11:09PM +, Pavel Begunkov wrote:
>
>>> Does any code actually look at the fields as a pair?
>>> Would it even be better to use separate bytes?
>>> Even growing the on-stack structure by a word won't really matter.
>>
>> u8 type,
It's similar like XZ compressed files. For the simplicity, both XZ
and ZSTD tests are done in a single function. The format is specified
via $COMPRESS_FORMAT and the compression function is pre-defined.
Signed-off-by: Takashi Iwai
---
.../selftests/firmware/fw_filesystem.sh | 75
The test patterns are almost same in three sequential tests.
Make the unified helper function for improving the readability.
Signed-off-by: Takashi Iwai
---
.../selftests/firmware/fw_filesystem.sh | 106 +-
1 file changed, 30 insertions(+), 76 deletions(-)
diff --git
On Fri, Jan 22, 2021 at 12:11:08PM -0800, Kenneth R. Crudup wrote:
> > > From: Kenneth R. Crudup
> > > I've been running Linus' master branch on my laptop (Dell XPS 13
> > > 2-in-1). With this commit in place, after resuming from hibernate
> > > my machine is essentially useless, with a torrent
On 1/25/2021 4:24 AM, David Rientjes wrote:
> On Wed, 20 Jan 2021, Vlastimil Babka wrote:
>
>> On 1/19/21 8:26 PM, David Rientjes wrote:
>>> On Mon, 18 Jan 2021, Charan Teja Reddy wrote:
>>>
should_proactive_compact_node() returns true when sum of the
weighted fragmentation score of
Hi,
it seems that ZSTD format is getting popular, and I've been asked
about the firmware loader support. So I took a quick glance, and it
turned out that it's fairly easy thanks to the existing ZSTD API.
Now high time to submit something.
The first patch adds a new Kconfig
Due to the popular demands on ZSTD, here is a patch to add a support
of ZSTD-compressed firmware files via the direct firmware loader.
It's just like XZ-compressed file support, providing a decompressor
with ZSTD. Since ZSTD API can give the decompression size beforehand,
the code is even simpler
The test uses a different firmware name, and we forgot to adapt for
the XZ compressed file tests.
Signed-off-by: Takashi Iwai
---
tools/testing/selftests/firmware/fw_filesystem.sh | 2 ++
1 file changed, 2 insertions(+)
diff --git a/tools/testing/selftests/firmware/fw_filesystem.sh
On 27/01/2021 15:00, Kanchan Joshi wrote:
> This RFC patchset adds asynchronous ioctl capability for NVMe devices.
> Purpose of RFC is to get the feedback and optimize the path.
>
> At the uppermost io-uring layer, a new opcode IORING_OP_IOCTL_PT is
> presented to user-space applications. Like
From: Kan Liang
With Architectural Performance Monitoring Version 5, CPUID 10.ECX cpu
leaf indicates the fixed counter enumeration. This extends the previous
count to a bitmap which allows disabling even lower fixed counters.
It could be used by a Hypervisor.
The existing intel_ctrl variable is
From: Kan Liang
Add perf core PMU support for the Intel Sapphire Rapids server, which is
the successor of the Intel Ice Lake server. The enabling code is based
on Ice Lake, but there are several new features introduced.
The event encoding is changed and simplified, e.g., the event codes
which
From: Kan Liang
Current perf doesn't check the index of a Topdown metrics event before
updating the event. A perf tool user may get a value from an unsupported
Topdown metrics event.
For example, the L2 topdown event, cpu/event=0x00,umask=0x84/, is not
supported on Ice Lake. A perf tool user
From: Kan Liang
Similar to Ice Lake, Intel Sapphire Rapids server also supports the
topdown performance metrics feature. The difference is that Intel
Sapphire Rapids server extends the PERF_METRICS MSR to feature TMA
method level two metrics, which will introduce 8 metrics events. Current
From: Kan Liang
Current PERF_SAMPLE_WEIGHT sample type is very useful to expresses the
cost of an action represented by the sample. This allows the profiler
to scale the samples to be more informative to the programmer. It could
also help to locate a hotspot, e.g., when profiling by memory
> On Jan 27, 2021, at 7:03 AM, Mimi Zohar wrote:
>
> [Cc'ing linux-integrity]
>
> On Wed, 2021-01-27 at 11:46 +, David Howells wrote:
>> Jarkko Sakkinen wrote:
>>
I suppose a user space tool could be created. But wouldn’t what is
currently done in the kernel in this area need
From: Kan Liang
Changes since V1:
- Use PERF_SAMPLE_WEIGHT_STRUCT to replace PERF_SAMPLE_WEIGHT_EXT.
The new sample type PERF_SAMPLE_WEIGHT_STRUCT shares the same space as
the current PERF_SAMPLE_WEIGHT.
- Move the check for the unsupported Topdown event into a separate patch
- Use the
On 26-01-21, 16:18, Thara Gopinath wrote:
> When bam dma is "controlled remotely", thus far clocks were not controlled
> from the Linux. In this scenario, Linux was disabling runtime pm in bam dma
> driver and not doing any clock management in suspend/resume hooks.
>
> With introduction of crypto
From: Richard Neumann
This patch adds quirks to the upstream (v8) version of the
AMD Sensor Fusion Hub driver.
The quirks provide a function to detect the sensor mask for systems
that do not have it stored in the AMD_P2C_MSG3 register.
The information about the systems IDs and available sensors
From: Richard Neumann
Added quirks file to determine the sensor masks for systems
that do not have it stored in the corresponding P2C register.
Values are based upon user reports from:
https://bugzilla.kernel.org/show_bug.cgi?id=199715
Signed-off-by: Richard Neumann
---
From: Richard Neumann
Added Richard Neumann (me) to the list of maintainers for the
AMD Sensor Fusion Hub driver.
Signed-off-by: Richard Neumann
---
MAINTAINERS | 1 +
1 file changed, 1 insertion(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index 992fe3b0900a..de28236a08fe 100644
---
Fix kprobe_on_func_entry() returns error code instead of false so that
register_kretprobe() can return an appropriate error code.
append_trace_kprobe() expects the kprobe registration returns -ENOENT
when the target symbol is not found, and it checks whether the target
module is unloaded or not.
From: Richard Neumann
Outsourced the mask definitions of the four sensors into
the PCI device driver header file for later use with the quirks.
Also renamed the values from *_EN to *_MASK to emphasize that
they are actually sensor bitmasks for matching against activestatus.
Signed-off-by:
Amdgpu driver uses 4-byte data type as DQM fence memory,
and transmits GPU address of fence memory to microcode
through query status PM4 message. However, query status
PM4 message definition and microcode processing are all
processed according to 8 bytes. Fence memory only allocates
4 bytes of
On Wed, Jan 27, 2021 at 02:55:07PM +0100, Rafael J. Wysocki wrote:
> On Wed, Jan 27, 2021 at 1:54 PM Bjorn Helgaas wrote:
> >
> > From: Bjorn Helgaas
> >
> > Clean up a few _OSC-related things.
> >
> > We talked about the _OSC failure message in the last patch long ago, and I
> > just dropped
Emil Renner Berthing writes:
> On Wed, 27 Jan 2021 at 16:20, Kalle Valo wrote:
>>
>> Willem de Bruijn writes:
>>
>> > On Wed, Jan 27, 2021 at 5:23 AM Emil Renner Berthing
>> > wrote:
>> >>
>> >> In commit d3ccc14dfe95 most of the tasklets in this driver was
>> >> updated to the new API.
From: Lai Jiangshan
TSS_entry2task_stack is used to refer to tss.sp1 which is stored the value
of thread.sp0.
At the code where TSS_entry2task_stack is used in sysenter, the CR3 is
already kernel CR3 and kernel segments is loaded.
So that we can directly use percpu for it instead of
From: Lai Jiangshan
Prepare for using percpu and removing TSS_entry2task_stack
Signed-off-by: Lai Jiangshan
---
arch/x86/entry/entry_32.S | 22 +-
1 file changed, 17 insertions(+), 5 deletions(-)
diff --git a/arch/x86/entry/entry_32.S b/arch/x86/entry/entry_32.S
index
From: Lai Jiangshan
sp1 is not used by hardware and is used as thread.sp0. We should just
use new percpu variable.
And remove unneeded TSS_sp1.
Signed-off-by: Lai Jiangshan
---
arch/x86/entry/entry_32.S| 6 +++---
arch/x86/include/asm/processor.h | 2 ++
From: Lai Jiangshan
When X86_BUG_CPU_MELTDOWN & KPTI, cpu_current_top_of_stack lives in the
TSS which is also in the user CR3 and it becomes a coveted fruit. An
attacker can fetch the kernel stack top from it and continue next steps
of actions based on the kernel stack.
The address might not
On Wed, Jan 27, 2021 at 05:49:46PM +0300, Dan Carpenter wrote:
> On Wed, Jan 27, 2021 at 03:25:20PM +0100, Greg KH wrote:
> > On Wed, Jan 27, 2021 at 10:17:08PM +0800, carlis wrote:
> > > On Wed, 27 Jan 2021 15:13:05 +0100
> > > Greg KH wrote:
> > >
> > > > On Wed, Jan 27, 2021 at 10:08:09PM
Commit cca079ef8ac29a7c02192d2bad2ffe4c0c5ffdd0 makes sparc32 use
memblocks instead of the previous bootmem solution. Unfortunately, due
to this:
#define PAGE_OFFSET 0xf000
#define __va(x) ((void *)((unsigned long) (x) - phys_base +
PAGE_OFFSET))
#define phys_to_virt __va
it
On Wed, Jan 27, 2021 at 12:03:58AM +0530, Anant Thazhemadam wrote:
> The newer usb_control_msg_{send|recv}() API are an improvement on the
> existing usb_control_msg() as it ensures that a short read/write is treated
> as an error, data can be used off the stack, and raw usb pipes need not be
>
On Wed, Jan 27, 2021 at 03:31:17PM +0100, Bartosz Golaszewski wrote:
> On Wed, Jan 27, 2021 at 3:22 PM Greg Kroah-Hartman
> wrote:
> >
> > On Fri, Jan 22, 2021 at 11:35:59AM -0800, Saravana Kannan wrote:
> > > There are multiple instances of GPIO device tree nodes of the form:
> > >
> > > foo {
>
From: Lai Jiangshan
In x86_64, tss.sp1 is reused as cpu_current_top_of_stack. But we can
directly use percpu since CR3 and gs_base is correct when it is used.
In x86_32, tss.sp1 is resued as thread.sp0 in three places in entry
code. We have the correct CR3 and %fs at two of the places. The
In host control mode, reads are the major source of activation trials.
Keep track of those reads counters, for both active as well inactive
regions.
We reset the read counter upon write - we are only interested in "clean"
reads. less intuitive however, is that we also reset it upon region's
Hi Nishanth,
On 27/01/21 8:42 pm, Nishanth Menon wrote:
> On 20:38-20210127, Aswath Govindraju wrote:
>> Add support for the zeroth instance of GPIO subsystem in the main domain.
>>
>> Signed-off-by: Aswath Govindraju
>
>
> I really dont want to pick up one patch
Hi Jianlin,
Now as you reported, this must be fixed with actual bug which prevent
kretprobe events on unloaded module. I'll send another one which also
fix this issue.
Thank you,
On Wed, 27 Jan 2021 23:15:07 +0800
Jianlin Lv wrote:
> When trying to create kretprobe with the wrong function
On 18/01/2021 14:55, Hans Verkuil wrote:
> On 12/01/2021 16:24, Hans Verkuil wrote:
>> Hi Maxime,
>>
>> On 11/01/2021 15:22, Maxime Ripard wrote:
>>> Hi,
>>>
>>> Here's a series introducing the CEC support for the BCM2711 found on the
>>> RaspberryPi4.
>>>
>>> The BCM2711 HDMI controller uses a
Before the offending commit in msm_atomic_commit_tail wait_flush was
called once per frame, after the commit was submitted. After it
wait_flush is also called at the beginning to ensure previous
potentially async commits are done.
For cmd panels the source of wait_flush is a ping-pong irq
On Thu, 28 Jan 2021 00:13:53 +0900
Masami Hiramatsu wrote:
> Hi Nikolay,
>
> On Wed, 27 Jan 2021 15:43:29 +0200
> Nikolay Borisov wrote:
>
> > Hello,
> >
> > I'm currently seeing latest Linus' master being somewhat broken w.r.t
> > krpobes. In particular I have the following test-case:
> >
Hi Andrey
On Tue, 26 Jan 2021 at 15:55, Andrey Konovalov
wrote:
>
> Hi Dave,
>
> On 26.01.2021 16:01, Dave Stevenson wrote:
> > Hi Andrey
> >
> > On Tue, 26 Jan 2021 at 07:50, Andrey Konovalov
> > wrote:
> >>
> >> This control is needed for imx219 driver, as the link frequency
> >> is
On Wed, 27 Jan 2021 at 16:20, Kalle Valo wrote:
>
> Willem de Bruijn writes:
>
> > On Wed, Jan 27, 2021 at 5:23 AM Emil Renner Berthing
> > wrote:
> >>
> >> In commit d3ccc14dfe95 most of the tasklets in this driver was
> >> updated to the new API. However for the rx_work_tasklet only the
> >>
On Wed, Jan 27, 2021 at 05:12:16PM +0200, Avri Altman wrote:
> In order not to hang on to “cold” regions, we shall inactivate a
> region that has no READ access for a predefined amount of time -
> READ_TO_MS. For that purpose we shall monitor the active regions list,
> polling it on every
> > You can devmem 0xF2400240(Device ID Status Register).
> > #define A8040_B0_DEVICE_ID 0x8045
> > #define A8040_AX_DEVICE_ID 0x8040
> > #define A7040_B0_DEVICE_ID 0x7045
> > #define A7040_AX_DEVICE_ID 0x7040
> > #define A3900_A1_DEVICE_ID 0x6025
> > #define
On Wed, Jan 27, 2021 at 05:03:12AM +, Bharat Kumar Gogada wrote:
> > On Thu, Jan 21, 2021 at 03:29:16PM +0530, Bharat Kumar Gogada wrote:
> Here is the CCI spec
> https://developer.arm.com/documentation/ddi0470/k/preface
I'm sure it was obvious, but please include this in the commit log as
We will use it later, when we'll need to differentiate between device
and host control modes.
Signed-off-by: Avri Altman
---
drivers/scsi/ufs/ufshpb.c | 7 ---
1 file changed, 4 insertions(+), 3 deletions(-)
diff --git a/drivers/scsi/ufs/ufshpb.c b/drivers/scsi/ufs/ufshpb.c
index
No need of BCLK state maintenance from driver side as
clock_enable and clk_disable API's maintaing state counter.
One of the major issue was spotted when Headset jack inserted
while playback continues, due to same PCM device node opens twice
for playaback/capture and closes once for capture and
Hi Nishanth,
On 27/01/21 8:44 pm, Nishanth Menon wrote:
> On 20:38-20210127, Aswath Govindraju wrote:
>> The following speed modes are now supported in J7200 SoC,
>> - HS200 and HS400 modes at 1.8 V card voltage, in MMCSD0 subsystem [1].
>> - UHS-I speed modes in MMCSD1 sub
901 - 1000 of 1636 matches
Mail list logo
