Processed: tagging 865303

2017-10-05 Thread Debian Bug Tracking System 
Processing commands for cont...@bugs.debian.org:

> tags 865303 - moreinfo
Bug #865303 [src:linux] libreoffice: Libreoffice Java features crash with Linux 
3.16.43-2+deb8u1
Bug #865866 [src:linux] libreoffice-writer crash on startup Debian 9 i386 arch
Bug #869161 [src:linux] libreoffice-base crashes with code 139 when creating a 
new base or opening an existing one
Bug #869613 [src:linux] libreoffice write crashes (Debian 9)
Bug #869649 [src:linux] Debian 9 i386 - Libreoffice write crash
Bug #870070 [src:linux] Debian 9.1 stretch: LibreOffice Writer crashes at 
startup
Bug #875269 [src:linux] libreoffice-base: LibreOffice-Base crashes when trying 
to open Tables view in Debian 9 Stretch.
Bug #876021 [src:linux] libreoffice-writer: launching writer makes libreoffice 
crash
Bug #876458 [src:linux] LibreOffice Writer does not launch
Bug #877339 [src:linux] libreoffice-core: libreoffice SEGV in _expand_stack_to 
on most documents
Bug #877809 [src:linux] libreoffice writer java kernel crash
Removed tag(s) moreinfo.
Removed tag(s) moreinfo.
Removed tag(s) moreinfo.
Removed tag(s) moreinfo.
Removed tag(s) moreinfo.
Removed tag(s) moreinfo.
Removed tag(s) moreinfo.
Removed tag(s) moreinfo.
Removed tag(s) moreinfo.
Removed tag(s) moreinfo.
Removed tag(s) moreinfo.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
865303: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=865303
865866: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=865866
869161: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=869161
869613: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=869613
869649: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=869649
870070: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=870070
875269: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875269
876021: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=876021
876458: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=876458
877339: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=877339
877809: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=877809
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: unmerging 820081, reassign 820081 to libreoffice-writer, found 820081 in 1:5.1.2~rc1-1 ...

2017-10-05 Thread Debian Bug Tracking System 
Processing commands for cont...@bugs.debian.org:

> unmerge 820081
Bug #820081 [src:linux] libreoffice-writer: can't open LibreOffice Writer
Bug #865303 [src:linux] libreoffice: Libreoffice Java features crash with Linux 
3.16.43-2+deb8u1
Bug #865866 [src:linux] libreoffice-writer crash on startup Debian 9 i386 arch
Bug #869161 [src:linux] libreoffice-base crashes with code 139 when creating a 
new base or opening an existing one
Bug #869613 [src:linux] libreoffice write crashes (Debian 9)
Bug #869649 [src:linux] Debian 9 i386 - Libreoffice write crash
Bug #870070 [src:linux] Debian 9.1 stretch: LibreOffice Writer crashes at 
startup
Bug #875269 [src:linux] libreoffice-base: LibreOffice-Base crashes when trying 
to open Tables view in Debian 9 Stretch.
Bug #876021 [src:linux] libreoffice-writer: launching writer makes libreoffice 
crash
Bug #876458 [src:linux] LibreOffice Writer does not launch
Bug #877339 [src:linux] libreoffice-core: libreoffice SEGV in _expand_stack_to 
on most documents
Bug #877809 [src:linux] libreoffice writer java kernel crash
Disconnected #820081 from all other report(s).
> reassign 820081 libreoffice-writer
Bug #820081 [src:linux] libreoffice-writer: can't open LibreOffice Writer
Bug reassigned from package 'src:linux' to 'libreoffice-writer'.
No longer marked as found in versions linux/3.2.89-1, linux/4.9.30-2+deb9u1, 
linux/4.11.6-1, linux/3.16.43-2+deb8u1, and linux/4.9.30-2+deb9u2.
Ignoring request to alter fixed versions of bug #820081 to the same values 
previously set
> found 820081 1:5.1.2~rc1-1
Bug #820081 [libreoffice-writer] libreoffice-writer: can't open LibreOffice 
Writer
Marked as found in versions libreoffice/1:5.1.2~rc1-1.
> found 820081 1:5.2.7-1
Bug #820081 [libreoffice-writer] libreoffice-writer: can't open LibreOffice 
Writer
Marked as found in versions libreoffice/1:5.2.7-1.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
820081: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=820081
865303: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=865303
865866: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=865866
869161: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=869161
869613: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=869613
869649: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=869649
870070: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=870070
875269: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875269
876021: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=876021
876458: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=876458
877339: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=877339
877809: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=877809
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: reassign 820081 to src:linux, severity of 820081 is grave, forcibly merging 865303 820081

2017-10-05 Thread Debian Bug Tracking System 
Processing commands for cont...@bugs.debian.org:

> reassign 820081 src:linux
Bug #820081 [libreoffice-writer] libreoffice-writer: can't open LibreOffice 
Writer
Bug reassigned from package 'libreoffice-writer' to 'src:linux'.
No longer marked as found in versions libreoffice/1:5.2.7-1 and 
libreoffice/1:5.1.2~rc1-1.
Ignoring request to alter fixed versions of bug #820081 to the same values 
previously set
> severity 820081 grave
Bug #820081 [src:linux] libreoffice-writer: can't open LibreOffice Writer
Severity set to 'grave' from 'important'
> forcemerge 865303 820081
Bug #865303 [src:linux] libreoffice: Libreoffice Java features crash with Linux 
3.16.43-2+deb8u1
Bug #865866 [src:linux] libreoffice-writer crash on startup Debian 9 i386 arch
Bug #869161 [src:linux] libreoffice-base crashes with code 139 when creating a 
new base or opening an existing one
Bug #869613 [src:linux] libreoffice write crashes (Debian 9)
Bug #869649 [src:linux] Debian 9 i386 - Libreoffice write crash
Bug #870070 [src:linux] Debian 9.1 stretch: LibreOffice Writer crashes at 
startup
Bug #875269 [src:linux] libreoffice-base: LibreOffice-Base crashes when trying 
to open Tables view in Debian 9 Stretch.
Bug #876021 [src:linux] libreoffice-writer: launching writer makes libreoffice 
crash
Bug #876458 [src:linux] LibreOffice Writer does not launch
Bug #877339 [src:linux] libreoffice-core: libreoffice SEGV in _expand_stack_to 
on most documents
Bug #877809 [src:linux] libreoffice writer java kernel crash
Bug #820081 [src:linux] libreoffice-writer: can't open LibreOffice Writer
Added indication that 820081 affects 
libreoffice-base,libreoffice,openjdk-9-jre,jsvc,openjdk-7-jre,rustc,openjdk-8-jre,live-build,libreoffice-writer,security.debian.org
The source linux and version 3.2.89-1 do not appear to match any binary packages
Marked as found in versions linux/4.9.30-2+deb9u1, linux/3.16.43-2+deb8u1, 
linux/4.11.6-1, linux/3.2.89-1, and linux/4.9.30-2+deb9u2.
Added tag(s) confirmed and upstream.
Bug #865866 [src:linux] libreoffice-writer crash on startup Debian 9 i386 arch
Bug #869161 [src:linux] libreoffice-base crashes with code 139 when creating a 
new base or opening an existing one
Bug #869613 [src:linux] libreoffice write crashes (Debian 9)
Bug #869649 [src:linux] Debian 9 i386 - Libreoffice write crash
Bug #870070 [src:linux] Debian 9.1 stretch: LibreOffice Writer crashes at 
startup
Bug #875269 [src:linux] libreoffice-base: LibreOffice-Base crashes when trying 
to open Tables view in Debian 9 Stretch.
Bug #876021 [src:linux] libreoffice-writer: launching writer makes libreoffice 
crash
Bug #876458 [src:linux] LibreOffice Writer does not launch
Bug #877339 [src:linux] libreoffice-core: libreoffice SEGV in _expand_stack_to 
on most documents
Bug #877809 [src:linux] libreoffice writer java kernel crash
Merged 820081 865303 865866 869161 869613 869649 870070 875269 876021 876458 
877339 877809
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
820081: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=820081
865303: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=865303
865866: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=865866
869161: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=869161
869613: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=869613
869649: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=869649
870070: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=870070
875269: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875269
876021: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=876021
876458: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=876458
877339: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=877339
877809: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=877809
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#877809: libreoffice writer java kernel crash

2017-10-05 Thread Rene Engelhard 
reassign 877809 src:linux
forcemerge 865303 877809
thanks

On Thu, Oct 05, 2017 at 10:19:18PM +0100, Andrew Rule wrote:
> I recently upgraded to libreoffice 5.4.1-1 i386, and experienced the following
> problem:
> 
> While using
> openjdk-8-jre version 8u144-b01-1 i386
> kernel 4.9.21 i686 built from source

Yes, that kernel didn't have the bug. It doesn't have the Stack Clash
security fix either I think?

> then there is no problem at all, but,
> 
> with either
> kernel 4.9.51 i686 built from source, or
> kernel 4.12.0-2-686-pae Debian 4.12.13-1 i686

Those have.

> then using openjdk-8-jre in LibreOffice Calc works fine, Impress works fine,
> but Writer crashes on load, with exit +139, both on an Intel i3 and an AMD A4.
> If you turn off Java, or use the Free Software Foundation (gcj) it works and
> does not crash.

And you didn't even dare to check the libreoffice-writer bug list?

Outstanding bugs -- Grave functionality bugs; More information needed (1 bug)

#865303 [G|Mu|=☣] [src:linux] libreoffice: Libreoffice Java features crash with 
Linux 3.16.43-2+deb8u1
Outstanding bugs -- Important bugs; Patch Available (2 bugs)

#876051 [i|+|☣] [openjdk-8-jre-headless] i386 applications using JNI may crash 
due to Hotspot workaround for Exec Shield
#876069 [i|+|☣] [openjdk-9-jre-headless] i386 applications using JNI may crash 
due to Hotspot workaround for Exec Shield

directly on the top

You yourself say "libreoffice writer java kernel crash".

The first bug says:

Found in versions linux/4.9.30-2+deb9u1, linux/4.11.6-1, linux/3.2.89-1, 
linux/4.9.30-2+deb9u2, linux/3.16.43-2+deb8u1

and has many "friends" merged with it.

> I have also amd64 architecture on the AMD A4, and have not experienced the
> problem with that architecture.

Yes, that is i386 only.

See also

https://lwn.net/Articles/727206/
https://lwn.net/Articles/727703/

Yes, this is still unfixed, but a kernel/OpenJDK bug. LO just calls
JNI_StartJVM or how it's called. _OpenJDK_ crashes then.

> ii  libreoffice-wiki-publisher  1.2.0+LibO5.4.1-1

You can try removing this, this is just recommended to have a "full"
LO install if one did apt-get install libreoffice. That one's Java
and seems to be initialized on (most) "normal" writer startups, too
-> the Java crash.

Or use a architecture which wasn't already obsolete last decade. As you
say yourself: amd64 works.

Regards,

Rene

Processed: Re: Bug#877809: libreoffice writer java kernel crash

2017-10-05 Thread Debian Bug Tracking System 
Processing commands for cont...@bugs.debian.org:

