[Bug 1853193] Re: copy_file_range test fails with linux 5.3+ on bionic

2020-11-02 Thread Launchpad Bug Tracker
This bug was fixed in the package glibc - 2.27-3ubuntu1.3

---
glibc (2.27-3ubuntu1.3) bionic; urgency=medium

  [ Balint Reczey ]
  * debian/gbp.conf: Add initial configuration
  * debian/control.in/main: Add Vcs-* pointing to Ubuntu packaging repository
  * arm64: Enable searching shared libraries in atomics/ on LSE HW
  * Ship arm64 variant with LSE support in libc6-lse (LP: #1885012)
  * Run tests of libc6-lse on HW supporting LSE
  * debian/patches/git-updates.diff: update from upstream stable branch
- pthread_cond_broadcast: Fix waiters-after-spinning case
- Fix SSe2-based memmove corrupting memory (CVE-2017-18269)
- Fix strstr() performance regression on Haswell processors
- Support Japanese new era "令和 (Reiwa)"
- io: Remove copy_file_range emulation
(LP: #1851263, #1858203, #1838327, #1797335, #1756209, #1853193)
  * XFAIL stdlib/tst-getrandom (LP: #1891403)
  * debian/testsuite-xfail-debian.mk: XFAIL new tst-support_descriptors

  [ Thadeu Lima de Souza Cascardo ]
  * tests: Make preadwritev2 invalid flags tests unsupported (LP: #1770480)

  [ Andreas Hasenack ]
  * branch-pthread_rwlock_trywrlock-hang-23844.patch:
nptl: Fix pthread_rwlock_try*lock stalls (Bug 23844) (LP: #1864864)

 -- Balint Reczey   Wed, 02 Sep 2020 11:18:37 +0200

** Changed in: glibc (Ubuntu Bionic)
   Status: Fix Committed => Fix Released

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2017-18269

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1853193

Title:
  copy_file_range test fails with linux 5.3+ on bionic

To manage notifications about this bug go to:
https://bugs.launchpad.net/glibc/+bug/1853193/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1853193] Re: copy_file_range test fails with linux 5.3+ on bionic

2020-09-11 Thread Thadeu Lima de Souza Cascardo
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
/autopkgtest-bionic/bionic/ppc64el/g/glibc/20200911_170104_5f83a@/log.gz

https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
/autopkgtest-bionic/bionic/ppc64el/g/glibc/20200911_180721_529c2@/log.gz

Comparing the two results, glibc 2.27-3ubuntu1.3 is definitively better.
So, marking as verified.

** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1853193

Title:
  copy_file_range test fails with linux 5.3+ on bionic

To manage notifications about this bug go to:
https://bugs.launchpad.net/glibc/+bug/1853193/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1853193] Re: copy_file_range test fails with linux 5.3+ on bionic

2020-09-10 Thread Steve Langasek
Hello Thadeu, or anyone else affected,

Accepted glibc into bionic-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/glibc/2.27-3ubuntu1.3
in a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
bionic to verification-done-bionic. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-bionic. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: glibc (Ubuntu Bionic)
   Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-bionic

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1853193

Title:
  copy_file_range test fails with linux 5.3+ on bionic

To manage notifications about this bug go to:
https://bugs.launchpad.net/glibc/+bug/1853193/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1853193] Re: copy_file_range test fails with linux 5.3+ on bionic

2020-07-02 Thread Bug Watch Updater
Launchpad has imported 6 comments from the remote bug at
https://sourceware.org/bugzilla/show_bug.cgi?id=24744.

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.launchpad.net/InterBugTracking.


On 2019-06-28T07:38:49+00:00 Florian Weimer wrote:

The kernel is evolving this interface rapidly, and our emulation is no
longer faithful: Among other things, we do not detect overlapping copies
(which is quite hard outside the kernel).  The kernel also plans to
support cross-device copies.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1853193/comments/0


On 2019-06-28T08:10:57+00:00 Cvs-commit wrote:

The master branch has been updated by Florian Weimer
:

https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=5a659ccc0ec217ab02a4c273a1f6d346a359560a

commit 5a659ccc0ec217ab02a4c273a1f6d346a359560a
Author: Florian Weimer 
Date:   Fri Jun 28 09:39:21 2019 +0200

io: Remove copy_file_range emulation [BZ #24744]

The kernel is evolving this interface (e.g., removal of the
restriction on cross-device copies), and keeping up with that
is difficult.  Applications which need the function should
run kernels which support the system call instead of relying on
the imperfect glibc emulation.

Reviewed-by: Adhemerval Zanella 

Reply at:
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1853193/comments/1


On 2019-06-28T08:11:21+00:00 Florian Weimer wrote:

Fixed in glibc 2.30.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1853193/comments/2


On 2019-07-09T08:24:03+00:00 Cvs-commit wrote:

The release/2.29/master branch has been updated by Florian Weimer
:

https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=da347f4aa3a67e018f19e51a7ece6add87dba5cf

commit da347f4aa3a67e018f19e51a7ece6add87dba5cf
Author: Florian Weimer 
Date:   Fri Jun 28 09:39:21 2019 +0200

io: Remove copy_file_range emulation [BZ #24744]

The kernel is evolving this interface (e.g., removal of the
restriction on cross-device copies), and keeping up with that
is difficult.  Applications which need the function should
run kernels which support the system call instead of relying on
the imperfect glibc emulation.

Reviewed-by: Adhemerval Zanella 
(cherry picked from commit 5a659ccc0ec217ab02a4c273a1f6d346a359560a)

Reply at:
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1853193/comments/3


On 2019-07-09T08:47:01+00:00 Cvs-commit wrote:

The release/2.27/master branch has been updated by Florian Weimer
:

https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=949da7f2fd0bc0f8dca91892e5c926504a7d11c2

commit 949da7f2fd0bc0f8dca91892e5c926504a7d11c2
Author: Florian Weimer 
Date:   Fri Jun 28 09:39:21 2019 +0200

io: Remove copy_file_range emulation [BZ #24744]

The kernel is evolving this interface (e.g., removal of the
restriction on cross-device copies), and keeping up with that
is difficult.  Applications which need the function should
run kernels which support the system call instead of relying on
the imperfect glibc emulation.

Reviewed-by: Adhemerval Zanella 
(cherry picked from commit 5a659ccc0ec217ab02a4c273a1f6d346a359560a)

Reply at:
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1853193/comments/4


On 2019-07-09T09:25:02+00:00 Cvs-commit wrote:

The release/2.28/master branch has been updated by Florian Weimer
:

https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=5f7fa9ac30048bcc1d883cf52a544ea182882ee9

commit 5f7fa9ac30048bcc1d883cf52a544ea182882ee9
Author: Florian Weimer 
Date:   Fri Jun 28 09:39:21 2019 +0200

io: Remove copy_file_range emulation [BZ #24744]

The kernel is evolving this interface (e.g., removal of the
restriction on cross-device copies), and keeping up with that
is difficult.  Applications which need the function should
run kernels which support the system call instead of relying on
the imperfect glibc emulation.

Reviewed-by: Adhemerval Zanella 
(cherry picked from commit 5a659ccc0ec217ab02a4c273a1f6d346a359560a)

Reply at:
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1853193/comments/5


** Changed in: glibc
   Status: Unknown => Fix Released

** Changed in: glibc
   Importance: Unknown => Medium

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1853193

Titl

[Bug 1853193] Re: copy_file_range test fails with linux 5.3+ on bionic

2020-07-02 Thread Mathew Hodson
This test was removed by upstream in recent versions.

** Changed in: glibc (Ubuntu)
   Status: Invalid => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1853193

Title:
  copy_file_range test fails with linux 5.3+ on bionic

To manage notifications about this bug go to:
https://bugs.launchpad.net/glibc/+bug/1853193/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1853193] Re: copy_file_range test fails with linux 5.3+ on bionic

2020-07-02 Thread Mathew Hodson
** Tags added: testcase

** Changed in: glibc (Ubuntu)
   Importance: Undecided => Medium

** Changed in: glibc (Ubuntu Bionic)
   Importance: Undecided => Medium

** Bug watch added: Sourceware.org Bugzilla #24744
   https://sourceware.org/bugzilla/show_bug.cgi?id=24744

** Also affects: glibc via
   https://sourceware.org/bugzilla/show_bug.cgi?id=24744
   Importance: Unknown
   Status: Unknown

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1853193

Title:
  copy_file_range test fails with linux 5.3+ on bionic

To manage notifications about this bug go to:
https://bugs.launchpad.net/glibc/+bug/1853193/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1853193] Re: copy_file_range test fails with linux 5.3+ on bionic

2020-06-29 Thread Thadeu Lima de Souza Cascardo
** Patch added: "fix for bionic"
   
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1853193/+attachment/5388335/+files/glibc_2.27-3ubuntu1.1.debdiff

** Description changed:

+ [Impact]
+ When tested against newer versions of linux, glibc tests will fail as it 
makes some assumptions about supportead features on the kernel.
+ 
+ [Fix]
+ Do not run the test that checks that copy_file_range will fail with EXDEV 
when done across devices.
+ 
+ [Test case]
+ Build glibc and run its tests on linux 5.3.
+ 
+ [Regression potential]
+ The same test is being ignored right now, we risk ignoring a failure on an 
older version of linux, like 4.15. However, that could happen because the 
feature is backported to said kernel. And we are currently ignoring the failure 
anyway.
+ 
+ ===
+ 
  copy_file_range on linux 5.3 now works across devices, so EXDEV is not
  returned anymore on those cases. glibc, however, tests that is the case
  and its autopkgtest fails, then, when running on linux 5.3.
  
  glibc 2.30 does not fail in that case anymore, so eoan glibc works fine
  on linux 5.3. However, the change on glibc 2.30 was to remove its
  userspace emulation entirely, and require users to fallback on their
  own.
  
  https://sourceware.org/bugzilla/show_bug.cgi?id=24744
  
  Linux commit 5dae222a5ff0c269730393018a5539cc970a4726.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1853193

Title:
  copy_file_range test fails with linux 5.3+ on bionic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1853193/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1853193] Re: copy_file_range test fails with linux 5.3+ on bionic

2020-06-18 Thread Thadeu Lima de Souza Cascardo
I am sending a proposed patch. I am building a package that includes
that patch on my ppa:cascardo/ppa. I will trigger tests against that and
verify this really fixes the issue.

** Patch added: "disable cross_device_failure test for copy_file_range"
   
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1853193/+attachment/5385113/+files/test-disable-copy_file_range-cross_device_failure.patch

** Changed in: glibc (Ubuntu Bionic)
   Status: New => In Progress

** Changed in: glibc (Ubuntu Bionic)
 Assignee: (unassigned) => Thadeu Lima de Souza Cascardo (cascardo)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1853193

Title:
  copy_file_range test fails with linux 5.3+ on bionic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1853193/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs