From: Samuel Dionne-Riel <samuel@dionne-riel.com>
To: linux-kernel@vger.kernel.org
Cc: torvalds@linux-foundation.org, graham@grahamc.com
Subject: Re: Userspace regression in LTS and stable kernels
Date: Wed, 13 Feb 2019 13:00:51 -0500 [thread overview]
Message-ID: <CAN1fySWPQnk26=8Qnf22Pw-N0tAFirwYs6n4uOJZ5LSH_aEuNQ@mail.gmail.com> (raw)
In-Reply-To: <CAN1fySViLgrLAHHfTHMef-Bkh73kUHKP-ava6TbgALeSE4LfFw@mail.gmail.com>
Sorry, had an issue when sending the e-mail and lost a bit of context
at the end, here's the missing bit:
---
[...]
Note: I wish to be CC'ed for answers and comments as I am not
subscribed to the mailing list, thanks.
References:
* NixOS bug 53672, https://github.com/NixOS/nixpkgs/issues/53672
* Bug 202497, https://bugzilla.kernel.org/show_bug.cgi?id=202497
Thanks,
On 13/02/2019, Samuel Dionne-Riel <samuel@dionne-riel.com> wrote:
> Hi,
>
> I am posting as a representative of the NixOS Linux distribution,
> about a userspace regression on 5.0-rc* which recently was backported
> to the 4.14.99, 4.19.21 and 4.20.8 current LTS and stable versions.
> The issue has been reported to the bug tracker, bug 202497, but seems
> to have gone unnoticed by the maintainers.
>
> The issue seems to break userspace for long-standing patterns in the
> NixOS distribution, with regards to use of the shebangs.
>
> Here is an example shebang causing an issue:
>
> #! /nix/store/mbwav8kz8b3y471wjsybgzw84mrh4js9-perl-5.28.1/bin/perl
> -I/nix/store/x6yyav38jgr924nkna62q3pkp0dgmzlx-perl5.28.1-File-Slurp-9999.25/lib/perl5/site_perl
> -I/nix/store/ha8v67sl8dac92r9z07vzr4gv1y9nwqz-perl5.28.1-Net-DBus-1.1.0/lib/perl5/site_perl
> -I/nix/store/dcrkvnjmwh69ljsvpbdjjdnqgwx90a9d-perl5.28.1-XML-Parser-2.44/lib/perl5/site_perl
> -I/nix/store/rmji88k2zz7h4zg97385bygcydrf2q8h-perl5.28.1-XML-Twig-3.52/lib/perl5/site_perl
>
> (The shebang was artificially wrapped spaces replaced by newlines)
>
> Another contributor tracked the regression it to commit
> 8099b047ecc431518b9bb6bdbba3549bbecdc343 in the 5.0-rc* tree.
>
> I bring no particular fix to the issue, but I believe it should at
> least be fast-tracked to a revert for the stable and LTS branches, and
> since 5.0 might drop soon, a solution worked on, or possibly a revert
> until one is figured out.
>
> Thanks,
>
> --
> — Samuel Dionne-Riel
>
--
— Samuel Dionne-Riel
next prev parent reply other threads:[~2019-02-13 18:00 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-13 17:57 Userspace regression in LTS and stable kernels Samuel Dionne-Riel
2019-02-13 18:00 ` Samuel Dionne-Riel [this message]
2019-02-13 23:36 ` Richard Weinberger
2019-02-14 0:41 ` Samuel Dionne-Riel
2019-02-14 0:54 ` Kees Cook
2019-02-14 1:27 ` Samuel Dionne-Riel
2019-02-14 1:35 ` Kees Cook
2019-02-14 3:16 ` Samuel Dionne-Riel
2019-02-14 0:41 ` Kees Cook
2019-02-14 17:56 ` Linus Torvalds
2019-02-14 20:20 ` Andrew Morton
2019-02-15 7:00 ` Greg Kroah-Hartman
2019-02-15 7:13 ` Greg Kroah-Hartman
2019-02-15 9:10 ` Michal Hocko
2019-02-15 9:20 ` Greg Kroah-Hartman
2019-02-15 9:42 ` Michal Hocko
2019-02-15 15:19 ` Sasha Levin
2019-02-15 15:52 ` Michal Hocko
2019-02-15 16:18 ` Samuel Dionne-Riel
2019-02-15 18:02 ` Sasha Levin
2019-02-15 18:00 ` Sasha Levin
2019-02-18 12:56 ` Michal Hocko
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAN1fySWPQnk26=8Qnf22Pw-N0tAFirwYs6n4uOJZ5LSH_aEuNQ@mail.gmail.com' \
--to=samuel@dionne-riel.com \
--cc=graham@grahamc.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).