Finally got around to debugging this, it turns out that a header file
had defined _FILE_OFFSET_BITS to 64 on my 32 bit builds. This is not a
kernel issue. so I'm going to close this.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
And reverting 0a46ef234756dca04623b7591e8ebb3440622f0b on 6.10.10 makes
the test run OK, without reverting it the kernel will hang.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2080853
T
$ git bisect bad
0a46ef234756dca04623b7591e8ebb3440622f0b is the first bad commit
commit 0a46ef234756dca04623b7591e8ebb3440622f0b (HEAD)
Author: Jan Kara
Date: Thu Mar 21 17:26:50 2024 +0100
ext4: do not create EA inode under buffer lock
ext4_xattr_set_entry() creates new EA inodes
I'm doing some bisect builds, but my system is a bit slow, so may take a
few days.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2080853
Title:
oracular 6.11 kernel regression with ext4
Correction, I meant to say: Course bisect, 5.15 OK, 6.5.0 onwards fail,
so this looks like a regression
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2056451
Title:
hfs: concurrent crea
Course bisect, 4.4 to 5.15 OK, 6.5.0 onwards fail, so this looks like a
regression
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2056451
Title:
hfs: concurrent create/unlink can trip -E
Yes, sorry, I pasted the text into the report and somehow forgot to put
sudo ./reproducer
I just wanted to clarify that the open with O_DIRECT and O_CREAT failure
should not leave the file around if the open call gets an error return
since this is not consistent with other file systems. Also it's
We've been here before with the minix file system:
https://lore.kernel.org/all/20220107133626.413379-1-qhjin@gmail.com/T/#u
in that scenario the file was not created on a file error when doing
O_CREAT | O_DIRECT
--
You received this bug notification because you are a member of Kernel
Packag
The file is created but the fd is -1. Surely the semantics of a O_CREAT
failure are a file that's not created.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2041670
Title:
tmpfs: O_DIR
The behavior for 32 bit is not what I expected,
offset: 4294967295 (0x), fallocate returned: 0
allocating at the boundary is OK, where as at 0xfbff it fails. I'd
expect at the boundary for it to fail too.
--
You received this bug notification because you are a member of Kernel
Packa
Tested and fails on m68k with ext4 and btrfs; occurs across arches and
across file systems.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1994079
Title:
fallocate on 32 bit boundary on
Tested and fails also on m68k Linux 4.16
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1994079
Title:
fallocate on 32 bit boundary on 32 bit systems with setrlimit fails to
generate S
12 matches
Mail list logo
