Hello,
syzbot found the following issue on:
HEAD commit:d01f2f7e Add linux-next specific files for 20210226
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=17a449cad0
kernel config: https://syzkaller.appspot.com/x/.config?x=a1746d2802a82a05
dashboard
25.02.2021 16:42, Arnd Bergmann пишет:
> From: Arnd Bergmann
>
> The added device_property_present() call causes a build
> failure in some configurations because of the missing header:
>
> drivers/rtc/rtc-tps65910.c:422:7: error: implicit declaration of function
> 'device_property_present' [-We
Hi
On 2021-02-26 23:01, Bhaumik Bhatt wrote:
On 2021-02-26 06:52 AM, Manivannan Sadhasivam wrote:
On Fri, Feb 26, 2021 at 04:12:49PM +0530, Gokul Sriram Palanisamy
wrote:
On platforms with two or more identical mhi
devices, qmi service will run with identical
qrtr-node-id. Because of this iden
The OASIS virtio spec defines a sound device type ID that is not
present in the header yet.
Signed-off-by: Anton Yakovlev
---
include/uapi/linux/virtio_ids.h | 1 +
1 file changed, 1 insertion(+)
diff --git a/include/uapi/linux/virtio_ids.h b/include/uapi/linux/virtio_ids.h
index bc1c0621f5ed..
Introduce skeleton of the virtio sound driver. The driver implements
the virtio sound device specification, which has become part of the
virtio standard.
Initial initialization of the device, virtqueues and creation of an
empty ALSA sound device.
Signed-off-by: Anton Yakovlev
---
MAINTAINERS
The driver implements a message-based transport for I/O substream
operations. Before the start of the substream, the hardware buffer is
sliced into I/O messages, the number of which is equal to the current
number of periods. The size of each message is equal to the current
size of one period.
I/O
Like the HDA specification, the virtio sound device specification links
PCM substreams, jacks and PCM channel maps into functional groups. For
each discovered group, a PCM device is created, the number of which
coincides with the group number.
Introduce the module parameters for setting the hardwa
The control queue can be used by different parts of the driver to send
commands to the device. Control messages can be either synchronous or
asynchronous. The lifetime of a message is controlled by a reference
count.
Introduce a module parameter to set the message completion timeout:
msg_timeout
On 24.02.2021 09:41, Michael S. Tsirkin wrote:
> On Wed, Feb 24, 2021 at 08:07:48AM +0300, Arseny Krasnov wrote:
>> On 23.02.2021 17:17, Michael S. Tsirkin wrote:
>>> On Thu, Feb 18, 2021 at 08:39:37AM +0300, Arseny Krasnov wrote:
This adds transport callback and it's logic for SEQPACKET deq
Introduce the operators required for the operation of substreams.
Signed-off-by: Anton Yakovlev
---
sound/virtio/Makefile | 3 +-
sound/virtio/virtio_pcm.c | 2 +
sound/virtio/virtio_pcm.h | 4 +
sound/virtio/virtio_pcm_ops.c | 453 ++
4 file
Enumerate all available jacks and create ALSA controls.
At the moment jacks have a simple implementation and can only be used
to receive notifications about a plugged in/out device.
Signed-off-by: Anton Yakovlev
---
sound/virtio/Makefile | 1 +
sound/virtio/virtio_card.c | 14 +++
sound
All running PCM substreams are stopped on device suspend and restarted
on device resume.
Signed-off-by: Anton Yakovlev
---
sound/virtio/virtio_card.c| 56 +++
sound/virtio/virtio_pcm.c | 1 +
sound/virtio/virtio_pcm_ops.c | 41 -
3
Enumerate all available PCM channel maps and create ALSA controls.
Signed-off-by: Anton Yakovlev
---
sound/virtio/Makefile | 1 +
sound/virtio/virtio_card.c | 10 ++
sound/virtio/virtio_card.h | 8 ++
sound/virtio/virtio_chmap.c | 219
sound/virt
Hello!
On 27.02.2021 1:49, Laurent Pinchart wrote:
From: Laurent Pinchart
The new function checks if the list_head prev and next pointers are
NULL, in order to see if a list_head that has been zeroed when allocated
has been initialized with INIT_LIST_HEAD() or added to a list.
So zeroed
From: Masami Hiramatsu
commit f3fbd7ec62dec1528fb8044034e2885f2b257941 upstream
This is arm port of commit 6a5022a56ac3 ("kprobes/x86: Allow to
handle reentered kprobe on single-stepping")
Since the FIQ handlers can interrupt in the single stepping
(or preparing the single stepping, do_debug et
On 2021/2/26 9:01, Song Bao Hua (Barry Song) wrote:
-Original Message-
From: Luo Jiaxing [mailto:luojiax...@huawei.com]
Sent: Friday, February 26, 2021 12:39 AM
To: nouv...@lists.freedesktop.org; dri-de...@lists.freedesktop.org;
bske...@redhat.com
Cc: linux-kernel@vger.kernel.org; lin
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: 2c87f7a38f930ef6f6a7bdd04aeb82ce3971b54b
commit: 6e261d1090d6db0e9dd22978b6f38a2c58558a3f pinctrl: qcom: Add sm8250
lpass lpi pinctrl driver
config: arm64-randconfig-m031-20210226 (attached as .config)
compi
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: 8b83369ddcb3fb9cab5c1088987ce477565bb630
commit: 67fc209b527d023db4d087c68e44e9790aa089ef cpufreq: qcom-hw: drop
devm_xxx() calls from init/exit hooks
config: arm64-randconfig-m031-20210226 (attached as .con
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: 8b83369ddcb3fb9cab5c1088987ce477565bb630
commit: 97ef275077932c65b1b8ec5022abd737a9fbf3e0 powerpc/xive: Fix xmon support
on the PowerNV platform
config: powerpc64-randconfig-m031-20210226 (attached as .confi
Hi.
On Thu, Dec 03, 2020 at 12:51:11PM -0800, Nick Terrell wrote:
> From: Nick Terrell
>
> Please pull from
>
> g...@github.com:terrelln/linux.git tags/v7-zstd-1.4.6
>
> to get these changes. Alternatively the patchset is included.
>
> This patchset upgrades the zstd library to the latest u
Changes the way how LINEAR11 values are calculated. The new method
increases the precision of 2-3 digits.
old method:
corsairpsu-hid-3-1
Adapter: HID adapter
v_in:230.00 V
v_out +12v: 12.00 V
v_out +5v: 5.00 V
v_out +3.3v: 3.00 V
On Fri, Feb 26, 2021 at 08:36:55AM +0100, Daniel Vetter wrote:
> Also given that both deal with struct page there's a ton of divergence
> between these two that doesn't make much sense. Maybe could even share
> the code fully, aside from how you allocate the struct pages.
I've been saying that sin
On Fri, Feb 26, 2021 at 10:13 PM 'Fangrui Song' via Clang Built Linux
wrote:
>
> For folks who are interested in --gc-sections on metadata sections,
> I want to bring you awareness of the implication of __start_/__stop_ symbols
> and C identifier name sections.
> You can see https://github.com/Cl
There are a number of printf "mismatches" in the use of die() in
x86/tools/relocs.c. Fix them up and add the printf attribute to the
reloc.h header file to prevent them from ever coming back.
Cc: Thomas Gleixner
Cc: Ingo Molnar
Cc: Borislav Petkov
Cc: "H. Peter Anvin"
Cc: linux-kernel@vger.ke
Hi Kernel Test Robot,
On Sat, Feb 27, 2021 at 3:47 AM kernel test robot wrote:
> FYI, the error/warning still remains.
My response in
https://lore.kernel.org/linux-arm-kernel/CAMuHMdVmMLvvJ4mAa+y8JCJ2+5Bwu2W=psgn3toC1msTghn=x...@mail.gmail.com/
is still valid.
>
> tree: https://git.kernel.org
The include guard for the e1000e and e1000 hw.h files are the same, so
add the proper "E" term to the hw.h file for the e1000e driver.
This resolves some static analyzer warnings, like the one found by the
"lgtm.com" tool.
Cc: Jesse Brandeburg
Cc: Tony Nguyen
Cc: "David S. Miller"
Cc: Jakub Ki
Hi zuoqilin,
There's an obvious typo in the subject. Which is kind of ironical
considering the point of your patch.
Also, your patch is driver-specific, so "i2c/busses:" isn't an
appropriate prefix. According to the standard practice for the i2c
subsystem, the proper prefix for the subject would
25.02.2021 09:27, Nicolin Chen пишет:
...
>> The partially revert should be okay, but it's not clear to me what makes
>> difference for T124 since I don't see that problem on T30, which also
>> has active display at a boot time.
>
> Hmm..do you see ->attach_dev() is called from host1x_client_iommu
Alvaro,
On Sat, 27 Feb 2021 08:49:25 +,
Álvaro Fernández Rojas wrote:
>
> Hi Andy,
>
> That wasn’t top-posting,
If that isn't top-posting, I wonder what is. With HTML on top, to make
sure it breaks every established rule.
> I was just asking why it was changed to Not Applicable instead of
On Fri, Feb 26, 2021 at 08:47:36PM -0300, Arnaldo Carvalho de Melo wrote:
> Em Thu, Feb 25, 2021 at 09:35:04PM +0100, Jiri Olsa escreveu:
> > On Wed, Feb 24, 2021 at 02:59:16PM -0500, Nicholas Fraser wrote:
> > > From 9fd0b3889f00ad13662879767d833309d8a035b6 Mon Sep 17 00:00:00 2001
> > > From: Nic
On Fri, Feb 26, 2021 at 11:22:29PM +, Colin King wrote:
> From: Colin Ian King
>
> The error check on rval from the call to adp1653_get_fault currently
> returns if rval is non-zero. This appears to be incorrect as the
> following if statement checks for various bit settings in rval so
> clea
This patch reduces the product match for GA401 series laptops to
the minimum string required.
The GA401 series of laptops has a lengthy list of product
variations in the 2020 series and the 2021 series refresh
is using the same base product ID of GA401.
The same is also true for the GA502 series,
On Fri, Feb 26, 2021 at 08:41:26AM +0800, Jin, Yao wrote:
SNIP
> > + SET_SYMBOL(prefix, PMU_EVENT_SYMBOL);
> > len++;
> > }
> > }
> > }
> > +
> > + /* unlikely, but still.. */
> > + if (!len)
> > +
-randconfig-r013-20210227 (attached as .config)
compiler: powerpc-linux-gcc (GCC) 9.3.0
reproduce (this is a W=1 build):
wget
https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O
~/bin/make.cross
chmod +x ~/bin/make.cross
#
https://git.kernel.org/pub/scm
Le 11/02/2021 à 15:30, Segher Boessenkool a écrit :
On Thu, Feb 11, 2021 at 03:09:43PM +0100, Christophe Leroy wrote:
Le 11/02/2021 à 12:49, Segher Boessenkool a écrit :
On Thu, Feb 11, 2021 at 07:41:52AM +, Christophe Leroy wrote:
powerpc BUG_ON() is based on using twnei or tdnei instr
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: 3fb6d0e00efc958d01c2f109c8453033a2d96796
commit: 688f97ed3f5e339c0c2c09d9ee7ff23d5807b0a7 drm/amd/display: Add
vupdate_no_lock interrupts for DCN2.1
date: 4 days ago
config: i386-randconfig-r002-20210227
> From: AngeloGioacchino Del Regno
From: Martin Botka
That got caught in rebasing madness.. Should any additional mistakes appear,
I'll send a V2.
Konrad
>
> From: Masami Hiramatsu
>
> commit f3fbd7ec62dec1528fb8044034e2885f2b257941 upstream
>
> This is arm port of commit 6a5022a56ac3 ("kprobes/x86: Allow to
> handle reentered kprobe on single-stepping")
>
> Since the FIQ handlers can interrupt in the single stepping
> (or preparing the single
Signed-off-by: Martin Botka
Sorry for the second Sob. Previous one was HTML. Sorry
On Sat, Feb 27, 2021 at 11:40, Konrad Dybcio
wrote:
From: AngeloGioacchino Del Regno
From: Martin Botka
That got caught in rebasing madness.. Should any additional mistakes
appear, I'll send a V2.
From: Pavel Skripkin
Date: Fri, 26 Feb 2021 22:11:06 +0300
Hi,
> syzbot found WARNING in __alloc_pages_nodemask()[1] when order >= MAX_ORDER.
> It was caused by __netdev_alloc_skb(), which doesn't check len value after
> adding NET_SKB_PAD.
> Order will be >= MAX_ORDER and passed to __alloc_pag
On Thu, Feb 25, 2021 at 2:41 PM Mauro Carvalho Chehab
wrote:
>
> Document the basic policies of the media subsystem profile.
>
> Signed-off-by: Mauro Carvalho Chehab
> ---
>
> v2: fix the Documentation/*/media directories
>
>
> Documentation/driver-api/media/index.rst | 2 +
> .../media/m
From: Zhuang Yanying
If the TSC frequency of the VM is not equal to the host, hot-plugging vCPU
will cause the VM to be hang. The time of hang depends on the current TSC
value of the VM.
During hot-plugging vCPUs, kvm_arch_vcpu_create() uses max_tsc_khz,
that is the host TSC frequency, to initia
If build Image without CONFIG_PM_SLEEP, there would be a compile warning:
warning: ‘cdn_dp_resume’ defined but not used [-Wunused-function]
Because SET_SYSTEM_SLEEP_PM_OPS will do nothing without CONFIG_PM_SLEEP.
Make cdn_dp_resume depend on CONFIG_PM_SLEEP
Signed-off-by: Chen Jun
---
drivers/
Now swapfile in f2fs directly submit IO to blockdev according to
swapfile extents reported by f2fs when swapon, therefore there is
no need to check IS_SWAPFILE when exec filesystem operation.
Signed-off-by: Huang Jianan
Signed-off-by: Guo Weichao
---
fs/f2fs/data.c | 2 +-
fs/f2fs/f2fs.h | 3 +-
If the swapfile isn't created by pin and fallocate, it cann't be
guaranteed section-aligned, so it may be selected by f2fs gc. When
gc_pin_file_threshold is reached, the address of swapfile may change,
but won't be synchroniz to swap_extent, so swap will write to wrong
address, which will cause dat
Because page_no < sis->max guarantees that the while loop break out
normally, the wrong check contidion here doesn't cause a problem.
Signed-off-by: Huang Jianan
Signed-off-by: Guo Weichao
---
fs/f2fs/data.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/fs/f2fs/data.c b/f
Hi Amir,
On 2/27/21 6:41 AM, Amir Goldstein wrote:
On Sat, Feb 27, 2021 at 12:19 AM Alejandro Colomar (man-pages)
On 2/24/21 5:10 PM, Amir Goldstein wrote:
On Wed, Feb 24, 2021 at 4:22 PM Luis Henriques wrote:
.TP
+.B EOPNOTSUPP
I'll add the kernel version here:
.BR EOPNOTSUPP " (since
The CPU_MIPS64 and CPU_MIPS32 variables are supposed to be able to
distinguish broadly between 64-bit and 32-bit MIPS CPUs. However, they
weren't selected by the specialty CPUs, Octeon and Loongson, which meant
it was possible to hit a weird state of:
MIPS=y, CONFIG_64BIT=y, CPU_MIPS64=n
This
On Sat, Feb 27, 2021 at 7:52 AM Eric Gao wrote:
>
> sometimes, we need the msgsnd or msgrcv syscall can return after a limited
> time, so that the business thread do not be blocked here all the time. In
> this case, I add the msgsnd_timed and msgrcv_timed syscall that with time
> parameter, which
On Fri, Feb 26, 2021 at 8:08 PM Robert Richter wrote:
> On 25.02.21 15:37:10, Arnd Bergmann wrote:
>
> A possible double inclusion isn't really nice here, but it should work
> that way.
>
> Also, the menu entry for the driver is in fact only for the OF case,
> as it is always included for ACPI eve
Most of the Allwinner sun6i compatible devices contain a spinlock unit
which can be used to sync access to devices shared between the ARM cores
and the embedded companion core. According to the datasheets at least 32
spinlocks are supported. The implementation supports 32, 64, 128 and 256
spinlock
Adds documentation on how to use the sun6i_hwspinlock driver for sun6i
compatible series SoCs.
Signed-off-by: Wilken Gottwalt
---
Changes in v6:
- fixed formating and name issues in dt documentation
Changes in v5:
- changed binding to earliest known supported SoC sun6i-a31
- dropped unnece
Adds the sun6i_hwspinlock driver for the hardware spinlock unit found in
most of the sun6i compatible SoCs.
This unit provides at least 32 spinlocks in hardware. The implementation
supports 32, 64, 128 or 256 32bit registers. A lock can be taken by
reading a register and released by writing a 0 to
randconfig-a005-20210227
i386 randconfig-a006-20210227
i386 randconfig-a004-20210227
i386 randconfig-a001-20210227
i386 randconfig-a003-20210227
i386 randconfig-a002-20210227
i386 randconfig-a013
On Sat, 27 Feb 2021, Jason A. Donenfeld wrote:
> The CPU_MIPS64 and CPU_MIPS32 variables are supposed to be able to
> distinguish broadly between 64-bit and 32-bit MIPS CPUs. However, they
That is not true. The purpose of these options is to identify MIPS64 and
MIPS32 ISA processors respective
The Jitter RNG fast noise source implemented as part of the kernel
crypto API is queried for 256 bits of entropy at the time the seed
buffer managed by the LRNG is about to be filled.
CC: Torsten Duwe
CC: "Eric W. Biederman"
CC: "Alexander E. Patrakov"
CC: "Ahmed S. Darwish"
CC: "Theodore Y. T
In order to improve NUMA-locality when serving getrandom(2) requests,
allocate one DRNG instance per node.
The DRNG instance that is present right from the start of the kernel is
reused as the first per-NUMA-node DRNG. For all remaining online NUMA
nodes a new DRNG instance is allocated.
During b
The LRNG switchable DRNG support also allows the replacement of the hash
implementation used as conditioning component. The common generic hash
support code provides the required callbacks using the synchronous hash
implementations of the kernel crypto API.
All synchronous hash implementations sup
Parts of the LRNG are already covered by self-tests, including:
* Self-test of SP800-90A DRBG provided by the Linux kernel crypto API.
* Self-test of the PRNG provided by the Linux kernel crypto API.
* Raw noise source data testing including SP800-90B compliant
tests when enabling CONFIG_LRNG_
Using the LRNG switchable DRNG support, the SP800-90A DRBG extension is
implemented.
The DRBG uses the kernel crypto API DRBG implementation. In addition, it
uses the kernel crypto API SHASH support to provide the hashing
operation.
The DRBG supports the choice of either a CTR DRBG using AES-256,
Add runtime-pluggable support for all PRNGs that are accessible via
the kernel crypto API, including hardware PRNGs. The PRNG is selected
with the module parameter drng_name where the name must be one that the
kernel crypto API can resolve into an RNG.
This allows using of the kernel crypto API PR
Implement health tests for LRNG's slow noise sources as mandated by
SP-800-90B The file contains the following health tests:
- stuck test: The stuck test calculates the first, second and third
discrete derivative of the time stamp to be processed by the hash
for the per-CPU entropy pool. Only
The DRNG switch support allows replacing the DRNG mechanism of the
LRNG. The switching support rests on the interface definition of
include/linux/lrng.h. A new DRNG is implemented by filling in the
interface defined in this header file.
In addition to the DRNG, the extension also has to provide a
Hi,
The following patch set provides a different approach to /dev/random which
is called Linux Random Number Generator (LRNG) to collect entropy within
the Linux kernel. It provides the same API and ABI and can be used as a
drop-in replacement.
The LRNG implements at least all features of the exi
In an effort to provide a flexible implementation for a random number
generator that also delivers entropy during early boot time, allows
replacement of the deterministic random number generation mechanism,
implement the various components in separate code for easier
maintenance, and provide compli
Hi，
Sorry for my late reply.
> On Feb 9, 2021, at 9:17 PM, Odin Ugedal wrote:
>
>
> Hi! This looks quite useful, but I have a few quick thoughts. :)
>
> I know of a lot of people who would love this (especially some
> Kubernetes users)! I really like how this allow users to use cfs
> in a mor
The test interface allows a privileged process to capture the raw
unconditioned noise that is collected by the LRNG for statistical
analysis. Such testing allows the analysis how much entropy
the interrupt noise source provides on a given platform.
Extracted noise data is not used to seed the LRNG.
Hi Bjorn,
On 2021-02-27 00:44, Bjorn Andersson wrote:
> On Fri 26 Feb 12:23 CST 2021, Rob Clark wrote:
>
>
> The current logic picks one of:
> 1) is the compatible mentioned in qcom_smmu_impl_of_match[]
> 2) is the compatible an adreno
> 3) no quirks needed
>
> The change flips the order of the
To support the LRNG operation which uses the Jitter RNG separately
from the kernel crypto API, at a time where potentially the regular
memory management is not yet initialized, the Jitter RNG needs to
provide a state whose memory is defined at compile time. As only once
instance will ever be needed
This patch allows several DRBG functions to be called by the LRNG kernel
code paths outside the drbg.c file.
CC: Torsten Duwe
CC: "Eric W. Biederman"
CC: "Alexander E. Patrakov"
CC: "Ahmed S. Darwish"
CC: "Theodore Y. Ts'o"
CC: Willy Tarreau
CC: Matthew Garrett
CC: Vito Caputo
CC: Andreas
The LRNG sysctl interface provides the same controls as the existing
/dev/random implementation. These sysctls behave identically and are
implemented identically. The goal is to allow a possible merge of the
existing /dev/random implementation with this implementation which
implies that this patch
On 2021-02-27 00:16, Stephen Boyd wrote:
Quoting Sai Prakash Ranjan (2021-02-25 23:51:00)
On 2021-02-26 01:11, Stephen Boyd wrote:
> Quoting Sai Prakash Ranjan (2021-02-25 01:30:24)
>> Add a DT node for the AOSS QMP on SC7280 SoC.
>>
>> Signed-off-by: Sai Prakash Ranjan
>> ---
>> arch/arm64/bo
On 2021-02-27 00:15, Stephen Boyd wrote:
Quoting Sai Prakash Ranjan (2021-02-26 00:04:27)
On 2021-02-26 01:07, Stephen Boyd wrote:
> Quoting Sai Prakash Ranjan (2021-02-25 01:30:19)
>> Add a DT node for Last level cache (aka. system cache)
>> controller which provides control over the last level
Linux 5.12 fixes a regression.
Cross-filesystem copies (introduced in 5.3) were buggy.
Move the statements documenting cross-fs to BUGS.
Kernels 5.3..5.11 should be patched soon.
State version information for some errors related to this.
Reported-by: Luis Henriques
Reported-by: Amir Goldstein
I made some generalisations to this project.
It is now ITd X, (IT developments X), and think a generalization of
related media can be about 24-bit streaming.
And thus generalized media to this channel:
https://www.youtube.com/channel/UCmcb1ZPp4tW3eji-0Jaja9Q/videos
Serenity,
Ywe.
Linus,
I2C has three more bugfixes and one revert for you. I accidently applied
one patch too early.
Please pull.
Thanks,
Wolfram
The following changes since commit 2c87f7a38f930ef6f6a7bdd04aeb82ce3971b54b:
Merge tag 'pwm/for-5.12-rc1' of
git://git.kernel.org/pub/scm/linux/kernel/git/t
Commit 9b82f13e7ef3 ("kbuild: clamp SUBLEVEL to 255") breaks the build
if SUBLEVEL or PATCHLEVEL is empty.
Commit 78d3bb4483ba ("kbuild: Fix for empty SUBLEVEL
or PATCHLEVEL") fixed the issue by prepending a zero.
This time, we cannot take the same approach because we have C code:
#define LIN
On Wed, Feb 24, 2021 at 10:20:44AM -0800, Linus Torvalds wrote:
> On Wed, Feb 24, 2021 at 6:27 AM Greg KH wrote:
> >
> > [..] I've reverted that change at
> > the very end so we don't have to worry about regressions in 5.12.
>
> Side note: it would have been really nice to see links to the actua
Hi
Glad to contact you, my name is Reacheal and i wish to contact you for
an important purpose which can be of good benefit to you. I will give
you more details about me after receiving your reply indicating that
you have received this letter.
Regards,
Reacheal
Excerpts from Christoph Hellwig's message of February 16, 2021 3:47 am:
> How do these maxlen = 0 entries even survive the sysctl_check_table
> check?
maxlen!=0 is only checked for "default" handlers, e.g. proc_dostring,
proc_dointvec. it is not checked for non-default handlers, because some
of
On Sat, 27 Feb 2021 19:44:40 +0800
kernel test robot wrote:
> [ 20.216017] WARNING: CPU: 0 PID: 1 at kernel/trace/trace.c:8370
> create_trace_option_files (kbuild/src/consumer/kernel/trace/trace.c:8370
> (discriminator 1))
> [ 20.218480] Modules linked in:
> [ 20.219395] CPU: 0 PID: 1 Co
Hi Greg:
On Fri, Feb 26, 2021 at 07:40:56AM +0100, Greg KH wrote:
> On Fri, Feb 26, 2021 at 09:22:37AM +0800, Xu Yilun wrote:
> > On Mon, Feb 22, 2021 at 10:56:45AM -0800, Tom Rix wrote:
> > > Yilun,
> > >
> > > Is there anything outstanding or remaining to be done ?
> >
> > Sorry for late reply
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: 3fb6d0e00efc958d01c2f109c8453033a2d96796
commit: 930914b7d528fc6b0249bffc00564100bcf6ef75 powerpc/xive: Add a debugfs
file to dump internal XIVE state
config: powerpc64-randconfig-m031-20210226 (attached as
On Sat, Feb 27, 2021 at 10:57:33PM +0800, Xu Yilun wrote:
> Hi Greg:
>
> On Fri, Feb 26, 2021 at 07:40:56AM +0100, Greg KH wrote:
> > On Fri, Feb 26, 2021 at 09:22:37AM +0800, Xu Yilun wrote:
> > > On Mon, Feb 22, 2021 at 10:56:45AM -0800, Tom Rix wrote:
> > > > Yilun,
> > > >
> > > > Is there an
On Fri, Feb 26, 2021 at 2:24 PM Arnd Bergmann wrote:
>
> On Fri, Feb 26, 2021 at 9:13 AM Borislav Petkov wrote:
> >
> > On Thu, Feb 25, 2021 at 01:58:48PM -0800, Nick Desaulniers wrote:
> > > The config that reproduces it wasn't shared here; I wouldn't be
> > > surprised if this was found via ran
Attacks against vulnerable userspace applications with the purpose to break
ASLR or bypass canaries traditionally use some level of brute force with
the help of the fork system call. This is possible since when creating a
new process using fork its memory contents are the same as those of the
paren
On Fri, 26 Feb 2021 08:32:59 +0900
William Breathitt Gray wrote:
> On Sun, Feb 21, 2021 at 02:05:07PM +, Jonathan Cameron wrote:
> > On Fri, 19 Feb 2021 17:51:37 +0900
> > William Breathitt Gray wrote:
> >
> > > On Sun, Feb 14, 2021 at 06:09:13PM +, Jonathan Cameron wrote:
> > > > O
On Fri, 26 Feb 2021 09:03:48 +0900
William Breathitt Gray wrote:
> On Sun, Feb 21, 2021 at 03:51:40PM +, Jonathan Cameron wrote:
> > On Thu, 18 Feb 2021 19:32:16 +0900
> > William Breathitt Gray wrote:
> >
> > > On Sun, Feb 14, 2021 at 06:11:46PM +, Jonathan Cameron wrote:
> > > > O
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: 3fb6d0e00efc958d01c2f109c8453033a2d96796
commit: a0cd7a7c4bc004587d1f4785a320f58e72d880eb mm: simplify
free_highmem_page() and free_reserved_page()
date: 3 days ago
config: microblaze-randconfig-r006-20210
On Fri, Feb 26, 2021 at 12:54:02AM +0530, Jagan Teki wrote:
> Engicam C.TOUCH 2.0 is an EDIMM compliant general purpose Carrier
> board.
>
> Genaral features:
> - Ethernet 10/100
> - Wifi/BT
> - USB Type A/OTG
> - Audio Out
> - CAN
> - LVDS panel connector
>
> i.Core MX8M Mini is an EDIMM SoM bas
On Fri, Feb 26, 2021 at 12:54:03AM +0530, Jagan Teki wrote:
> i.Core MX8M Mini is an EDIMM SoM based on NXP i.MX8M Mini from Engicam.
>
> EDIMM2.2 Starter Kit is an EDIMM 2.2 Form Factor Capacitive Evaluation
> Board from Engicam.
>
> i.Core MX8M Mini needs to mount on top of this Evaluation boar
This patchset supports some dfl device drivers written in userspace.
In the patchset v1, the "driver_override" interface should be used to bind
the DFL UIO driver to DFL devices. But there is concern that the
"driver_override" interface is not OK itself.
In v2, we use a new matching algorithem. T
This patch adds description for UIO support for dfl devices on DFL
bus.
Signed-off-by: Xu Yilun
Reviewed-by: Tom Rix
Reviewed-by: Wu Hao
---
v2: no doc in v1, add it for v2.
v3: some documentation fixes.
v4: documentation change since the driver matching is changed.
v5: no change.
v6: improve t
Attacks against vulnerable userspace applications with the purpose to break
ASLR or bypass canaries traditionally use some level of brute force with
the help of the fork system call. This is possible since when creating a
new process using fork its memory contents are the same as those of the
paren
This patch supports the DFL drivers be written in userspace. This is
realized by exposing the userspace I/O device interfaces.
The driver now only binds the ether group feature, which has no irq. So
the irq support is not implemented yet.
Signed-off-by: Xu Yilun
Reviewed-by: Tom Rix
---
v9: swi
On Sat, Feb 27, 2021 at 11:27:03PM +0800, Xu Yilun wrote:
> This patch supports the DFL drivers be written in userspace. This is
> realized by exposing the userspace I/O device interfaces.
>
> The driver now only binds the ether group feature, which has no irq. So
> the irq support is not implemen
On Tue, 23 Feb 2021 17:37:40 +0100
Lars-Peter Clausen wrote:
> On 2/18/21 3:05 PM, Jonathan Cameron wrote:
> > On Wed, 17 Feb 2021 10:34:38 +0200
> > Alexandru Ardelean wrote:
> >
> >> From: Mircea Caprioru
> >>
> >> A PWM signal will be used as a trigger source to have a deterministic
> >> s
Add a security hook that allows a LSM to be notified when a task gets a
fatal signal. This patch is a previous step on the way to compute the
task crash period by the "brute" LSM (linux security module to detect
and mitigate fork brute force attack against vulnerable userspace
processes).
Signed-o
On Fri, 26 Feb 2021 12:11:42 +0100
Sean Nyekjaer wrote:
> Improve readability by using empty linies instead of extra spaces.
>
> Signed-off-by: Sean Nyekjaer
> ---
> drivers/iio/accel/mma8452.c | 120
> 1 file changed, 67 insertions(+), 53 deletions(-)
>
>
On Sat, Feb 27, 2021 at 3:59 PM Alejandro Colomar
wrote:
>
> Linux 5.12 fixes a regression.
>
> Cross-filesystem copies (introduced in 5.3) were buggy.
>
> Move the statements documenting cross-fs to BUGS.
> Kernels 5.3..5.11 should be patched soon.
>
> State version information for some errors re
1 - 100 of 264 matches
Mail list logo
