Santiago Vila | 18 Jun 2011 20:05
Picon
Favicon

Bug#630902: m4: FTBFS: FAIL: test-readlink (fwd)

Hello.

I have just received this from the Debian bug system.

I can't reproduce the failure on Debian "testing" (currently using
linux-image-2.6.38-2-amd64).

I can reproduce it, however, on the same Debian testing system if I
use the kernel currently available on "unstable" (linux-image-2.6.39-2-amd64).

Does this mean this is a kernel bug?

The build log says to report this failure here anyway, hence this report.

---------- Forwarded message ----------
From: Daniel Schepler <dschepler <at> gmail.com>
To: submit <at> bugs.debian.org
Date: Sat, 18 Jun 2011 08:47:10 -0700
Subject: Bug#630902: m4: FTBFS: FAIL: test-readlink

Source: m4
Version: 1.4.16-1
Severity: serious

From my pbuilder build log:

...
/usr/bin/make  check-TESTS
make[6]: Entering directory `/tmp/buildd/m4-1.4.16/tests'
make[7]: Entering directory `/tmp/buildd/m4-1.4.16/tests'
(Continue reading)

Santiago Vila | 19 Jun 2011 00:55
Picon
Favicon

Re: Bug#630902: m4: FTBFS: FAIL: test-readlink

Hi.

I confirm that m4 builds ok using vanilla 2.6.38.8 from kernel.org,
and it fails using vanilla 2.6.39.1 from kernel.org.

Santiago Vila | 19 Jun 2011 18:24
Picon
Favicon

Re: Bug#630902: m4: FTBFS: FAIL: test-readlink

For the record, this is what "git bisect" says:

65cfc6722361570bfe255698d9cd4dccaf47570d is the first bad commit

commit 65cfc6722361570bfe255698d9cd4dccaf47570d
Author: Al Viro <viro <at> zeniv.linux.org.uk>
Date:   Sun Mar 13 15:56:26 2011 -0400

    readlinkat(), fchownat() and fstatat() with empty relative pathnames

    For readlinkat() we simply allow empty pathname; it will fail unless
    we have dfd equal to O_PATH-opened symlink, so we are outside of
    POSIX scope here.  For fchownat() and fstatat() we allow AT_EMPTY_PATH;
    let the caller explicitly ask for such behaviour.

    Signed-off-by: Al Viro <viro <at> zeniv.linux.org.uk>


Gmane