** Changed in: linux (Ubuntu)
Status: Fix Committed => 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/1619918
Title:
lsattr 32bit does not work on 64bit kernel (Inapp
This bug was fixed in the package linux - 4.4.0-75.96
---
linux (4.4.0-75.96) xenial; urgency=low
* linux: 4.4.0-75.96 -proposed tracker (LP: #1684441)
* [Hyper-V] hv: util: move waiting for release to hv_utils_transport itself
(LP: #1682561)
- Drivers: hv: util: move wai
This bug was fixed in the package linux - 3.13.0-117.164
---
linux (3.13.0-117.164) trusty; urgency=low
* linux: 3.13.0-117.164 -proposed tracker (LP: #1680733)
* CVE-2017-6353
- sctp: deny peeloff operation on asocs with threads sleeping on it
* CVE-2017-5986
- sctp:
This bug was fixed in the package linux - 4.8.0-49.52
---
linux (4.8.0-49.52) yakkety; urgency=low
* linux: 4.8.0-49.52 -proposed tracker (LP: #1684427)
* [Hyper-V] hv: util: move waiting for release to hv_utils_transport itself
(LP: #1682561)
- Drivers: hv: util: move wa
found another similar bug 1678645
--
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/1619918
Title:
lsattr 32bit does not work on 64bit kernel (Inappropriate ioctl error)
Status in linux:
@Po-Hsu So, I did the work, yet you didn't act on it in time. Great!
Just confirms the impression of the Ubuntu kernel team I've had for a
while.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/
I'm happy to report that with kernel linux-
image-3.13.0-114-generic:amd64 and e2fsprogs:i386 on trusty the original
issue with lsattr is fixed and there are no regressions with "btrfs fi
show" or "btrfs sub snapshot".
For verification of the other kernels, is it sufficient for me to
install those
Po-Hsu Lin, I understand the kernel team is busy, but frankly, I don't
understand why I should be doing all the work when it wasn't me
introducing the regression. There are clear steps provided in how to
verify the problem and the fix. I don't think it should be beyond those
who get paid for this
Hello Rolf,
Our "Bug verification & Regression testing" slot for the current SRU cycle [1]
is between 19-Mar - 31-Mar
So it would be great if we can have your help before 31-Mar
Thank you very much!!
[1] https://wiki.ubuntu.com/KernelTeam/Newsletter/2017-03-21
--
You received this bug notifi
Thank you for releasing the test kernels. I will likely need a bit more
time for testing than the allotted five days as the internet in this
part of the world is inadequate. Please confirm the extension.
--
You received this bug notification because you are a member of Kernel
Packages, which is
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
yakkety' to 'verification-done-yakkety'. If the problem still exists,
change the tag 'verifi
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'. If the problem still exists,
change the tag 'verifica
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
trusty' to 'verification-done-trusty'. If the problem still exists,
change the tag 'verifica
** Changed in: linux (Ubuntu Trusty)
Status: In Progress => Fix Committed
--
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/1619918
Title:
lsattr 32bit does not work on 64bit kernel
** Changed in: linux (Ubuntu Yakkety)
Status: In Progress => Fix Committed
--
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/1619918
Title:
lsattr 32bit does not work on 64bit kernel
** Changed in: linux (Ubuntu Xenial)
Status: In Progress => Fix Committed
--
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/1619918
Title:
lsattr 32bit does not work on 64bit kernel
Thanks for all the help and testing, Rolf! I'll submit an SRU request
to have this patch in all Ubuntu releases.
** Changed in: linux (Ubuntu Zesty)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed
I'm happy to report that with the latest kernel from
http://kernel.ubuntu.com/~jsalisbury/lp1619918/ the original issue with
lsattr is fixed and there are no regressions with "btrfs fi show" or
"btrfs sub snapshot".
--
You received this bug notification because you are a member of Kernel
Packages
This fix from Jeff has landed in mainline and has been cc'd to stable:
commit 2a362249187a8d0f6d942d6e1d763d150a296f47
Author: Jeff Mahoney
Date: Mon Feb 6 19:39:09 2017 -0500
btrfs: fix btrfs_compat_ioctl failures on non-compat ioctls
I built a Xenial test kernel with this commit. Can y
On 08.02.2017 04:29, Joseph Salisbury wrote:
> There should be a fix coming from upstream shortly:
> https://lkml.org/lkml/2017/2/6/969
Great! Thanks.
** No longer affects: linux (Ubuntu Vivid)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscrib
There should be a fix coming from upstream shortly:
https://lkml.org/lkml/2017/2/6/969
--
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/1619918
Title:
lsattr 32bit does not work on 64bit k
How many more times will I have to do silly tests with predictable
results before this regression is finally fixed, Joseph? Just asking.
--
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/1619
On 07.01.2017 01:38, Luke-Jr wrote:
> On Friday, January 06, 2017 5:22:34 PM Joseph Salisbury wrote:
>> btrfs: bugfix: handle FS_IOC32_{GETFLAGS,SETFLAGS,GETVERSION} in
>> btrfs_ioctl
>>
>> However, this commit introduced a new regression. With this commit
>> applied, "btrfs fi show" no longer
Hi Luke,
A kernel bug report was opened against Ubuntu [0]. This bug was fixed
by the following commit in v4.7-rc1:
commit 4c63c2454eff996c5e27991221106eb511f7db38
Author: Luke Dashjr
Date: Thu Oct 29 08:22:21 2015 +
btrfs: bugfix: handle FS_IOC32_{GETFLAGS,SETFLAGS,GETVERSION} in
Thanks for the testing feedback, Rolf. I will ping upstream and the
patch Author to get feed back on the next steps. There may be another
fix for the new bug, or we may just want to revert it.
In the meantime, can you test the current 4.10-rc2 mainline kernel, to
confirm the new bug still exists
Thank you for providing the kernel. Here are the (as expected results)
results:
- lsattr bug is back
- "btrfs fi show" works
- snapshotting works
$ uname -a
Linux 1001P 4.4.0-53-generic #74~lp1619918Commit4c63c2454eReverted SMP Tue Dec
13 18:27:31 UT x86_64 x86_64 x86_64 GNU/Linux
--
You rece
I built a Xenial test kernel with commit 4c63c2454e reverted. The test
kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1619918
Can you test this kernel and see if it resolves the snapshotting bug?
It will probably re-introduce the original bug.
We can decide the next steps
** Bug watch added: Linux Kernel Bug Tracker #190221
http://bugzilla.kernel.org/show_bug.cgi?id=190221
** Also affects: kernel via
http://bugzilla.kernel.org/show_bug.cgi?id=190221
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member
adding to comment #36: mainline kernel 4.9.0-040900rc7-generic
#201611271731 does
- not have the problem with lsattr
- not have the problem with "btrfs fi show"
- INDEED have the problem with snapshotting
--
You received this bug notification because you are a member of Kernel
Packages, which is
The original bug is just an annoyance in my opinion and a cornercase as
well. From what I can tell it makes it impossible to get extended
attributes for any file, but only if you have a mixed i386/amd64
environment, run the amd64 kernel while having i386 e2fsprogs. The
impact of that should be pr
IOW, I think backing out the patch and reintroducing the original
problem is better than keeping the regression the fix introduced to
stick around.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net
mainline amd64 kernel 4.9.0-040900rc7-generic #201611271731 does not
have the problem with lsattr "btrfs fi show". It DOES have the problem
with creating a btrfs snapshot.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
h
If we back out the patch, your original bug will return, correct? Was
the original bug a regression? If it was, we can bisect to find the
commit that caused the original bug and then back out that commit and
commit 4c63c2454eff996.
The alternative is to perform the testing in comment #33, and se
You know, it's getting to be somewhat annoying. I have very limited
bandwidth here. Why don't you back out the patch already until a proper
solution is found? I will happily continue to test but as you can see
it does take me some time. The test case is pretty clear, why can you
not be bothered
Can you see if this new regression is also occurring with the current mainline
kernel:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.9-rc7/
Commit 4c63c2454eff996 fixes the original bug, but introduced a new bug.
Testing mainline will tell us if the new bug is already fixed in
mainline. If it
I've downloaded the kernel from
http://kernel.ubuntu.com/~jsalisbury/lp1619918/xenial/ and
https://launchpad.net/~canonical-kernel-security-
team/+archive/ubuntu/ppa/+build/11038082 now. Both kernels have the
same problem/regression (verified with "sudo btrfs fi show /")
--
You received this bug
If possible, it would be great if you could test the xenial kernel
posted in comment #22 as well as the Yakkety kernel, which is available
from:
https://launchpad.net/~canonical-kernel-security-
team/+archive/ubuntu/ppa/+build/11038082
--
You received this bug notification because you are a memb
I apologize for the delayed response, I was travelling.
Yes, the error message is the same as for the original report. Then it
was triggered by a call to lsattr, now by calling btrfs to create a
snapshot. The released kernels do not have the originally reported
problem with lsattr but regressed
One additional question. Are you only seeing this new regression on
Trusty, or does it also happen on Xenial? Would it be possible for you
to maybe test the Xenial and Yakkety kernels if it is unknown?
--
You received this bug notification because you are a member of Kernel
Packages, which is s
Also, using the 32 bit tools package with a 64 bit kernel, should be
fine.
--
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/1619918
Title:
lsattr 32bit does not work on 64bit kernel (Inapp
Thanks for testing, Rolf. The error message from the regression appears
to be the same error message you were getting when you originally opened
the bug, is that correct? You are just now getting it with other btrfs
operations, but the original bug is fixed?
--
You received this bug notification
Thank you for providing the test kernel. Unfortunately, it does not fix
the regression. I installed the trusty kernel. I did not install the
linux-tools-* packages as it would have uninstalled the trusty version
of linux-tools-generic. I have the i386 version of that package
installed but I run
Please ignore comment #24. Pasted in wrong bug.
--
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/1619918
Title:
lsattr 32bit does not work on 64bit kernel (Inappropriate ioctl error)
Sta
Did this issue start happening after an update/upgrade? Was there a
prior kernel version where you were not having this particular problem?
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.9 kernel[0
I also built a Trusty test kernel. It can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1619918/trusty
Can you also give this one a test?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpa
There is a Xenial test kernel with the original fix and a pick of commit
c5868f8. Can you give this test kernel a test? It can be downloaded
from:
http://kernel.ubuntu.com/~jsalisbury/lp1619918/xenial/
I'm in the process of building a Trusty test kernel as well and will
post a link to it when i
This appears to be the same error message you were getting when you
originally opened the bug, is that correct? You are just now getting it
with other btrfs operations now?
There may be some additional commits that are needed. I'll build a
Xenial and Trusty test kernel for testing.
** Changed i
** Changed in: linux (Ubuntu Xenial)
Status: Triaged => In Progress
** Changed in: linux (Ubuntu Xenial)
Assignee: Tim Gardner (timg-tpi) => Joseph Salisbury (jsalisbury)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux i
** Changed in: linux (Ubuntu Xenial)
Importance: Undecided => High
--
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/1619918
Title:
lsattr 32bit does not work on 64bit kernel (Inappropri
@rolf,
I apologize for this getting released. I/we care very much about
regressions. I take full responsibility for this happening.
In the future if there is an issue in verifying a fix, changing the
verification-needed- tag to verification-failed- would
help.
We will get this addressed asap.
-
The "I don't give a sh.."-attitude displayed here towards a regression
is shocking. Why do I even bother to test?
The regression is apparently much more severe to obot. I can no longer
take a snapshot of my btrfs filesystem.
$ sudo btrfs sub snapshot -r /mnt/LTS/@home/
/mnt/LTS/snapshots/home-
Brad, how can you set this to verified and release when that introduces
a pretty severe regression? OMG!!
** Tags added: regression-update
--
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/1
This bug was fixed in the package linux - 3.13.0-98.145
---
linux (3.13.0-98.145) trusty; urgency=low
* Fix GRO recursion overflow for tunneling protocols (LP: #1631287)
- tunnels: Don't apply GRO to multiple layers of encapsulation.
* CVE-2016-7039
- SAUCE: net: add recu
This bug was fixed in the package linux - 3.19.0-71.79
---
linux (3.19.0-71.79) vivid; urgency=low
* Fix GRO recursion overflow for tunneling protocols (LP: #1631287)
- tunnels: Don't apply GRO to multiple layers of encapsulation.
- gro: Allow tunnel stacking in the case of
This bug was fixed in the package linux - 3.19.0-71.79
---
linux (3.19.0-71.79) vivid; urgency=low
* Fix GRO recursion overflow for tunneling protocols (LP: #1631287)
- tunnels: Don't apply GRO to multiple layers of encapsulation.
- gro: Allow tunnel stacking in the case of
This bug was fixed in the package linux - 4.4.0-42.62
---
linux (4.4.0-42.62) xenial; urgency=low
* Fix GRO recursion overflow for tunneling protocols (LP: #1631287)
- tunnels: Don't apply GRO to multiple layers of encapsulation.
- gro: Allow tunnel stacking in the case of F
** Tags removed: verification-needed-vivid verification-needed-xenial
** Tags added: verification-done-vivid verification-done-xenial
--
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/1619918
Yes, regression from -96 to -97 verified on trusty.
** Tags removed: verification-done-trusty
** Tags added: regression-proposed verification-needed-trusty
** Tags removed: verification-needed-trusty
** Tags added: verification-done-trusty
** Changed in: linux (Ubuntu Trusty)
Status: Fix
I think there might be a regression with this kernel. "sudo btrfs fi
show" no longer works and only puts out "Btrfs v3.12"
--
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/1619918
Title:
Thanks. This works well in trusty.
** Tags removed: verification-needed-trusty
** Tags added: verification-done-trusty
--
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/1619918
Title:
lsa
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
trusty' to 'verification-done-trusty'.
If verification is not done by 5 working days from t
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
vivid' to 'verification-done-vivid'.
If verification is not done by 5 working days from tod
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'.
If verification is not done by 5 working days from t
** Changed in: linux (Ubuntu Vivid)
Status: In Progress => Fix Committed
--
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/1619918
Title:
lsattr 32bit does not work on 64bit kernel (
** Changed in: linux (Ubuntu Trusty)
Status: In Progress => Fix Committed
** Changed in: linux (Ubuntu Xenial)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bug
Test kernel at http://people.canonical.com/~rtg/lsattr-lp1619918/
--
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/1619918
Title:
lsattr 32bit does not work on 64bit kernel (Inappropriate
Commit 02da2d72174c61988eb4456b53f405e3ebdebce4 merged in v4.7
** Also affects: e2fsprogs (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: e2fsprogs (Ubuntu Trusty)
Importance: Undec
https://lists.ubuntu.com/archives/kernel-team/2016-September/079897.html
--
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/1619918
Title:
lsattr 32bit does not work on 64bit kernel (Inappro
Rolf, can you collect the requested logs? I think this is pointless
since it's pretty clear that there's a commit that just needs to be
backported, but that's between use and the Ubuntu Kernel team to figure
out. Or you can just use the upstream 4.7 kernel. :-)
--
You received this bug notifi
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Changed in: e2fsprogs (Ubuntu)
Status: New => Invalid
--
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/1
70 matches
Mail list logo