On 5/12/25 3:25 PM, Andrew Donnellan wrote:
On Wed, 2025-05-07 at 00:29 +0530, Srish Srinivasan wrote:
I think you should handle this as the existing code does: if it's
ENOENT, return 0, and for other codes print an error and return -
EIO.
Currently, the other layers in the boot stack assume
allmodconfiggcc-14.2.0
arc allnoconfiggcc-14.2.0
arc allyesconfiggcc-14.2.0
arc defconfiggcc-14.2.0
arc randconfig-001-20250512gcc-14.2.0
arc
Hi Arnd,
Do you know when you will be able to add GCC 15 to
https://mirrors.edge.kernel.org/pub/tools/crosstool/ ?
Thanks
Christophe
Le 10/05/2025 à 03:35, Paul Mackerras a écrit :
> Running Linux on Microwatt with a kernel compiled on an x86-64 system
> running Fedora 42 (using the packaged cr
Building vdso32 on power10 with pcrel leads to following errors:
VDSO32A arch/powerpc/kernel/vdso/gettimeofday-32.o
arch/powerpc/kernel/vdso/gettimeofday.S: Assembler messages:
arch/powerpc/kernel/vdso/gettimeofday.S:40: Error: syntax error; found
`@', expected `,'
14.2.0
arc allmodconfiggcc-14.2.0
arc allnoconfiggcc-14.2.0
arc allyesconfiggcc-14.2.0
arc defconfiggcc-14.2.0
arc randconfig-001-20250512gcc-14.2.0
arc rand
This patchset introduced two new syscalls file_getattr() and
file_setattr(). These syscalls are similar to FS_IOC_FSSETXATTR ioctl()
except they use *at() semantics. Therefore, there's no need to open the
file to get a fd.
These syscalls allow userspace to set filesystem inode attributes on
specia
Introduce new hooks for setting and getting filesystem extended
attributes on inode (FS_IOC_FSGETXATTR).
Cc: seli...@vger.kernel.org
Cc: Paul Moore
Signed-off-by: Andrey Albershteyn
---
fs/file_attr.c| 19 ---
include/linux/lsm_hook_defs.h | 2 ++
include/linux
These hooks are called on inode extended attribute retrieval/change.
Cc: seli...@vger.kernel.org
Cc: Paul Moore
Signed-off-by: Andrey Albershteyn
---
security/selinux/hooks.c | 14 ++
1 file changed, 14 insertions(+)
diff --git a/security/selinux/hooks.c b/security/selinux/hooks.c
From: Andrey Albershteyn
This patch moves function related to file extended attributes manipulations to
separate file. Just refactoring.
Signed-off-by: Andrey Albershteyn
---
fs/Makefile | 3 +-
fs/file_attr.c | 318 +++
fs/i
Future patches will add new syscalls which use these functions. As
this interface won't be used for ioctls only the EOPNOSUPP is more
appropriate return code.
This patch coverts return code from ENOIOCTLCMD to EOPNOSUPP for
vfs_fileattr_get and vfs_fileattr_set. To save old behavior
translate EOPN
Introduce new hooks for setting and getting filesystem extended
attributes on inode (FS_IOC_FSGETXATTR).
Cc: seli...@vger.kernel.org
Cc: Paul Moore
Signed-off-by: Andrey Albershteyn
---
fs/file_attr.c| 19 ---
include/linux/lsm_hook_defs.h | 2 ++
include/linux
From: Andrey Albershteyn
This patch moves function related to file extended attributes manipulations to
separate file. Just refactoring.
Signed-off-by: Andrey Albershteyn
---
fs/Makefile | 3 +-
fs/file_attr.c | 318 +++
fs/i
This patchset introduced two new syscalls file_getattr() and
file_setattr(). These syscalls are similar to FS_IOC_FSSETXATTR ioctl()
except they use *at() semantics. Therefore, there's no need to open the
file to get a fd.
These syscalls allow userspace to set filesystem inode attributes on
specia
On 2025-05-12 15:18:53, Andrey Albershteyn wrote:
> This patchset introduced two new syscalls file_getattr() and
> file_setattr(). These syscalls are similar to FS_IOC_FSSETXATTR ioctl()
> except they use *at() semantics. Therefore, there's no need to open the
> file to get a fd.
>
> These syscall
This will be helpful for file_get/setattr syscalls to convert
between fileattr and fsxattr.
Signed-off-by: Andrey Albershteyn
Reviewed-by: Jan Kara
---
fs/file_attr.c | 32 +---
include/linux/fileattr.h | 2 ++
2 files changed, 23 insertions(+), 11 deletio
On 2025-05-12 15:25:11, Andrey Albershteyn wrote:
> This patchset introduced two new syscalls file_getattr() and
> file_setattr(). These syscalls are similar to FS_IOC_FSSETXATTR ioctl()
> except they use *at() semantics. Therefore, there's no need to open the
> file to get a fd.
>
> These syscall
On 2025-05-12 15:22:52, Andrey Albershteyn wrote:
> Future patches will add new syscalls which use these functions. As
> this interface won't be used for ioctls only the EOPNOSUPP is more
> appropriate return code.
>
> This patch coverts return code from ENOIOCTLCMD to EOPNOSUPP for
> vfs_fileattr
When a device is opened by a userspace driver, via VFIO interface, DMA
window is created. This DMA window has TCE Table and a corresponding
data for userview of TCE table.
When the userspace driver closes the device, all the above infrastructure
is free'ed and the device control given back to kern
Thanks for the fix, applied to drm-misc-fixes
On 5/8/2025 3:06 PM, Markus Burri wrote:
> Use the effective written size instead of original size as index for zero
> termination. If the input from user-space is to larger and the input is
> truncated, the original size is out-of-bound.
> Since there
Reviewed-by: Jacek Lawrynowicz
On 5/8/2025 3:06 PM, Markus Burri wrote:
> Use the effective written size instead of original size as index for zero
> termination. If the input from user-space is to larger and the input is
> truncated, the original size is out-of-bound.
> Since there is an upfront
On Wed, 07 May 2025 10:42:31 -0500, Rob Herring (Arm) wrote:
> The reserved-memory.yaml reference needs the full path. No warnings were
> generated because the example has the wrong compatible string, so fix
> that too.
>
> Fixes: 304a90c4f75d ("dt-bindings: soc: fsl: Convert q(b)man-* to yaml
On 5/12/2025 6:25 AM, Andrey Albershteyn wrote:
> Introduce new hooks for setting and getting filesystem extended
> attributes on inode (FS_IOC_FSGETXATTR).
>
> Cc: seli...@vger.kernel.org
> Cc: Paul Moore
>
> Signed-off-by: Andrey Albershteyn
> ---
> fs/file_attr.c| 19 +
On Wed, 2025-05-07 at 21:18 +0530, Srish Srinivasan wrote:
> > We expect SB_VERSION to always be world-readable, I think? In which
> > case it shouldn't return H_AUTHORITY / -EPERM, ever, and if it does
> > that's an error which should be handled as an error. Or am I
> > misinterpreting the spec he
On Wed, 2025-05-07 at 00:29 +0530, Srish Srinivasan wrote:
> > I think you should handle this as the existing code does: if it's
> > ENOENT, return 0, and for other codes print an error and return -
> > EIO.
> Currently, the other layers in the boot stack assume static key mode
> for
> any failure
On 06. 05. 25, 15:41, Thomas Gleixner wrote:
On Wed, Mar 19 2025 at 10:28, Jiri Slaby wrote:
Hi,
tl;dr if patches are agreed upon, I ask subsys maintainers to take the
respective ones via their trees (as they are split per subsys), so that
the IRQ tree can take only the rest. That would minimi
25 matches
Mail list logo