> reassign 877809 src:linux
Bug #877809 [libreoffice] libreoffice writer java kernel crash
Bug reassigned from package 'libreoffice' to 'src:linux'.
No longer marked as found in versions libreoffice/1:5.4.1-1.
Ignoring request to alter fixed versions of bug #877809 to the same values 
previously set
> forcemerge 865303 877809
Bug #865303 [src:linux] libreoffice: Libreoffice Java features crash with Linux 
3.16.43-2+deb8u1
Bug #865866 [src:linux] libreoffice-writer crash on startup Debian 9 i386 arch
Bug #869161 [src:linux] libreoffice-base crashes with code 139 when creating a 
new base or opening an existing one
Bug #869613 [src:linux] libreoffice write crashes (Debian 9)
Bug #869649 [src:linux] Debian 9 i386 - Libreoffice write crash
Bug #870070 [src:linux] Debian 9.1 stretch: LibreOffice Writer crashes at 
startup
Bug #875269 [src:linux] libreoffice-base: LibreOffice-Base crashes when trying 
to open Tables view in Debian 9 Stretch.
Bug #876021 [src:linux] libreoffice-writer: launching writer makes libreoffice 
crash
Bug #876458 [src:linux] LibreOffice Writer does not launch
Bug #877339 [src:linux] libreoffice-core: libreoffice SEGV in _expand_stack_to 
on most documents
Bug #877809 [src:linux] libreoffice writer java kernel crash
Severity set to 'grave' from 'important'
Added indication that 877809 affects 
libreoffice-base,libreoffice,openjdk-9-jre,jsvc,openjdk-7-jre,rustc,openjdk-8-jre,live-build,libreoffice-writer,security.debian.org
The source linux and version 3.2.89-1 do not appear to match any binary packages
Marked as found in versions linux/3.16.43-2+deb8u1, linux/4.9.30-2+deb9u1, 
linux/4.11.6-1, linux/4.9.30-2+deb9u2, and linux/3.2.89-1.
Added tag(s) confirmed and moreinfo.
Bug #865866 [src:linux] libreoffice-writer crash on startup Debian 9 i386 arch
Bug #869161 [src:linux] libreoffice-base crashes with code 139 when creating a 
new base or opening an existing one
Bug #869613 [src:linux] libreoffice write crashes (Debian 9)
Bug #869649 [src:linux] Debian 9 i386 - Libreoffice write crash
Bug #870070 [src:linux] Debian 9.1 stretch: LibreOffice Writer crashes at 
startup
Bug #875269 [src:linux] libreoffice-base: LibreOffice-Base crashes when trying 
to open Tables view in Debian 9 Stretch.
Bug #876021 [src:linux] libreoffice-writer: launching writer makes libreoffice 
crash
Bug #876458 [src:linux] LibreOffice Writer does not launch
Bug #877339 [src:linux] libreoffice-core: libreoffice SEGV in _expand_stack_to 
on most documents
Merged 865303 865866 869161 869613 869649 870070 875269 876021 876458 877339 
877809
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
865303: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=865303
865866: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=865866
869161: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=869161
869613: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=869613
869649: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=869649
870070: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=870070
875269: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875269
876021: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=876021
876458: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=876458
877339: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=877339
877809: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=877809
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: limit source to linux, tagging 877760

2017-10-05 Thread Debian Bug Tracking System 
Processing commands for cont...@bugs.debian.org:

> limit source linux
Limiting to bugs with field 'source' containing at least one of 'linux'
Limit currently set to 'source':'linux'

> tags 877760 + pending confirmed
Bug #877760 [src:linux] linux: KEYS: request_key() does not update/replace 
expired keys
Added tag(s) confirmed and pending.
> thanks
Stopping processing here.

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

Processed: tagging 877760

2017-10-05 Thread Debian Bug Tracking System 
Processing commands for cont...@bugs.debian.org:

> tags 877760 + upstream fixed-upstream
Bug #877760 [src:linux] linux: KEYS: request_key() does not update/replace 
expired keys
Added tag(s) fixed-upstream and upstream.
> thanks
Stopping processing here.

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

Bug#877760: linux: KEYS: request_key() does not update/replace expired keys

2017-10-05 Thread Salvatore Bonaccorso 
Control: tags -1 + patch

Hi

