Bug#918188: linux: FTBFS on arm64

[Noah Meyerhans]

On Fri, Jan 04, 2019 at 06:57:21AM +0100, Salvatore Bonaccorso wrote:
> >   LD  vmlinux.o
> >   MODPOST vmlinux.o
> >   GEN .version
> >   CHK include/generated/compile.h
> >   UPD include/generated/compile.h
> >   CC  init/version.o
> >   LD  init/built-in.o
> > ./drivers/firmware/efi/libstub/lib.a(arm64-stub.stub.o): In function 
> > `handle_kernel_image':
> > ./debian/build/build_arm64_none_arm64/./drivers/firmware/efi/libstub/arm64-stub.c:63:
> >  undefined reference to `__efistub__GLOBAL_OFFSET_TABLE_'
> > ld: ./drivers/firmware/efi/libstub/lib.a(arm64-stub.stub.o): relocation 
> > R_AARCH64_ADR_PREL_PG_HI21 against external symbol 
> > `__efistub__GLOBAL_OFFSET_TABLE_' can not be used when making a shared 
> > object; recompile with -fPIC
> > /<>/Makefile:1010: recipe for target 'vmlinux' failed
> > make[5]: *** [vmlinux] Error 1
> > Makefile:152: recipe for target 'sub-make' failed
> > make[4]: *** [sub-make] Error 2
> > Makefile:24: recipe for target '__sub-make' failed
> > make[3]: *** [__sub-make] Error 2
> > make[3]: Leaving directory 
> > '/<>/debian/build/build_arm64_none_arm64'
> > debian/rules.real:190: recipe for target 
> > 'debian/stamps/build_arm64_none_arm64' failed
> > make[2]: *** [debian/stamps/build_arm64_none_arm64] Error 2
> > make[2]: Leaving directory '/<>'
> > debian/rules.gen:400: recipe for target 'build-arch_arm64_none_arm64_real' 
> > failed
> > make[1]: *** [build-arch_arm64_none_arm64_real] Error 2
> > make[1]: Leaving directory '/<>'
> > debian/rules:41: recipe for target 'build-arch' failed
> > make: *** [build-arch] Error 2
> > dpkg-buildpackage: error: debian/rules build-arch gave error exit status 2
> 
> https://buildd.debian.org/status/fetch.php?pkg=linux=arm64=4.9.144-1=1546572157=0

The problem was introduced with upstream commit
27b5ebf61818749b3568354c64a8ec2d9cd5ecca. Reverting that commit fixes
the build, but there may be a better option.



signature.asc
Description: PGP signature

Bug#918271: marked as done (Why does Debian start every process with low max priority in Linux)

[Debian Bug Tracking System]

Your message dated Sat, 05 Jan 2019 05:08:36 +
with message-id <3b7782bd4738bcdbbd32fe6708e82a76dc0071da.ca...@decadent.org.uk>
and subject line Re: Bug#918271: Why does Debian start every process with low 
max priority in Linux
has caused the Debian Bug report #918271,
regarding Why does Debian start every process with low max priority in Linux
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
918271: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918271
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:linux
Version: 4.19.13-1
Severity: normal
Tags: a11y

I update by apt-mirror Debian repository on local disk. Next I update by apt my 
local Debian. From time to time I copy a repository to another local disk by 
command «#cp -Rp . 'to_some_directory'" by size 340Gb.

I have : Intel(R) Core(TM) i7-3820 CPU @ 3.60GHz multi-core (c=4), 
hyper-threaded (t=2). 32 Gb memory.

Before appearance a kernel «linux-image-4.19.0-1-amd64 Linux 4.19 for 64-bit 
PCs (signed) ver. 4.19.13-1»  in flowing copy period the start of new processes 
start, the switch between current processes and the work in they is very slow 
down and it is impossible to work in Debian. After apperance a kernel  4.19 the 
problen is smoothed out to an acceptable, but still the start of new processes 
holds some seconds.

Why does Debian start every process with low max priority in Linux 20 , but not 
19 or 18 at least because it needs to begin the process with more low priority 
or reduce there priority if it will be need.
--- End Message ---
--- Begin Message ---
This is a bug tracking system, not a support forum.  See <
https://www.debian.org/support>.

Ben.

-- 
Ben Hutchings
Absolutum obsoletum. (If it works, it's out of date.) - Stafford Beer



signature.asc
Description: This is a digitally signed message part
--- End Message ---

Processed: reassign 918142 to udev

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> reassign 918142 udev
Bug #918142 [src:linux] linux-image-4.19.0-1-amd64: Can no longer disable the 
touchscreen module
Bug reassigned from package 'src:linux' to 'udev'.
No longer marked as found in versions linux/4.19.12-1.
Ignoring request to alter fixed versions of bug #918142 to the same values 
previously set
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
918142: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918142
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: tagging 918142

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 918142 - moreinfo
Bug #918142 [src:linux] linux-image-4.19.0-1-amd64: Can no longer disable the 
touchscreen module
Removed tag(s) moreinfo.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
918142: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918142
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#918271: Why does Debian start every process with low max priority in Linux

[Сергей Фёдоров]

Package: src:linux
Version: 4.19.13-1
Severity: normal
Tags: a11y

I update by apt-mirror Debian repository on local disk. Next I update by apt my 
local Debian. From time to time I copy a repository to another local disk by 
command «#cp -Rp . 'to_some_directory'" by size 340Gb.

I have : Intel(R) Core(TM) i7-3820 CPU @ 3.60GHz multi-core (c=4), 
hyper-threaded (t=2). 32 Gb memory.

Before appearance a kernel «linux-image-4.19.0-1-amd64 Linux 4.19 for 64-bit 
PCs (signed) ver. 4.19.13-1»  in flowing copy period the start of new processes 
start, the switch between current processes and the work in they is very slow 
down and it is impossible to work in Debian. After apperance a kernel  4.19 the 
problen is smoothed out to an acceptable, but still the start of new processes 
holds some seconds.

Why does Debian start every process with low max priority in Linux 20 , but not 
19 or 18 at least because it needs to begin the process with more low priority 
or reduce there priority if it will be need.

Bug#918140: Confirming linux-image-4.17.0-3-amd64 works

[Tyler Schwend]

Just confirming that linux-image-4.17.0-3-amd64 is working fine. Almost 24
hours of uptime whereas I couldn't get 2 hours on
linux-image-4.19.0-1-amd64.

I am using the same kernel options on both kernels, so I'm not sure if 4.17
works without disabling APSTE or not.

Bug#917533: linux-image-4.9.0-8-marvell: nfs-kernel-server leaks ports and triggers rkhunter/unhide-tcp

[Ian Campbell]

On Fri, 2018-12-28 at 09:58 +, Ian Campbell wrote:
> I'm next going to reboot into my locally built kernel with the 
> (likely/hopeful)
> fix applied. I'll follow up in a few days (maybe a week to be sure) if I don't
> see this issue recurring. If it is looking positive at that point I'll also
> ping davem and Trond to requests upstream backports.

It's been a week and I've not had recurrence of the issue, previously I
was seeing it every 2-3 days.

I'm attaching the patch I was using which I described earlier as:

> pkg-kernel git's stretch branch at d9cfad89feb2 ('Revert
> "tracing: Use strlcpy() instead of strcpy() in 
> __trace_find_cmdline()"') plus backports of:
> 
> 8d1b8c62e080 SUNRPC: Refactor TCP socket timeout code into a helper function
> 3ffbc1d65583 net/sunrpc/xprt_sock: fix regression in connection error 
> reporting.
> 9b30889c548a SUNRPC: Ensure we always close the socket after a connection 
> shuts down

I'll also ping upstream about a possible stable backport shortly.

Ian.
From 3f47e65ec1a5b9c456cda19655759d43ec476988 Mon Sep 17 00:00:00 2001
From: Ian Campbell 
Date: Tue, 25 Dec 2018 09:28:51 +
Subject: [PATCH] Backport patches to stop NFS kernel server leak

This tweaks rkhunters hidden port checks
---
 debian/changelog  |  3 +
 ...-always-close-the-socket-after-a-con.patch | 82 +
 ...TCP-socket-timeout-code-into-a-helpe.patch | 88 +++
 ...sock-fix-regression-in-connection-er.patch | 50 +++
 debian/patches/series |  3 +
 5 files changed, 226 insertions(+)
 create mode 100644 debian/patches/bugfix/all/SUNRPC-Ensure-we-always-close-the-socket-after-a-con.patch
 create mode 100644 debian/patches/bugfix/all/SUNRPC-Refactor-TCP-socket-timeout-code-into-a-helpe.patch
 create mode 100644 debian/patches/bugfix/all/net-sunrpc-xprt_sock-fix-regression-in-connection-er.patch

diff --git a/debian/changelog b/debian/changelog
index da70135267ba..1c6b7e88734a 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -734,6 +734,9 @@ linux (4.9.144-1) UNRELEASED; urgency=medium
   * Refresh inet-frags-avoid-abi-change-in-4.9.134.patch for context changes
 in 4.9.142
 
+  [ Ian Campbell ]
+  * Backport NFS fixes to not trigger rkhunter hidden port scan.
+
  -- Ben Hutchings   Sat, 08 Dec 2018 20:53:57 +
 
 linux (4.9.135-1) stretch; urgency=medium
diff --git a/debian/patches/bugfix/all/SUNRPC-Ensure-we-always-close-the-socket-after-a-con.patch b/debian/patches/bugfix/all/SUNRPC-Ensure-we-always-close-the-socket-after-a-con.patch
new file mode 100644
index ..5e99fe42a090
--- /dev/null
+++ b/debian/patches/bugfix/all/SUNRPC-Ensure-we-always-close-the-socket-after-a-con.patch
@@ -0,0 +1,82 @@
+From b0494c706325fdd1ec6b4fdef1d1f0cc12f4f4ad Mon Sep 17 00:00:00 2001
+From: Trond Myklebust 
+Date: Mon, 5 Feb 2018 10:20:06 -0500
+Subject: [PATCH 3/3] SUNRPC: Ensure we always close the socket after a
+ connection shuts down
+
+Ensure that we release the TCP socket once it is in the TCP_CLOSE or
+TCP_TIME_WAIT state (and only then) so that we don't confuse rkhunter
+and its ilk.
+
+Signed-off-by: Trond Myklebust 
+(cherry picked from commit 9b30889c548a4d45bfe6226e58de32504c1d682f)
+---
+ net/sunrpc/xprtsock.c | 23 ++-
+ 1 file changed, 10 insertions(+), 13 deletions(-)
+
+diff --git a/net/sunrpc/xprtsock.c b/net/sunrpc/xprtsock.c
+index d5422d479a22..5be417ed1311 100644
+--- a/net/sunrpc/xprtsock.c
 b/net/sunrpc/xprtsock.c
+@@ -798,13 +798,6 @@ static void xs_sock_reset_connection_flags(struct rpc_xprt *xprt)
+ 	smp_mb__after_atomic();
+ }
+ 
+-static void xs_sock_mark_closed(struct rpc_xprt *xprt)
+-{
+-	xs_sock_reset_connection_flags(xprt);
+-	/* Mark transport as closed and wake up all pending tasks */
+-	xprt_disconnect_done(xprt);
+-}
+-
+ /**
+  * xs_error_report - callback to handle TCP socket state errors
+  * @sk: socket
+@@ -824,9 +817,6 @@ static void xs_error_report(struct sock *sk)
+ 	err = -sk->sk_err;
+ 	if (err == 0)
+ 		goto out;
+-	/* Is this a reset event? */
+-	if (sk->sk_state == TCP_CLOSE)
+-		xs_sock_mark_closed(xprt);
+ 	dprintk("RPC:   xs_error_report client %p, error=%d...\n",
+ 			xprt, -err);
+ 	trace_rpc_socket_error(xprt, sk->sk_socket, err);
+@@ -1619,9 +1609,11 @@ static void xs_tcp_state_change(struct sock *sk)
+ 		if (test_and_clear_bit(XPRT_SOCK_CONNECTING,
+ 	>sock_state))
+ 			xprt_clear_connecting(xprt);
++		clear_bit(XPRT_CLOSING, >state);
+ 		if (sk->sk_err)
+ 			xprt_wake_pending_tasks(xprt, -sk->sk_err);
+-		xs_sock_mark_closed(xprt);
++		/* Trigger the socket release */
++		xs_tcp_force_close(xprt);
+ 	}
+  out:
+ 	read_unlock_bh(>sk_callback_lock);
+@@ -2227,14 +2219,19 @@ static void xs_tcp_shutdown(struct rpc_xprt *xprt)
+ {
+ 	struct sock_xprt *transport = container_of(xprt, struct sock_xprt, xprt);
+ 	struct socket *sock = transport->sock;
++	int skst = transport->inet ? transport->inet->sk_state : TCP_CLOSE;
+ 
+ 

linux-image-4.19.0-1-amd64: Thanks for packaging linux-image-4.19.0-1-amd64!

[Michal Suchanek]

Hello,

I noticed there is a STR regression in 4.19.12 due to xhci_pci failing
suspend on the XHCI root hub.

And before even reporting the bug 4.19.13 is out and loading xhci_pci
from the updated kernel resolves the issue.

It's wonderful when bugs are resolved this quicky :)

Thanks

Michal

Bug#918103: ipv6: Consider sk_bound_dev_if when binding a socket to an address

[Ralf Jung]

Hi,

> Once a version uploaded to sid, migrates to testing, it can be
> prepared for stable-backports based on that.
> 
> So what will need to happen here: upload of 4.19.13-2 to unstable
> (actually possibly only >= 4.19.14-1 if we do not have pressure to
> upload 4.19.13-2), then wait it migrates to testing, then the
> stretch-backports upload can be done.
> 
> Hope this helps,

It does, thanks. :)

Kind regards,
Ralf

Bug#918103: ipv6: Consider sk_bound_dev_if when binding a socket to an address

[Salvatore Bonaccorso]

Hi Ralf,

On Fri, Jan 04, 2019 at 11:42:26AM +0100, Ralf Jung wrote:
> Hi,
> 
> > On Thu, Jan 03, 2019 at 12:14:05PM +0100, Ralf Jung wrote:
> >> Package: linux-image-4.18.0-0.bpo.3-amd64
> >> Version: 4.18.20-2~bpo9+1
> >> Severity: normal
> >> Tags: upstream
> >>
> >> Dear Maintainer,
> >>
> >> I reported an upstream bug at 
> >>  that got a patch 
> >> submitted with .
> >> It would be great to have this patch applied to the next Debian kernel 
> >> update.
> > 
> > Queued it up for our next sid upload, as per
> > https://salsa.debian.org/kernel-team/linux/commit/c91e16558f8fe6f1fa4df2faa27ad69afa397d03
> 
> Thanks a lot!
> 
> How are updates to the stable-backports kernel usually handled?

Once a version uploaded to sid, migrates to testing, it can be
prepared for stable-backports based on that.

So what will need to happen here: upload of 4.19.13-2 to unstable
(actually possibly only >= 4.19.14-1 if we do not have pressure to
upload 4.19.13-2), then wait it migrates to testing, then the
stretch-backports upload can be done.

Hope this helps,

Regards,
Salvatore

Bug#918103: ipv6: Consider sk_bound_dev_if when binding a socket to an address

[Ralf Jung]

Hi,

> On Thu, Jan 03, 2019 at 12:14:05PM +0100, Ralf Jung wrote:
>> Package: linux-image-4.18.0-0.bpo.3-amd64
>> Version: 4.18.20-2~bpo9+1
>> Severity: normal
>> Tags: upstream
>>
>> Dear Maintainer,
>>
>> I reported an upstream bug at 
>>  that got a patch 
>> submitted with .
>> It would be great to have this patch applied to the next Debian kernel 
>> update.
> 
> Queued it up for our next sid upload, as per
> https://salsa.debian.org/kernel-team/linux/commit/c91e16558f8fe6f1fa4df2faa27ad69afa397d03

Thanks a lot!

How are updates to the stable-backports kernel usually handled?

Kind regards,
Ralf

Processed: Re: Bug#918103: ipv6: Consider sk_bound_dev_if when binding a socket to an address

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + fixed-upstream pending patch
Bug #918103 [src:linux] ipv6: Consider sk_bound_dev_if when binding a socket to 
an address
Added tag(s) pending and patch.

-- 
918103: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918103
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#918103: ipv6: Consider sk_bound_dev_if when binding a socket to an address

[Salvatore Bonaccorso]

Control: tags -1 + fixed-upstream pending patch

Hi Ralf,

On Thu, Jan 03, 2019 at 12:14:05PM +0100, Ralf Jung wrote:
> Package: linux-image-4.18.0-0.bpo.3-amd64
> Version: 4.18.20-2~bpo9+1
> Severity: normal
> Tags: upstream
> 
> Dear Maintainer,
> 
> I reported an upstream bug at 
>  that got a patch 
> submitted with .
> It would be great to have this patch applied to the next Debian kernel update.

Queued it up for our next sid upload, as per
https://salsa.debian.org/kernel-team/linux/commit/c91e16558f8fe6f1fa4df2faa27ad69afa397d03
.

Regards,
Salvatore

Processed: tagging 918103

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 918103 + fixed-upstream
Bug #918103 [src:linux] ipv6: Consider sk_bound_dev_if when binding a socket to 
an address
Added tag(s) fixed-upstream.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
918103: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918103
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#918142: linux-image-4.19.0-1-amd64: Can no longer disable the touchscreen module

[fakefur]

makes no difference
i cannot disable the touchscreen


On Thu, 2019-01-03 at 20:15 +, Ben Hutchings wrote:
> Control: tag -1 moreinfo
> 
> On Thu, 2019-01-03 at 20:19 +0100, lauren wrote:
> > Package: src:linux
> > Version: 4.19.12-1
> > Severity: normal
> > 
> > Dear Maintainer,
> > 
> > *** Reporter, please consider answering these questions, where
> > appropriate ***
> > 
> >* What led up to the situation?
> > upgraded to kernel 4.19 as part of regular debian apt update
> > 
> >* What exactly did you do (or not do) that was effective (or
> >  ineffective)?
> > i added "blacklist hid_multitouch" to
> > /etc/modprobe.d/blacklist.conf
> > 
> >* What was the outcome of this action?
> > no effect - the touchscreen is still active
> > 
> >* What outcome did you expect instead?
> > that the touchscreen was not active
> [...]
> 
> The kernel doesn't load modules itself; that's controlled by systemd,
> initramfs-tools, etc.
> 
> If you only recently updated the modprobe configuration, try running
> "update-initramfs -u" and then rebooting.  Does that fix the problem?
> 
> Ben.
> 

Processed: reassign 918191 to src:linux

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> reassign 918191 src:linux 4.18.16-1
Bug #918191 [linux-image-4.18.16] linux-image-4.18.16: Fail to shutdown or 
reboot
Warning: Unknown package 'linux-image-4.18.16'
Bug reassigned from package 'linux-image-4.18.16' to 'src:linux'.
No longer marked as found in versions 4.18.16-1.
Ignoring request to alter fixed versions of bug #918191 to the same values 
previously set
Bug #918191 [src:linux] linux-image-4.18.16: Fail to shutdown or reboot
The source 'linux' and version '4.18.16-1' do not appear to match any binary 
packages
Marked as found in versions linux/4.18.16-1.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
918191: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918191
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: tagging 918188

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 918188 + ftbfs
Bug #918188 [src:linux] linux: FTBFS on arm64
Added tag(s) ftbfs.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
918188: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918188
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems