** Changed in: linux
Status: Confirmed => Fix Released
--
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
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
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
Hey Colin,
This looks to be intentional? Afaict, the -EFBIG might ceome directly
from vfs_fallocate():
/* Check for wrap through zero too */
if (((offset + len) > inode->i_sb->s_maxbytes) || ((offset + len) < 0))
return -EFBIG;
and you should see the same behavior
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
Launchpad has imported 1 comments from the remote bug at
https://bugzilla.kernel.org/show_bug.cgi?id=216626.
If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help
** Bug watch added: Linux Kernel Bug Tracker #216626
https://bugzilla.kernel.org/show_bug.cgi?id=216626
** Also affects: linux via
https://bugzilla.kernel.org/show_bug.cgi?id=216626
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member
occurs on 6.0 i386 kernels too
** Changed in: linux (Ubuntu)
Status: Incomplete => New
--
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
This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:
apport-collect 1994079
and then change the status of the bug to 'Confirmed'.
If, due to the nature
Public bug reported:
This is a corner case on 32 bit systems when using large file offsets,
fallocate and setrlimit.
Setting the RLIMIT_FSIZE with setrlimit to 0x and then
fallocating 1 or more bytes at the offset of 0x should make the
fallocate fail with EFBIG and generate a SIGX
11 matches
Mail list logo