On Thu, Oct 05, 2017 at 09:06:33AM +0200, Salvatore Bonaccorso wrote:
> Source: linux
> Version: 3.16.7-ckt7-1
> Severity: normal
> 
> Hi 
> 
> In 3.16.7-ckt7-1 we applied a backport of "EYS: request_key() should
> reget expired keys rather than give EKEYEXPIRED", adressing #758870,
> 0b0a84154eff56913e91df29de5c3a03a0029e38.
[...]
> Are we potentially miss any relevant needed commits between v3.16..v3.18?
> (054f6180d8b5602b431b5924976c956e760488b1, "KEYS: Simplify
> KEYRING_SEARCH_{NO,DO}_STATE_CHECK flags"?).

I did some bisecting, and indeed it seems we were missing the second
change as mentioned as well in the merge:

https://git.kernel.org/linus/23c836ce5c1e1e0bb942f58a3cbc2f7fc05a08b5

> The second and third fix a bug in NFS idmapper handling whereby a key
> representing a mapping between an id and a name expires and causing
> EKEYEXPIRED to be seen internally in NFS (which prevents the mapping
> from happening) rather than re-looking up the mapping"

With attached patch on top of the (current) jessie branch in git, the
problem is solved.

Regards,
Salvatore
>From 83a57b39cea1cdd82e42483dc5a60f671c32252c Mon Sep 17 00:00:00 2001
From: Salvatore Bonaccorso 
Date: Thu, 5 Oct 2017 17:16:34 +0200
Subject: [PATCH] KEYS: Simplify KEYRING_SEARCH_{NO,DO}_STATE_CHECK flags

Closes: #877760
---
 debian/changelog   |  3 +
 ...fy-KEYRING_SEARCH_-NO-DO-_STATE_CHECK-fla.patch | 96 ++
 ...t_key-should-reget-expired-keys-rather-th.patch |  8 +-
 debian/patches/series  |  1 +
 4 files changed, 104 insertions(+), 4 deletions(-)
 create mode 100644 debian/patches/bugfix/all/KEYS-Simplify-KEYRING_SEARCH_-NO-DO-_STATE_CHECK-fla.patch

diff --git a/debian/changelog b/debian/changelog
index 55ac046e7..9bb4229ac 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -582,6 +582,9 @@ linux (3.16.48-1) UNRELEASED; urgency=medium
 - ext4: preserve i_mode if __ext4_set_acl() fails
 - ext4: Don't clear SGID when inheriting ACLs
 
+  [ Salvatore Bonaccorso ]
+  * KEYS: Simplify KEYRING_SEARCH_{NO,DO}_STATE_CHECK flags (Closes: #877760)
+
  -- Ben Hutchings   Sun, 06 Aug 2017 22:03:56 +0100
 
 linux (3.16.43-2+deb8u5) jessie-security; urgency=medium
diff --git a/debian/patches/bugfix/all/KEYS-Simplify-KEYRING_SEARCH_-NO-DO-_STATE_CHECK-fla.patch b/debian/patches/bugfix/all/KEYS-Simplify-KEYRING_SEARCH_-NO-DO-_STATE_CHECK-fla.patch
new file mode 100644
index 0..44f9caee4
--- /dev/null
+++ b/debian/patches/bugfix/all/KEYS-Simplify-KEYRING_SEARCH_-NO-DO-_STATE_CHECK-fla.patch
@@ -0,0 +1,96 @@
+From: David Howells 
+Date: Mon, 1 Dec 2014 22:52:50 +
+Subject: KEYS: Simplify KEYRING_SEARCH_{NO,DO}_STATE_CHECK flags
+Origin: https://git.kernel.org/linus/054f6180d8b5602b431b5924976c956e760488b1
+
+Simplify KEYRING_SEARCH_{NO,DO}_STATE_CHECK flags to be two variations of the
+same flag.  They are effectively mutually exclusive and one or the other
+should be provided, but not both.
+
+Keyring cycle detection and key possession determination are the only things
+that set NO_STATE_CHECK, except that neither flag really does anything there
+because neither purpose makes use of the keyring_search_iterator() function,
+but rather provides their own.
+
+For cycle detection we definitely want to check inside of expired keyrings,
+just so that we don't create a cycle we can't get rid of.  Revoked keyrings
+are cleared at revocation time and can't then be reused, so shouldn't be a
+problem either way.
+
+For possession determination, we *might* want to validate each keyring before
+searching it: do you possess a key that's hidden behind an expired or just
+plain inaccessible keyring?  Currently, the answer is yes.  Note that you
+cannot, however, possess a key behind a revoked keyring because they are
+cleared on revocation.
+
+keyring_search() sets DO_STATE_CHECK, which is correct.
+
+request_key_and_link() currently doesn't specify whether to check the key
+state or not - but it should set DO_STATE_CHECK.
+
+key_get_instantiation_authkey() also currently doesn't specify whether to
+check the key state or not - but it probably should also set DO_STATE_CHECK.
+
+Signed-off-by: David Howells 
+Tested-by: Chuck Lever 
+[carnil: Backported to 3.16: Adjust context]
+---
+ security/keys/keyring.c  | 7 ---
+ security/keys/request_key.c  | 1 +
+ security/keys/request_key_auth.c | 1 +
+ 3 files changed, 6 insertions(+), 3 deletions(-)
+
+--- a/security/keys/keyring.c
 b/security/keys/keyring.c
+@@ -609,6 +609,10 @@ static bool search_nested_keyrings(struc
+ 	   ctx->index_key.type->name,
+ 	   ctx->index_key.description);
+ 
++#define STATE_CHECKS (KEYRING_SEARCH_NO_STATE_CHECK | KEYRING_SEARCH_DO_STATE_CHECK)
++	BUG_ON((ctx->flags & STATE_CHECKS) == 0 ||
++	   (ctx->flags & STATE_CHECKS)

Processed: Re: Bug#877760: linux: KEYS: request_key() does not update/replace expired keys

2017-10-05 Thread Debian Bug Tracking System 
Processing control commands:

> tags -1 + patch
Bug #877760 [src:linux] linux: KEYS: request_key() does not update/replace 
expired keys
Added tag(s) patch.

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

Secure boot signing infrastructure - feedback request

2017-10-05 Thread Helen Koike 
Hello all,

As you probably already know, Debian doesn't support the Secure Boot
chain yet.
To support it we need to sign Grub and the Kernel with our key, so we
are discussing the best infrastructure for this workflow.

The first approach we had was to add a by-hand script in Dak as
described here
https://wiki.debian.org/SecureBoot#First_option:_by-hand_script_in_dak
But this option wasn't well received by the ftpteam

The second approach we have is to add some debhelper scripts (e.g
dh_sign...) that will access a signing service which will sign the
binaries with Debian's key.  We would use the dh_sign... helpers when
making an extra binary package. buildd would then publish the -signed
version of the package in the archives.
Please see a more detailed explanation here
https://wiki.debian.org/SecureBoot#Second_option:_use_buildd_.2B-_debhelper_instead_of_dak
A current known issue with this approach is the NEW queue: it requires
the maintainer to also upload binaries for an architecture on first
upload, and these binaries are not rebuilt by the buildd ( see
https://wiki.debian.org/SecureBoot#Issues ).

I would like to know everyone's opinions about these approaches, if you
agree to go forward with the second approach described above and how do
we solve the NEW queue policy issue.

Thanks
Helen Koike

Re: [PATCH v3] scripts/package/builddeb: split generating packaging and build

2017-10-05 Thread Ritesh Raj Sarraf 
On Wed, 2017-10-04 at 13:38 +0300, Riku Voipio wrote:
> > I see the same problem for bindeb-pkg as in v2.
> 
> The parallel build overload? I'm totally puzzled then. Debian is
> still
> stuck with make 4.1, so I guess there is a change in behaviour on
> later makes.
> 
> > "make deb-pkg" gave me tons of warnings, then finally fails to
> > build:

I have seen similar fork bombs when using kernel-package to build the
kernel. And no, I couldn't much debug back then.

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=807574

At that time, realizing that the upstream kernel has a bindeb-pkg
target, was a big relief.


-- 
Given the large number of mailing lists I follow, I request you to CC
me in replies for quicker response

Processed: [bts-link] source package linux

2017-10-05 Thread Debian Bug Tracking System 
Processing commands for cont...@bugs.debian.org:

> #
> # bts-link upstream status pull for source package linux
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> #
> user bts-link-upstr...@lists.alioth.debian.org
Setting user to bts-link-upstr...@lists.alioth.debian.org (was 
bts-link-de...@lists.alioth.debian.org).
> # remote status report for #863266 (http://bugs.debian.org/863266)
> # Bug title: libvirt-daemon: spice port conflict - multiple VMs want Port 5900
> #  * https://bugzilla.redhat.com/show_bug.cgi?id=1432684
> #  * remote status changed: ON-QA -> CLOSED
> #  * remote resolution changed: (?) -> ERRATA
> #  * closed upstream
> tags 863266 + fixed-upstream
Bug #863266 [linux] libvirt-daemon: spice port conflict - multiple VMs want 
Port 5900
Added tag(s) fixed-upstream.
> usertags 863266 - status-ON-QA
Usertags were: status-ON-QA.
Usertags are now: .
> usertags 863266 + status-CLOSED resolution-ERRATA
There were no usertags set.
Usertags are now: resolution-ERRATA status-CLOSED.
> thanks
Stopping processing here.

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

Bug#877764: linux-image-amd64: cifs mount gets automatically the file_mode=0755,dir_mode=0755 options

2017-10-05 Thread matecs 

hi,


when sid pulled the 4.13 kernel, i noticed that these mounts
automatically get the file_mode=0755 and dir_mode=0755 options.


It appears that this indicates the server does not support Unix
extensions.

What is the file server running?

it's the debian sid's samba daemon: Version 4.6.7-Debian


And the 'nounix' confirms that.

ohhh, i did not noticed this. anyway i've looked at smbd config
and i contains the line unix extensions = yes.



Are there any messages in the kernel log relating to cifs?

nothing interesting.
[   15.659306] FS-Cache: Netfs 'cifs' registered for caching
[   15.659358] Key type cifs.spnego registered
[   15.659362] Key type cifs.idmap registered

regards,
cs

Bug#877764: linux-image-amd64: cifs mount gets automatically the file_mode=0755,dir_mode=0755 options

2017-10-05 Thread Ben Hutchings 
Control: reassign -1 src:linux 4.13.4-1
Control: tag -1 moreinfo

On Thu, 2017-10-05 at 10:18 +0200, matecs wrote:
> Package: linux-image-amd64
> Version: 4.13+86
> Severity: normal
> 
> Dear Maintainer,
> 
> i'm mounting my shares through cifs for years.
> when sid pulled the 4.13 kernel, i noticed that these mounts
> automatically get the file_mode=0755 and dir_mode=0755 options.

It appears that this indicates the server does not support Unix
extensions.

What is the file server running?

> the fstab looks like this:
> //nas.mchome.nop.hu/mc36 /nfs   cifs 
> user=mc36,password=***,uid=mc36,gid=mc36   0   0
> 
> then the resulting mount looks like this:
> //nas.mchome.nop.hu/mc36 on /nfs type cifs 
> (rw,relatime,vers=3.0,cache=strict,username=mc36,domain=,uid=1000,for
> ceuid,gid=1000,forcegid,addr=2001:0db8:1001:0255:0200:4eff:fe36:4e35,
> file_mode=0755,dir_mode=0755,nounix,serverino,mapposix,rsize=1048576,
> wsize=1048576,echo_interval=60,actimeo=1,user=mc36)

And the 'nounix' confirms that.

Are there any messages in the kernel log relating to cifs?

> things look similarly if i add vers=2.0 to the fstab. only vers=1.0 
> solves the issue.
[...]

Version 1 should no longer be used as it has well-known and unfixable
security issues.  The default protocol version for the cifs filesystem
was changed to 3 in Linux 4.13:
https://git.kernel.org/linus/eef914a9eb5eb83e60eb498315a491cd1edc13a1

Ben.

-- 
Ben Hutchings
Make three consecutive correct guesses and you will be considered an
expert.


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

Processed: Re: Bug#877764: linux-image-amd64: cifs mount gets automatically the file_mode=0755,dir_mode=0755 options

2017-10-05 Thread Debian Bug Tracking System 
Processing control commands:

> reassign -1 src:linux 4.13.4-1
Bug #877764 [linux-image-amd64] linux-image-amd64: cifs mount gets 
automatically the file_mode=0755,dir_mode=0755 options
Bug reassigned from package 'linux-image-amd64' to 'src:linux'.
No longer marked as found in versions linux-latest/86.
Ignoring request to alter fixed versions of bug #877764 to the same values 
previously set
Bug #877764 [src:linux] linux-image-amd64: cifs mount gets automatically the 
file_mode=0755,dir_mode=0755 options
Marked as found in versions linux/4.13.4-1.
> tag -1 moreinfo
Bug #877764 [src:linux] linux-image-amd64: cifs mount gets automatically the 
file_mode=0755,dir_mode=0755 options
Added tag(s) moreinfo.

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

Bug#877779: linux: modpost uses wrong sizes for mips-octeon kernel

2017-10-05 Thread James Cowgill 
Source: linux
Version: 4.12.13-1
Severity: normal

Hi,

I recently attempted to install an out-of-tree module (an old version of
the octeon mmc driver) on an octeon machine running big endian 32-bit
mips. In this configuration, the kernel is 64-bit, but userspace is 32-bit.

The module build failed with this error:
> LD [M]  /var/lib/dkms/octeon-mmc/9/build/octeon-mmc.o
>   Building modules, stage 2.
>   MODPOST 1 modules
> FATAL: /var/lib/dkms/octeon-mmc/9/build/octeon-mmc: sizeof(struct 
> of_device_id)=196 is not a modulo of the size of section 
> __mod_of___device_table=600.
> Fix definition of struct of_device_id in mod_devicetable.h

of_device_id is defined like this in mod_devicetable.h:
> struct of_device_id {
>   charname[32];
>   chartype[32];
>   charcompatible[128];
>   const void *data;
> };

The size of this structure is 200 bytes and not 196 byte as modpost
claims because the kernel is compiled as 64-bit (so the pointer at the
end is 8 bytes instead of 4).

I think there is a bug in the way Debian compiles modpost, because using
upstream's modpost works correctly. I see that the
real-XXX/devicetable-offsets.s file gets compiled with the target
compiler, but not with the target flags so flags such as "-mabi=64
-mnoabicalls" which are used in 64-bit MIPS kernels are not used. This
will cause the compiler to default to the userspace ABI which is 32-bit
in this case.

I'm not sure what the correct solution is here. Using the target flags
directly might make modpost specific to a kernel flavour. Hacking in
some special flags for mips* doesn't sound great either.

I have not tested any other platforms, but I am guessing this issue will
affect other platforms when the size of pointers in userspace and the
kernel differ.

James




signature.asc
Description: OpenPGP digital signature

Processed: fixed 877760 in 3.18-1~exp1

2017-10-05 Thread Debian Bug Tracking System 
Processing commands for cont...@bugs.debian.org:

> fixed 877760 3.18-1~exp1
Bug #877760 [src:linux] linux: KEYS: request_key() does not update/replace 
expired keys
Marked as fixed in versions linux/3.18-1~exp1.
> thanks
Stopping processing here.

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

Re: reports bugs

2017-10-05 Thread Uwe Kleine-König 
On Mon, Oct 02, 2017 at 10:41:03PM +0200, Alain wrote:
> don't want to receive reports bugs . please take care  of !

You either subscribed to the debian-kernel mailing list or to the pts.

If the former please send a message to
debian-kernel-requ...@lists.debian.org with

Subject: unsubscribe

and then confirm the reply to unsubscribe from the list.

If the latter (I think) go to https://tracker.debian.org/pkg/linux,
login and then click unsubscribe.

Best regards
Uwe

-- 
Pengutronix e.K.   | Uwe Kleine-König|
Industrial Linux Solutions | http://www.pengutronix.de/  |

Bug#877764: linux-image-amd64: cifs mount gets automatically the file_mode=0755,dir_mode=0755 options

2017-10-05 Thread matecs 

Package: linux-image-amd64
Version: 4.13+86
Severity: normal

Dear Maintainer,

i'm mounting my shares through cifs for years.
when sid pulled the 4.13 kernel, i noticed that these mounts
automatically get the file_mode=0755 and dir_mode=0755 options.

the fstab looks like this:
//nas.mchome.nop.hu/mc36 /nfs   cifs 
user=mc36,password=***,uid=mc36,gid=mc36   0   0


then the resulting mount looks like this:
//nas.mchome.nop.hu/mc36 on /nfs type cifs 
(rw,relatime,vers=3.0,cache=strict,username=mc36,domain=,uid=1000,forceuid,gid=1000,forcegid,addr=2001:0db8:1001:0255:0200:4eff:fe36:4e35,file_mode=0755,dir_mode=0755,nounix,serverino,mapposix,rsize=1048576,wsize=1048576,echo_interval=60,actimeo=1,user=mc36)


things look similarly if i add vers=2.0 to the fstab. only vers=1.0 
solves the issue.



-- System Information:
Debian Release: buster/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.13.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US, LC_CTYPE=en_US (charmap=locale: Cannot set LC_CTYPE 
to default locale: No such file or directory

locale: Cannot set LC_MESSAGES to default locale: No such file or directory
locale: Cannot set LC_ALL to default locale: No such file or directory
ANSI_X3.4-1968), LANGUAGE=en_US (charmap=locale: Cannot set LC_CTYPE to 
default locale: No such file or directory

locale: Cannot set LC_MESSAGES to default locale: No such file or directory
locale: Cannot set LC_ALL to default locale: No such file or directory
ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages linux-image-amd64 depends on:
ii  linux-image-4.13.0-1-amd64  4.13.4-1

linux-image-amd64 recommends no packages.

linux-image-amd64 suggests no packages.

-- debconf information:
perl: warning: Setting locale failed.
perl: warning: Please check that your locale settings:
LANGUAGE = (unset),
LC_ALL = (unset),
LANG = "en_US"
are supported and installed on your system.
perl: warning: Falling back to the standard locale ("C").
locale: Cannot set LC_CTYPE to default locale: No such file or directory
locale: Cannot set LC_MESSAGES to default locale: No such file or directory
locale: Cannot set LC_ALL to default locale: No such file or directory

Re: [PATCH v3] scripts/package/builddeb: split generating packaging and build

2017-10-05 Thread Masahiro Yamada 
Hi Riku,


2017-10-04 19:38 GMT+09:00 Riku Voipio :
> On 4 October 2017 at 12:12, Masahiro Yamada
>  wrote:
>> Hi Riku,
>
>> 2017-10-02 19:43 GMT+09:00  :
>>> From: Riku Voipio 
>>>
>>> Move debian/ directory generation out of builddeb to a new script,
>>> mkdebian. The package build commands are kept in builddeb, which
>>> is now an internal command called from debian/rules.
>>>
>>> With these changes in place, we can now use dpkg-buildpackage from
>>> deb-pkg and bindeb-pkg removing need for handrolled source/changes
>>> generation.
>>>
>>> This patch is based on the criticism of the current state of builddeb
>>> discussed on:
>>>
>>> https://patchwork.kernel.org/patch/9656403/
>>>
>>> Signed-off-by: Riku Voipio 
>>> ---
>>> changes since v2:
>>> - revert back to intdeb-pkg target
>>> - fix parellel builds from deb-pkg targets
>
>> No.  Not fixed.
>
>> I see the same problem for bindeb-pkg as in v2.
>
> The parallel build overload?

Yes.

> I'm totally puzzled then. Debian is still
> stuck with make 4.1, so I guess there is a change in behaviour on
> later makes.


Can you test the patch with GNU Make 4.2 or newer?

You can download tarballs
https://ftp.gnu.org/gnu/make/

The build process is pretty easy,
./configure, make, make install,  as usual.





>> "make deb-pkg" gave me tons of warnings, then finally fails to build:
>
>> rm -rf debian/*tmp debian/files
>> mv debian/ debian.backup # debian/ might be cleaned away
>> make clean
>> mv debian.backup debian
>>  dpkg-source -i.git -b linux
>> dpkg-source: warning: no source format specified in
>> debian/source/format, see dpkg-source(1)
>> dpkg-source: info: using source format '1.0'
>> dpkg-source: warning: source directory 'linux' is not
>> - 'linux-4.13.0+-4.13.0+'
>> dpkg-source: warning: .orig directory name linux.orig is not
>> - (wanted linux-4.13.0+-4.13.0+.orig)
>> dpkg-source: info: building linux-4.13.0+ using existing
>> linux-4.13.0+_4.13.0+.orig.tar.gz
>> dpkg-source: info: building linux-4.13.0+ in linux-4.13.0+_4.13.0+-7.diff.gz
>> dpkg-source: warning: ignoring deletion of file .scmversion, use
>> --include-removal to override
>> dpkg-source: warning: ignoring deletion of directory drivers/lguest
>> dpkg-source: warning: ignoring deletion of file
>> drivers/video/console/fbcon_rotate.h, use --include-removal to
>> override
>> dpkg-source: warning: ignoring deletion of file
>> drivers/video/console/fbcon.h, use --include-removal to override
>> dpkg-source: warning: ignoring deletion of file
>> drivers/video/console/fbcon_cw.c, use --include-removal to override
>> dpkg-source: warning: ignoring deletion of file
>> drivers/video/console/fbcon_rotate.c, use --include-removal to
>> override
>> dpkg-source: warning: ignoring deletion of file
>> drivers/video/console/fbcon.c, use --include-removal to override
>>
>>
>>   ...
>>
>>
>> dpkg-source: info: use the '3.0 (quilt)' format to have separate and
>> documented changes to upstream files, see dpkg-source(1)
>> dpkg-source: error: unrepresentable changes to source
>>
>>
>> Do you have a clue?
>
> It looks like making the tarball (or renaming it) failed, and
> dpkg-source picked up and older orig.tar.gz with same name. I think a
> full log would be useful here, because there probably is bug here in
> my patch.

I saw this build failure some times,
but I cannot reproduce it today.

I have not tracked down the condition it happens under.

I will save the log if it happens next time.





>>> +cat < debian/rules
>>> +#!/usr/bin/make -f
>>> +
>>> +build:
>>> +   \$(MAKE) KERNELRELEASE=${version} ARCH=${ARCH} KBUILD_SRC=
>>> +
>>> +binary-arch:
>>> +   \$(MAKE) KERNELRELEASE=${version} ARCH=${ARCH} KBUILD_SRC= 
>>> intdeb-pkg
>>> +
>>> +clean:
>>> +   rm -rf debian/*tmp debian/files
>>> +   mv debian/ debian.backup # debian/ might be cleaned away
>>> +   \$(MAKE) clean
>>> +   mv debian.backup debian
>>
>>
>> "mv debian debian.backup" is unnecessary, I think.
>>
>>
>> I think you saw
>>
>> clean-dirs += $(objtree)/debian/
>>
>> in scripts/package/Makefile.
>
>> Please notice this is cleaned-up by "make mrproper"
>> because Kbuild does not descend under scripts/ for "make clean".
>
> That is how it was in the old version of builddeb as well. I'll submit
> another patch to remove the mv-in-clean hack.

Yes, please do so.


-- 
Best Regards
Masahiro Yamada

Bug#877763: WARNING: CPU: 1 PID: 431 at /build/linux-wJBo44/linux-4.13.4/fs/btrfs/ctree.h:1559 btrfs_update_device+0x1b2/0x1c0 [btrfs]

2017-10-05 Thread Roman Lebedev 
Package: src:linux
Version: 4.13.4-1
Severity: normal

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

After upgrading to 4.13.0-1-amd64, i'm seeing new traces in the dmesg.

- -- Package-specific info:
** Version:
Linux version 4.13.0-1-amd64 (debian-kernel@lists.debian.org) (gcc version 
6.4.0 20170920 (Debian 6.4.0-7)) #1 SMP Debian 4.13.4-1 (2017-10-01)

** Command line:
BOOT_IMAGE=/@/boot/vmlinuz-4.13.0-1-amd64 
root=UUID=ccd67dc6-6b12-47f6-bef7-a17c40b87332 ro rootflags=subvol=@ 
cryptdevice=UUID=7093dff9-dea8-49a2-bc83-653d5b677b9b:sdb3_luks,UUID=f533b8e8-b916-4b60-9cfc-10f4a56cc146:sdc3_luks,UUID=dcff9ee8-30d8-40e1-9b87-127c540d3d9d:sda3_luks

** Tainted: W (512)
 * Taint on warning.

** Kernel log:
[ 3502.772087] [ cut here ]
[ 3502.772124] WARNING: CPU: 7 PID: 18428 at 
/build/linux-wJBo44/linux-4.13.4/fs/btrfs/ctree.h:1559 
btrfs_update_device+0x1b2/0x1c0 [btrfs]
[ 3502.772126] Modules linked in: cpufreq_userspace cpufreq_powersave 
cpufreq_conservative snd_hda_codec_hdmi binfmt_misc nls_ascii nls_cp437 
snd_hda_codec_realtek vfat snd_hda_codec_generic snd_hda_intel fat 
snd_hda_codec snd_hda_core eeepc_wmi asus_wmi sparse_keymap rfkill video amdkfd 
wmi_bmof snd_hwdep snd_pcm mxm_wmi radeon efi_pstore snd_timer xhci_pci 
edac_mce_amd snd efivars ttm xhci_hcd e1000e kvm_amd kvm irqbypass 
crct10dif_pclmul ptp fam15h_power pcspkr drm_kms_helper pps_core drm 
i2c_algo_bit k10temp sg button tpm_infineon soundcore crc32_pclmul 
ghash_clmulni_intel sp5100_tco i2c_piix4 wmi shpchp acpi_cpufreq it87 hwmon_vid 
configfs loop parport_pc ppdev lp parport sunrpc efivarfs ip_tables x_tables 
autofs4 dm_crypt dm_mod raid10 raid456 libcrc32c async_raid6_recov async_memcpy 
async_pq
[ 3502.772159]  async_xor async_tx raid1 raid0 multipath linear btrfs 
crc32c_generic xor raid6_pq md_mod joydev hid_generic usbhid hid sd_mod 
ohci_pci crc32c_intel aesni_intel aes_x86_64 crypto_simd ehci_pci cryptd 
ohci_hcd glue_helper evdev ahci ehci_hcd libahci serio_raw libata usbcore 
usb_common scsi_mod
[ 3502.772178] CPU: 7 PID: 18428 Comm: ld Not tainted 4.13.0-1-amd64 #1 Debian 
4.13.4-1
[ 3502.772180] Hardware name: To be filled by O.E.M. To be filled by 
O.E.M./CROSSHAIR V FORMULA-Z, BIOS 2201 03/23/2015
[ 3502.772182] task: 93cfae69e0c0 task.stack: bcc308d1
[ 3502.772201] RIP: 0010:btrfs_update_device+0x1b2/0x1c0 [btrfs]
[ 3502.772202] RSP: 0018:bcc308d13af8 EFLAGS: 00010206
[ 3502.772204] RAX: 0fff RBX: 93d102d17310 RCX: 03a380fd1e00
[ 3502.772206] RDX: 0004 RSI: 3efa RDI: 93cfe462c7e8
[ 3502.772207] RBP: 93d1c6c80c00 R08: 3efe R09: bcc308d13ab0
[ 3502.772209] R10:  R11: 0003 R12: 
[ 3502.772210] R13: 3eda R14: 93cfe462c7e8 R15: fff4
[ 3502.772212] FS:  7fe1328e2400() GS:93d1eedc() 
knlGS:
[ 3502.772213] CS:  0010 DS:  ES:  CR0: 80050033
[ 3502.772214] CR2: 7f3970f4f000 CR3: 0005dd051000 CR4: 000406e0
[ 3502.772216] Call Trace:
[ 3502.772237]  ? btrfs_finish_chunk_alloc+0x131/0x4e0 [btrfs]
[ 3502.772252]  ? btrfs_insert_item+0x7e/0xf0 [btrfs]
[ 3502.772267]  ? btrfs_create_pending_block_groups+0x144/0x250 [btrfs]
[ 3502.772284]  ? __btrfs_end_transaction+0x8e/0x2e0 [btrfs]
[ 3502.772301]  ? __btrfs_prealloc_file_range+0x355/0x470 [btrfs]
[ 3502.772319]  ? btrfs_prealloc_file_range+0x10/0x20 [btrfs]
[ 3502.772336]  ? btrfs_fallocate+0x742/0x11f0 [btrfs]
[ 3502.772340]  ? vfs_fallocate+0x151/0x270
[ 3502.772342]  ? SyS_fallocate+0x43/0x80
[ 3502.772345]  ? system_call_fast_compare_end+0xc/0x97
[ 3502.772347] Code: 4c 89 f7 45 31 c0 ba 10 00 00 00 4c 89 ee e8 16 26 ff ff 
4c 89 f7 e8 be fd fc ff e9 de fe ff ff 41 bc f4 ff ff ff e9 db fe ff ff <0f> ff 
eb b7 e8 75 93 2a ec 0f 1f 44 00 00 0f 1f 44 00 00 41 55
[ 3502.772370] ---[ end trace 258650fddcd0b268 ]---
[ 3502.772522] [ cut here ]
[ 3502.772571] WARNING: CPU: 3 PID: 18436 at 
/build/linux-wJBo44/linux-4.13.4/fs/btrfs/ctree.h:1559 
btrfs_update_device+0x1b2/0x1c0 [btrfs]
[ 3502.772573] Modules linked in: cpufreq_userspace cpufreq_powersave 
cpufreq_conservative snd_hda_codec_hdmi binfmt_misc nls_ascii nls_cp437 
snd_hda_codec_realtek vfat snd_hda_codec_generic snd_hda_intel fat 
snd_hda_codec snd_hda_core eeepc_wmi asus_wmi sparse_keymap rfkill video amdkfd 
wmi_bmof snd_hwdep snd_pcm mxm_wmi radeon efi_pstore snd_timer xhci_pci 
edac_mce_amd snd efivars ttm xhci_hcd e1000e kvm_amd kvm irqbypass 
crct10dif_pclmul ptp fam15h_power pcspkr drm_kms_helper pps_core drm 
i2c_algo_bit k10temp sg button tpm_infineon soundcore crc32_pclmul 
ghash_clmulni_intel sp5100_tco i2c_piix4 wmi shpchp acpi_cpufreq it87 hwmon_vid 
configfs loop parport_pc ppdev lp parport sunrpc efivarfs ip_tables x_tables 
autofs4 dm_crypt dm_mod raid10 raid456 libcrc32c async_raid6_recov async_memcpy 
async_pq
[ 3502.772610]

Bug#877760: linux: KEYS: request_key() does not update/replace expired keys

2017-10-05 Thread Salvatore Bonaccorso 
Source: linux
Version: 3.16.7-ckt7-1
Severity: normal

Hi 

In 3.16.7-ckt7-1 we applied a backport of "EYS: request_key() should
reget expired keys rather than give EKEYEXPIRED", adressing #758870,
0b0a84154eff56913e91df29de5c3a03a0029e38.

I noticed that in jessie, with still up to 3.16.43-2+deb8u5 the
following test-rocedure 

, [ keytest.sh ]
| #!/bin/sh
| keyctl request2 user debug:dummy a @s
| keyctl timeout %user:debug:dummy 3
| keyctl show  %user:debug:dummy
| sleep 4
| keyctl request2 user debug:dummy a @s
`

still leads to:

root@jessie-amd64:~# ./keytest 
542551421
Keyring
 542551421 --alswrv  0 0  user: debug:dummy
request_key: Key has expired
root@jessie-amd64:~# ./keytest 
request_key: Key has expired
Can't find 'user:debug:dummy'
Can't find 'user:debug:dummy'
request_key: Key has expired
root@jessie-amd64:~#

In stretch, this does not happen (with 4.9.30-2+deb9u5)

root@stretch-amd64:~# ./keytest 
89439986
Keyring
  89439986 --alswrv  0 0  user: debug:dummy
25490408
root@stretch-amd64:~# ./keytest 
25490408
Keyring
  25490408 --alswrv  0 0  user: debug:dummy
546453714
root@stretch-amd64:~#

or with 4.9.30-2+deb9u5~bpo8+1 from backports:

root@jessie-amd64:~# ./keytest 
142545203
Keyring
 142545203 --alswrv  0 0  user: debug:dummy
86582269
root@jessie-amd64:~# ./keytest 
86582269
Keyring
  86582269 --alswrv  0 0  user: debug:dummy
358240859
root@jessie-amd64:~#

Are we potentially miss any relevant needed commits between v3.16..v3.18?
(054f6180d8b5602b431b5924976c956e760488b1, "KEYS: Simplify
KEYRING_SEARCH_{NO,DO}_STATE_CHECK flags"?).

Regards,
Salvatore

Processed: retitle 876762 to linux-image-3.16.0-4-amd64: tmpfs file system sometimes has undeletable directories/files

2017-10-05 Thread Debian Bug Tracking System 
Processing commands for cont...@bugs.debian.org:

> retitle 876762 linux-image-3.16.0-4-amd64: tmpfs file system sometimes has 
> undeletable directories/files
Bug #876762 [src:linux] linux-image-3.16.0-4-amd64: tmpf file system sometimes 
has undeletable directories/files
Changed Bug title to 'linux-image-3.16.0-4-amd64: tmpfs file system sometimes 
has undeletable directories/files' from 'linux-image-3.16.0-4-amd64: tmpf file 
system sometimes has undeletable directories/files'.
> thanks
Stopping processing here.

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