Launchpad has imported 7 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=484871.
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
** Changed in: linux-2.6 (Debian)
Status: New = Fix Released
--
Jaunty i386 popen() misbehaves on x86_64 kernel 2.6.26
https://bugs.launchpad.net/bugs/339743
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
I just checked sources of karmic and don't see there any prebuilt openvz
enabled kernels. I thought it was this bug that was preventing the
openvz-enablde kernel to be built and put into the repository.
--
Jaunty i386 popen() misbehaves on x86_64 kernel 2.6.26
This bug was fixed in the package linux - 2.6.27-14.41
---
linux (2.6.27-14.41) intrepid-proposed; urgency=low
[ Stefan Bader ]
* Revert SAUCE: input: Blacklist digitizers from joydev.c
- LP: #300143
linux (2.6.27-14.40) intrepid-proposed; urgency=low
[ Amit Kucheria ]
I have reproduced the bad return value of int $0x080 calls on the amd64
kernels in intrepid-updates, currently 2.6.27-14.37, and confirmed that
the kernels in intrepid-proposed, version 2.6.27-14.36 (needing to be
updated), fixes the issue. I've added a slightly modified testcase to
the
** Branch linked: lp:ubuntu/karmic/linux-ports
--
Jaunty i386 popen() misbehaves on x86_64 kernel 2.6.26
https://bugs.launchpad.net/bugs/339743
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Accepted linux into intrepid-proposed, the package will build now and be
available in a few hours. Please test and give feedback here. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed. Thank you in advance!
** Tags added: verification-needed
--
** Changed in: openvz-kernel
Status: Confirmed = Fix Released
--
Jaunty i386 popen() misbehaves on x86_64 kernel 2.6.26
https://bugs.launchpad.net/bugs/339743
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
** Changed in: glibc (Ubuntu Intrepid)
Status: New = Invalid
--
Jaunty i386 popen() misbehaves on x86_64 kernel 2.6.26
https://bugs.launchpad.net/bugs/339743
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
** Description changed:
+ SRU justification:
+
+ Impact: A bug in the syscall implementation can cause incorrect behavior
+ when trying to use syscalls that are not implemented.
+
+ Fix: Cherry pick from upstream to correctly return an error code in that
+ situation.
+
+ Testcase: see test
** Changed in: linux (Ubuntu Intrepid)
Importance: Undecided = Medium
--
Jaunty i386 popen() misbehaves on x86_64 kernel 2.6.26
https://bugs.launchpad.net/bugs/339743
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
This bug was fixed in the package linux - 2.6.28-10.32
---
linux (2.6.28-10.32) jaunty; urgency=low
[ Amit Kucheria ]
* Delete prepare-ppa-source script
[ Andy Isaacson ]
* SAUCE: FSAM7400: select CHECK_SIGNATURE
* SAUCE: LIRC_PVR150: depends on VIDEO_IVTV
- LP:
http://kernel.ubuntu.com/git?p=ubuntu/ubuntu-
jaunty.git;a=commit;h=73eec19c0301e46b46184cc8c16704ee6b9e26a5
** Changed in: linux (Ubuntu Jaunty)
Status: In Progress = Fix Committed
Target: None = ubuntu-9.04-beta
** Changed in: linux (Ubuntu Intrepid)
Assignee: (unassigned) =
Thanks. I tested the Jaunty amd64 kernel using the same bad-syscall-
test binary; it works correctly and fixes the problem. I will test the
Intrepid kernel soon.
--
Jaunty i386 popen() misbehaves on x86_64 kernel 2.6.26
https://bugs.launchpad.net/bugs/339743
You received this bug notification
Yep, the Intrepid amd64 kernel also fixes the problem.
** Changed in: linux (Ubuntu)
Status: Incomplete = In Progress
--
Jaunty i386 popen() misbehaves on x86_64 kernel 2.6.26
https://bugs.launchpad.net/bugs/339743
You received this bug notification because you are a member of Ubuntu
** Bug watch added: Red Hat Bugzilla #484871
https://bugzilla.redhat.com/show_bug.cgi?id=484871
** Also affects: fedora via
https://bugzilla.redhat.com/show_bug.cgi?id=484871
Importance: Unknown
Status: Unknown
--
Jaunty i386 popen() misbehaves on x86_64 kernel 2.6.26
** Bug watch added: OpenVZ Bugzilla #1150
http://bugzilla.openvz.org/show_bug.cgi?id=1150
** Also affects: openvz-kernel via
http://bugzilla.openvz.org/show_bug.cgi?id=1150
Importance: Unknown
Status: Unknown
--
Jaunty i386 popen() misbehaves on x86_64 kernel 2.6.26
** Changed in: openvz-kernel
Status: Unknown = Confirmed
** Changed in: fedora
Status: Unknown = Fix Released
--
Jaunty i386 popen() misbehaves on x86_64 kernel 2.6.26
https://bugs.launchpad.net/bugs/339743
You received this bug notification because you are a member of Ubuntu
It seems that the only sensible fix is to fix the kernel. If this will
affect new system calls then this does seem like something worth fixing
correctly.
** Changed in: linux (Ubuntu)
Assignee: (unassigned) = Andy Whitcroft (apw)
Status: Triaged = In Progress
** Changed in: glibc
@Anders -- I have pulled down that kernel fix and applied it to Jaunty
and Intrepid, could you test the kernels at the URL below and confirm
you are happy that they fix the issue to your satisfaction. Please
report any testing back here. Kernels are at the URLs below:
And the first commit after v2.6.26 on which the problem is NOT exhibited
is:
commit ed8cae8ba01348bfd8f4648dd807b04d7f08
Author: Ulrich Drepper drep...@redhat.com
Date: Wed Jul 23 21:29:30 2008 -0700
flag parameters: pipe
This patch introduces the new syscall pipe2 which is
It seems that __have_pipe2 is being incorrectly set to 1 when running
under kernels inside this range (8ab32bb..ed8cae8). Before 8ab32bb,
__have_pipe2 is set to -1 and the program works correctly; starting with
ed8cae8, pipe2() is actually implemented so the program works correctly.
--
Jaunty
Fascinating. The problem is that pipe2() is not actually returning -1
and setting errno = ENOSYS like it should. Instead, it is returning
331, which is __NR_pipe2, and leaving errno == 0.
This affects every x86_64 kernel from v2.6.26 (8ab32bb) through
v2.6.29-rc3, and was fixed by
commit
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
Jaunty i386 popen() misbehaves on x86_64 kernel 2.6.26
https://bugs.launchpad.net/bugs/339743
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
To fix this on the kernel side, please add commit
c09249f8d1b84344eca882547afdbffee8c09d14 to the Intrepid and Jaunty
kernels.
It may be possible for glibc to work around this problem on unpatched
kernels, though it would not be very pretty.
** Bug watch added: Debian Bug tracker #518921
It is possible this is triggered by the fact that we do indeed default
to running with auditing. That would make the problem moot for a
default Intrepid and Jaunty install. I would need a complelling use
case to support and SRU of this change given the default install is
unaffected.
--
Jaunty
Kernels starting with 2.6.27 do not have that particular problem with
popen() because they implement the pipe2() system call, so popen() does
not tickle the missing syscall detection bug. But the attached source
can be used to reproduce the missing syscall detection bug directly, by
displaying
** Changed in: linux (Ubuntu)
Importance: Undecided = Medium
Status: New = Triaged
--
Jaunty i386 popen() misbehaves on x86_64 kernel 2.6.26
https://bugs.launchpad.net/bugs/339743
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: linux-2.6 (Debian)
Status: Unknown = New
--
Jaunty i386 popen() misbehaves on x86_64 kernel 2.6.26
https://bugs.launchpad.net/bugs/339743
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
By defconfig, I meant defconfig plus CONFIG_IA32_EMULATION=y (without
which it is not possible to run the i386 binary); that is the only
option I changed.
--
Jaunty i386 popen() misbehaves on x86_64 kernel 2.6.26
https://bugs.launchpad.net/bugs/339743
You received this bug notification because
30 matches
Mail list logo
