The patch trickled down from -stable to Ubuntu-3.2.0-40.63 and
Ubuntu-3.5.0-28.47
** Changed in: linux (Ubuntu Precise)
Status: New = Fix Released
** Changed in: linux (Ubuntu Quantal)
Status: New = Fix Released
--
You received this bug notification because you are a member of
I've gone ahead and opened up nominations for Precise, Quantal, and
Raring. For Raring, this patch is already included and available so
I'll go ahead and mark the Raring task Fix Released.
~/ubuntu-raring$ git describe --contains
98c350cda2c14a343d34ea01a3d9c24fea5ec66d
I can confirm that the patch was added into mainline kernel 3.6.
Here is the git commit:
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=98c350cda2c14a343d34ea01a3d9c24fea5ec66d
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Tags added: patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1092084
Title:
fscache 2GB file size limitation
To manage notifications about this bug go to:
** Package changed: linux-meta (Ubuntu) = linux (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1092084
Title:
fscache 2GB file size limitation
To manage notifications about this bug go to:
Log files not required for this bug. There is nothing to log!
** Changed in: linux (Ubuntu)
Status: Incomplete = New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1092084
Title:
fscache 2GB
Repeat. No log files should be required for this bug.
** Changed in: linux (Ubuntu)
Status: Incomplete = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1092084
Title:
fscache 2GB
Can you provide some information on the status of the patch with regards
to getting it merged upstream? Has it been sent upstream, what sort of
feedback has it received, is it getting applied to a subsystem
maintainer's tree, etc?
People affected by this bug are probably wondering why the kernel
