** No longer affects: iscsitarget (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1732746
Title:
[Trusty] iscsitarget-dkms 1.4.20.3+svn499-0ubuntu2.3 fails to build on
linux-lts-xenial
Hello,
Ran into this bug with iscsitarget 1.4.20.3+svn499-0ubuntu2.3, DKMS
failed to build.
The module built successfully with:
root@fleet-bunny:~# dpkg -l | grep iscsitarget-dkms
ii iscsitarget-dkms 1.4.20.3+svn499-0ubuntu2.5
root@fleet-bunny:~# dkms status
iscsitarget,
Hello Kleber, or anyone else affected,
Accepted iscsitarget into trusty-proposed. The package will build now
and be available at
https://launchpad.net/ubuntu/+source/iscsitarget/1.4.20.3+svn499-0ubuntu2.4
in a few hours, and then in the -proposed repository.
Please help us by testing this new
** Changed in: iscsitarget (Ubuntu)
Importance: Undecided => Medium
** Changed in: iscsitarget (Ubuntu Xenial)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: iscsitarget (Ubuntu Trusty)
Status: Triaged => In Progress
** Changed in: iscsitarget (Ubuntu Trusty)
Importance: Undecided => Medium
** Patch added: "iscsitarget_1.4.20.3+svn499-0ubuntu2.4.debdiff"
** Description changed:
+ [Impact]
+ iscsitarget-dkms will fail to build for 4.4.0 kernels on trusty, when their
ABI start with 1, like in -100 or -101.
+
+ [Test Case]
+ Install different kernels, including 3.13, and 4.4, and 4.4.0-78, 4.4.0-81
and 4.4.0-101. That means different kernel base
Ok cascardo, that means it is fixed in Xenial and you'll take Trusty by
moving your existing fix there then - thanks for the info - updating
tasks.
** Changed in: iscsitarget (Ubuntu)
Status: Triaged => Fix Released
** Changed in: iscsitarget (Ubuntu Xenial)
Status: Incomplete =>
It happens that the match was no good, and we replaced it with a grep
for the source that we uploaded for xenial. For some reason, we forgot
about trusty, so I am applying the same fix we added in xenial which
explains why linux-4.4.0-101-generic didn't hit the issue.
Cascardo.
--
You received
** 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/1732746
Title:
[Trusty] iscsitarget-dkms 1.4.20.3+svn499-0ubuntu2.3 fails to build on
linux-lts-xenial kernel
To manage
Hmm, bug 1701697 lists Xenial - I'd wait for Cascardos comment but would
expect the same breakage there.
** Changed in: iscsitarget (Ubuntu)
Assignee: (unassigned) => Thadeu Lima de Souza Cascardo (cascardo)
** Also affects: iscsitarget (Ubuntu Xenial)
Importance: Undecided
it worked in my local tests, but @cascardo since you wrote the initial
patch - could you give that a review?
Also I haven't checked but if you brought the same change to Xenial it
will need the same fix there.
** Patch added: "fix-lp1732746-trusty.debdiff"
So the problem came in with:
iscsitarget (1.4.20.3+svn499-0ubuntu2.3) trusty; urgency=medium
* d/p/(porting|compat|enable)-4.4.0-84.patch:
Add
Really the prototype of sock_recvmsg changed ??
I don't think so, but we need to find what is going on. ? (insert a little bit
of WTF here)
One odd thing - I see only in the bad case
applying patch compat-4.4.0-84.patch...patching file kernel/nthread.c
That is from:
Iniital checks on testbed setup
1. dkms build against Trusty base kernel 3.13.0-135-generic - ok
2. dkms build against current Trusty HWE kernel 4.4.0-98-generic - ok
3. build against proposed Trusty HWE kernel 4.4.0-101-generic - the reported
error
In detail it is:
I'm so glad we removed that later due to being unmaintained :-/
See bug 1613758
But for this lets take a look at what recent stable updates trigger ...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
15 matches
Mail list logo
