On 29/07/2024 22:18, Danila Tikhonov wrote:
> Add Soc ID table entries for Qualcomm SM7325 family.
>
> Signed-off-by: Danila Tikhonov
> ---
Reviewed-by: Krzysztof Kozlowski
Best regards,
Krzysztof
On 29/07/2024 22:18, Danila Tikhonov wrote:
> Add Qualcomm SM7325/SM7325P (yupik) SoC IDs.
>
> Signed-off-by: Danila Tikhonov
> ---
> include/dt-bindings/arm/qcom,ids.h | 2 ++
> 1 file changed, 2 insertions(+)
Reviewed-by: Krzysztof Kozlowski
Best regards,
Krzysztof
On 29/07/2024 22:18, Danila Tikhonov wrote:
> The SM7325 Linux Android firmware needs this workaround as well. Add it
> to the list.
>
> Signed-off-by: Danila Tikhonov
> ---
> drivers/usb/typec/ucsi/ucsi_glink.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/usb/typec/ucsi/ucs
On 29/07/2024 22:18, Danila Tikhonov wrote:
> The Qualcomm Snapdragon 778G/778G+/780G/782G uses CPUs named Kryo 670.
> Add the compatible string in the documentation.
>
> Signed-off-by: Danila Tikhonov
> ---
> Documentation/devicetree/bindings/arm/cpus.yaml | 1 +
Acked-by: Krzysztof Kozlowski
On 29/07/2024 22:18, Danila Tikhonov wrote:
> Add entry for Nothing Technology Limited (https://nl.nothing.tech/)
>
> Signed-off-by: Danila Tikhonov
> ---
Acked-by: Krzysztof Kozlowski
Best regards,
Krzysztof
On 29/07/2024 22:18, Danila Tikhonov wrote:
> From: Eugene Lepshy
>
> Add device tree for the Nothing Phone 1 (nothing,spacewar) smartphone
> which is based on the SM7325 SoC.
...
> +
> +&i2c2 {
> + clock-frequency = <10>;
> + status = "okay";
> +
> + /* nxp,tfa9873 (EAR speaker
On 29/07/2024 22:18, Danila Tikhonov wrote:
> Nothing Phone 1 (nothing,spacewar) is a smartphone based on the SM7325
> SoC.
>
> Signed-off-by: Danila Tikhonov
Reviewed-by: Krzysztof Kozlowski
Best regards,
Krzysztof
I have been testing Address Space Layout Randomization (ASLR)
functionalities with the kernel.randomize_va_space sysctl parameter.
According to the kernel documentation:
0 disables randomization.
1 randomizes the address of mmap base, stack, and VDSO page.
2 randomizes the heap address.
However,
This adds a Kconfig option and boot param to allow removing
the FOLL_FORCE flag from /proc/pid/mem write calls because
it can be abused.
The traditional forcing behavior is kept as default because
it can break GDB and some other use cases.
Previously we tried a more sophisticated approach allowin
According to '__reuseport_alloc()', annotate trailing VLA 'sock' of
'struct sock_reuseport' with '__counted_by()' and use convenient
'struct_size()' to simplify the math used in 'kzalloc()'.
Signed-off-by: Dmitry Antipov
---
include/net/sock_reuseport.h | 2 +-
net/core/sock_reuseport.c| 7 +
On Tue, Jul 30, 2024 at 04:45:29PM +0530, Prithivi Raj.S wrote:
> I have been testing Address Space Layout Randomization (ASLR)
> functionalities with the kernel.randomize_va_space sysctl parameter.
> According to the kernel documentation:
>
> 0 disables randomization.
> 1 randomizes the address o
On 29. Jul 2024, at 16:09, Gustavo A. R. Silva wrote:
> On 29/07/24 05:04, Thorsten Blum wrote:
>> Add the __counted_by compiler attribute to the flexible array member
>> inodes to improve access bounds-checking via CONFIG_UBSAN_BOUNDS and
>> CONFIG_FORTIFY_SOURCE.
>
> This change seems to be inc
Add the __counted_by compiler attribute to the flexible array member
inodes to improve access bounds-checking via CONFIG_UBSAN_BOUNDS and
CONFIG_FORTIFY_SOURCE.
Remove the now obsolete comment on the count field.
Refactor ext4_expand_inode_array() by assigning count before copying any
data using
On Tue, Jul 30, 2024 at 07:23:04PM +0200, Thorsten Blum wrote:
> Add the __counted_by compiler attribute to the flexible array member
> inodes to improve access bounds-checking via CONFIG_UBSAN_BOUNDS and
> CONFIG_FORTIFY_SOURCE.
>
> Remove the now obsolete comment on the count field.
>
> Refacto
On 30/07/24 11:23, Thorsten Blum wrote:
Add the __counted_by compiler attribute to the flexible array member
inodes to improve access bounds-checking via CONFIG_UBSAN_BOUNDS and
CONFIG_FORTIFY_SOURCE.
Remove the now obsolete comment on the count field.
Refactor ext4_expand_inode_array() by a
On 30/07/24 10:04, Dmitry Antipov wrote:
According to '__reuseport_alloc()', annotate trailing VLA 'sock' of
`socks` is a flexible-array member[1], not a VLA[2].
'struct sock_reuseport' with '__counted_by()' and use convenient
'struct_size()' to simplify the math used in 'kzalloc()'. >
Sig
From: Dmitry Antipov
Date: Tue, 30 Jul 2024 19:04:49 +0300
> According to '__reuseport_alloc()', annotate trailing VLA 'sock' of
> 'struct sock_reuseport' with '__counted_by()' and use convenient
> 'struct_size()' to simplify the math used in 'kzalloc()'.
>
> Signed-off-by: Dmitry Antipov
Revie
On Mon, Jul 29, 2024 at 11:18:07PM +0300, Danila Tikhonov wrote:
> This series of patches adds support for the Nothing Phone (1), identified
> as nothing,spacewar. The Nothing Phone (1) is built on the Qualcomm
> Snapdragon 778G+ (SM7325-AE, also known as yupik).
Your email header has this:
Conte
On 30. Jul 2024, at 20:12, Gustavo A. R. Silva wrote:
> On 30/07/24 11:23, Thorsten Blum wrote:
>> Add the __counted_by compiler attribute to the flexible array member
>> inodes to improve access bounds-checking via CONFIG_UBSAN_BOUNDS and
>> CONFIG_FORTIFY_SOURCE.
>> Remove the now obsolete comme
Add the __counted_by compiler attribute to the flexible array member
inodes to improve access bounds-checking via CONFIG_UBSAN_BOUNDS and
CONFIG_FORTIFY_SOURCE.
Remove the now obsolete comment on the count field.
Refactor ext4_expand_inode_array() by assigning count before copying any
data using
On 30/07/24 14:55, Thorsten Blum wrote:
Add the __counted_by compiler attribute to the flexible array member
inodes to improve access bounds-checking via CONFIG_UBSAN_BOUNDS and
CONFIG_FORTIFY_SOURCE.
Remove the now obsolete comment on the count field.
Refactor ext4_expand_inode_array() by a
Add the __counted_by compiler attribute to the flexible array member
inodes to improve access bounds-checking via CONFIG_UBSAN_BOUNDS and
CONFIG_FORTIFY_SOURCE.
Remove the now obsolete comment on the count field.
In ext4_expand_inode_array(), use struct_size() instead of offsetof()
and remove the
On Tue, Jul 30, 2024 at 6:25 AM Adrian Ratiu wrote:
>
> This adds a Kconfig option and boot param to allow removing
> the FOLL_FORCE flag from /proc/pid/mem write calls because
> it can be abused.
>
> The traditional forcing behavior is kept as default because
> it can break GDB and some other use
On Tue, 30 Jul 2024 at 16:09, Jeff Xu wrote:
>
> > + task = get_proc_task(file_inode(file));
> > + if (task) {
> > + ptrace_active = task->ptrace && task->mm == mm &&
> > task->parent == current;
>
> Do we need to call "read_lock(&tasklist_lock);"
On Tue, 30 Jul 2024 19:04:49 +0300 Dmitry Antipov wrote:
> - unsigned int size = sizeof(struct sock_reuseport) +
> - sizeof(struct sock *) * max_socks;
> - struct sock_reuseport *reuse = kzalloc(size, GFP_ATOMIC);
> + struct sock_reuseport *reuse =
> + kzal
According to '__reuseport_alloc()', annotate flexible array member
'sock' of 'struct sock_reuseport' with '__counted_by()' and use
convenient 'struct_size()' to simplify the math used in 'kzalloc()'.
Signed-off-by: Dmitry Antipov
---
v2: style (Jakub), title and commit message (Gustavo) adjustmen
26 matches
Mail list logo
