From: Ritesh Raj Sarraf <rrs@debian.org>
To: stable@vger.kernel.org
Cc: debian-kernel@lists.debian.org,
Ritesh Raj Sarraf <rrs@debian.org>,
Ritesh Raj Sarraf <rrs@researchut.com>,
Richard Weinberger <richard@nod.at>
Subject: [PATCH] um: Don't hardcode path as it is architecture dependent
Date: Tue, 14 May 2019 15:46:57 +0530 [thread overview]
Message-ID: <20190514101656.10228-1-rrs@debian.org> (raw)
Dear Stable Team,
Request for inclusion into the stable branches of Linux. This change
went into 4.20 but 4.19 is the LTS release that many of the Linux
Vendors are rebasing on. Hence, it'd be nice to see this part of the LTS
releases, at least 4.19.
The current code fails to run on amd64 because of hardcoded reference to
i386
Signed-off-by: Ritesh Raj Sarraf <rrs@researchut.com>
Signed-off-by: Richard Weinberger <richard@nod.at>
---
arch/um/drivers/port_user.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/um/drivers/port_user.c b/arch/um/drivers/port_user.c
index 9a8e1b64c22e..5f56d11b886f 100644
--- a/arch/um/drivers/port_user.c
+++ b/arch/um/drivers/port_user.c
@@ -168,7 +168,7 @@ int port_connection(int fd, int *socket, int *pid_out)
{
int new, err;
char *argv[] = { "/usr/sbin/in.telnetd", "-L",
- "/usr/lib/uml/port-helper", NULL };
+ OS_LIB_PATH "/uml/port-helper", NULL };
struct port_pre_exec_data data;
new = accept(fd, NULL, 0);
--
2.20.1
next reply other threads:[~2019-05-14 10:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-14 10:16 Ritesh Raj Sarraf [this message]
2019-05-14 10:26 ` [PATCH] um: Don't hardcode path as it is architecture dependent Greg KH
2019-05-14 11:06 ` Ritesh Raj Sarraf
2019-05-14 12:18 ` Greg KH
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=20190514101656.10228-1-rrs@debian.org \
--to=rrs@debian.org \
--cc=debian-kernel@lists.debian.org \
--cc=richard@nod.at \
--cc=rrs@researchut.com \
--cc=stable@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.