Re: Reiser4 for Linux-4.14, Reiser4progs-1.2.0, Libaal-1.0.7, Format 4.0.2

2017-11-28 Thread Metztli Information Technology 

On Tue, Nov 28, 2017 at 9:08 AM, Edward Shishkin  
wrote:
> On 11/28/2017 04:21 PM, Metztli Information Technology wrote:
>>
>> Appreciated Ed.
>>
>>> Hello,
>>>
>>> Please, download reiser4-for-4.14.1.patch which contains the fixup.
>>>
>> Updated patch works but had a rough time during the build procedure
>> because zstd is used by btrfs as well:
>
>
> This is something curious. Squashfs also uses zstd, as far as I know..

Well, ignore-dups was 'quick hack' -- and it took me several build attempts to 
figure out
at *which* package directory root it had to be touch'ed -- until I forced
/usr/share/kernel-wedge/commands/find-dups
to spit it out in the build log via its $configdir variable.

Notwithstanding, except for Ben, we don't get much constructive feedback from 
Debian but I assume
 Squashfs and btrfs 'harmonious' zstd coexistence has to do with:
"When you have duplicates, you need to find (or make) a package that both 
packages depend on, and move
the duplicate modules to it."
< https://github.com/pexip/os-kernel-wedge >

As I have time, I will attempt to figure out which package Squashfs and btrfs 
depend on so as to
potentianlly implement a patch to include reiser4 (SFRN) 4.0.2.

>
>
>> ...
>> some modules are in more than one package
>> debian/reiser4-modules-4.14.0-1+reiser4.0.2-amd64-di
>> lib/modules/4.14.0-1+reiser4.0.2-amd64/kernel/lib/xxhash.ko
>> debian/btrfs-modules-4.14.0-1+reiser4.0.2-amd64-di
>> lib/modules/4.14.0-1+reiser4.0.2-amd64/kernel/lib/xxhash.ko
>> debian/reiser4-modules-4.14.0-1+reiser4.0.2-amd64-di
>> lib/modules/4.14.0-1+reiser4.0.2-amd64/kernel/lib/zstd/zstd_compress.ko
>> debian/btrfs-modules-4.14.0-1+reiser4.0.2-amd64-di
>> lib/modules/4.14.0-1+reiser4.0.2-amd64/kernel/lib/zstd/zstd_compress.ko
>> debian/reiser4-modules-4.14.0-1+reiser4.0.2-amd64-di
>> lib/modules/4.14.0-1+reiser4.0.2-amd64/kernel/lib/zstd/zstd_decompress.ko
>> debian/btrfs-modules-4.14.0-1+reiser4.0.2-amd64-di
>> lib/modules/4.14.0-1+reiser4.0.2-amd64/kernel/lib/zstd/zstd_decompress.ko
>> command exited with status 1
>> make[2]: *** [install-udeb_amd64] Error 2
>> debian/rules.real:498: recipe for target 'install-udeb_amd64' failed
>> make[2]: Leaving directory '/usr/tzinti/build/kernel/tekitl-4.14.2/linux'
>> make[1]: *** [binary-arch_amd64] Error 2
>> debian/rules.gen:18: recipe for target 'binary-arch_amd64' failed
>> make[1]: Leaving directory '/usr/tzinti/build/kernel/tekitl-4.14.2/linux'
>> make: *** [binary-arch] Error 2
>> debian/rules:50: recipe for target 'binary-arch' failed
>> dpkg-buildpackage: error: fakeroot debian/rules binary-arch gave error
>> exit status 2
>>
>> < https://pbs.twimg.com/media/DPuO9nKU8AEMTgx.jpg:large >
>>
>> Accordingly, in order for the build to proceed past the kernel-wedge show
>> stopper, I had to
>>
>> touch debian/installer/amd64/ignore-dups
>> < https://github.com/pexip/os-kernel-wedge >
>> i.e.,
>> 
>> % kernel-wedge help find-dups
>> find-dups kernel-name
>>
>> Find duplicate modules. Pass the kernel name.
>>
>> Return 1 if any duplicates are found, unless $KW_CHECK_NONFATAL is
>> non-empty or the configuration file 'ignore-dups' exists.
>> --
>>
>> And the build procedure completed successfully at long last.
>>
>>> On 11/27/2017 03:37 PM, Metztli Information Technology wrote:

 Niltze, Ed-


 I've built libaal-1.0.7 and Reiser4progs-1.2.0 Debian packages for AMD64
 successfully and currently testing in a virtual machine.

 I've applied reiser4-for-4.14.0 patch to upstream kernel 4.14.2; Debian
 packaging for 4.14.2-xyz required GCC-7 for kernel build

-- which I installed including relevant dependencies. Yet I have
 experienced (twice) the appended tail show stopper error:
 ...

 CC  arch/x86/boot/compressed/pagetable.o
 CC  arch/x86/boot/compressed/eboot.o
 AS  arch/x86/boot/compressed/efi_stub_64.o
 AS  arch/x86/boot/compressed/efi_thunk_64.o
 CC  arch/x86/boot/compressed/misc.o
 XZKERN  arch/x86/boot/compressed/vmlinux.bin.xz
 ERROR: "find_get_pages_range" [fs/reiser4/reiser4.ko] undefined!
 make[6]: *** [__modpost] Error 1

 /usr/tzinti/build/kernel/tekitl-4.14.2/linux/scripts/Makefile.modpost:92:
 recipe for target '__modpost' failed
 make[5]: *** [modules] Error 2
 /usr/tzinti/build/kernel/tekitl-4.14.2/linux/Makefile:1228: recipe for
 target 'modules' failed
 make[5]: *** Waiting for unfinished jobs
 MKPIGGY arch/x86/boot/compressed/piggy.S
 AS  arch/x86/boot/compressed/piggy.o
 DATAREL arch/x86/boot/compressed/vmlinux
 LD  arch/x86/boot/compressed/vmlinux
 ZOFFSET arch/x86/boot/zoffset.h
 OBJCOPY arch/x86/boot/vmlinux.bin
 AS  arch/x86/boot/header.o
 LD  arch/x86/boot/setup.elf
 OBJCOPY

Re: recommends for apparmor in newest linux-image-4.13

2017-11-28 Thread Michael Stone 

On Wed, Nov 29, 2017 at 12:03:08AM +0100, Marco d'Itri wrote:

On Nov 28, Christoph Hellwig  wrote:

It's just a bad idea of a security model that implements ad-hoc
and mostly path based restrictions instead of an actually verified
security model.  Using that by default makes it much harder to actually
use a real MAC based security model, which not only is required for
various security sensitive deployments but also a good idea in general.

This may be true, but OTOH nobody cared enough about SELinux to actually
make it work out of the box in Debian.


By that criteria, it doesn't seem like anyone cares about apparmor 
either... 


FWIW, I also think apparmor a bad idea, but it's somehow morphed
from "can we make it possible to turn apparmor on" to "let's make RC 
bugs for stuff that doesn't work with apparmor" without much real buy-in 
AFAICT.


Mike Stone

Re: recommends for apparmor in newest linux-image-4.13

2017-11-28 Thread Marco d'Itri 
On Nov 28, Christoph Hellwig  wrote:

> It's just a bad idea of a security model that implements ad-hoc
> and mostly path based restrictions instead of an actually verified
> security model.  Using that by default makes it much harder to actually
> use a real MAC based security model, which not only is required for
> various security sensitive deployments but also a good idea in general.
This may be true, but OTOH nobody cared enough about SELinux to actually 
make it work out of the box in Debian.
So, for the time being I would gladly accept an inferior solution.

-- 
ciao,
Marco


signature.asc
Description: PGP signature

Bug#883023: linux-image-armmp: enable CONFIG_IMX_THERMAL=m

2017-11-28 Thread Heinrich Schuchardt 
Package: linux-image-4.13.0-1-armmp
Version: 4.13.13-1
Severity: wishlist

Dear Maintainer,

the i.MX6 CPU has a thermal sensor. To use it the appropriate
kernel module has to be built.

Please, enable
CONFIG_IMX_THERMAL=m

Best regards

Heinrich Schuchardt

-- System Information:
Debian Release: 9.2
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: armhf (armv7l)

Kernel: Linux 4.9.0-4-armmp (SMP w/4 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), 
LANGUAGE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Re: recommends for apparmor in newest linux-image-4.13

2017-11-28 Thread Christoph Hellwig 
On Thu, Nov 23, 2017 at 03:43:10PM +0100, Lars Wirzenius wrote:
> 
> do you think you could manage to either point the general -devel
> reading population to a discussion of why using AppArmor by default is
> horrible news, or write that yourself? That would seem to be more
> constructive than you just showing up after months of discussion
> saying it's horrible news.

It's just a bad idea of a security model that implements ad-hoc
and mostly path based restrictions instead of an actually verified
security model.  Using that by default makes it much harder to actually
use a real MAC based security model, which not only is required for
various security sensitive deployments but also a good idea in general.

Last but not least apparmor had various issues where certain distros
shipped non-upstream features that later turned out to be incompatible
with what went upstream.

Re: Reiser4 for Linux-4.14, Reiser4progs-1.2.0, Libaal-1.0.7, Format 4.0.2

2017-11-28 Thread Edward Shishkin 

On 11/28/2017 04:21 PM, Metztli Information Technology wrote:

Appreciated Ed.


Hello,

Please, download reiser4-for-4.14.1.patch which contains the fixup.


Updated patch works but had a rough time during the build procedure because 
zstd is used by btrfs as well:


This is something curious. Squashfs also uses zstd, as far as I know..


...
some modules are in more than one package
debian/reiser4-modules-4.14.0-1+reiser4.0.2-amd64-di 
lib/modules/4.14.0-1+reiser4.0.2-amd64/kernel/lib/xxhash.ko
debian/btrfs-modules-4.14.0-1+reiser4.0.2-amd64-di 
lib/modules/4.14.0-1+reiser4.0.2-amd64/kernel/lib/xxhash.ko
debian/reiser4-modules-4.14.0-1+reiser4.0.2-amd64-di 
lib/modules/4.14.0-1+reiser4.0.2-amd64/kernel/lib/zstd/zstd_compress.ko
debian/btrfs-modules-4.14.0-1+reiser4.0.2-amd64-di 
lib/modules/4.14.0-1+reiser4.0.2-amd64/kernel/lib/zstd/zstd_compress.ko
debian/reiser4-modules-4.14.0-1+reiser4.0.2-amd64-di 
lib/modules/4.14.0-1+reiser4.0.2-amd64/kernel/lib/zstd/zstd_decompress.ko
debian/btrfs-modules-4.14.0-1+reiser4.0.2-amd64-di 
lib/modules/4.14.0-1+reiser4.0.2-amd64/kernel/lib/zstd/zstd_decompress.ko
command exited with status 1
make[2]: *** [install-udeb_amd64] Error 2
debian/rules.real:498: recipe for target 'install-udeb_amd64' failed
make[2]: Leaving directory '/usr/tzinti/build/kernel/tekitl-4.14.2/linux'
make[1]: *** [binary-arch_amd64] Error 2
debian/rules.gen:18: recipe for target 'binary-arch_amd64' failed
make[1]: Leaving directory '/usr/tzinti/build/kernel/tekitl-4.14.2/linux'
make: *** [binary-arch] Error 2
debian/rules:50: recipe for target 'binary-arch' failed
dpkg-buildpackage: error: fakeroot debian/rules binary-arch gave error exit 
status 2

< https://pbs.twimg.com/media/DPuO9nKU8AEMTgx.jpg:large >

Accordingly, in order for the build to proceed past the kernel-wedge show 
stopper, I had to

touch debian/installer/amd64/ignore-dups
< https://github.com/pexip/os-kernel-wedge >
i.e.,

% kernel-wedge help find-dups
find-dups kernel-name

Find duplicate modules. Pass the kernel name.

Return 1 if any duplicates are found, unless $KW_CHECK_NONFATAL is
non-empty or the configuration file 'ignore-dups' exists.
--

And the build procedure completed successfully at long last.


On 11/27/2017 03:37 PM, Metztli Information Technology wrote:

Niltze, Ed-


I've built libaal-1.0.7 and Reiser4progs-1.2.0 Debian packages for AMD64 
successfully and currently testing in a virtual machine.

I've applied reiser4-for-4.14.0 patch to upstream kernel 4.14.2; Debian 
packaging for 4.14.2-xyz required GCC-7 for kernel build

   -- which I installed including relevant dependencies. Yet I have experienced 
(twice) the appended tail show stopper error:
...

CC  arch/x86/boot/compressed/pagetable.o
CC  arch/x86/boot/compressed/eboot.o
AS  arch/x86/boot/compressed/efi_stub_64.o
AS  arch/x86/boot/compressed/efi_thunk_64.o
CC  arch/x86/boot/compressed/misc.o
XZKERN  arch/x86/boot/compressed/vmlinux.bin.xz
ERROR: "find_get_pages_range" [fs/reiser4/reiser4.ko] undefined!
make[6]: *** [__modpost] Error 1
/usr/tzinti/build/kernel/tekitl-4.14.2/linux/scripts/Makefile.modpost:92: 
recipe for target '__modpost' failed
make[5]: *** [modules] Error 2
/usr/tzinti/build/kernel/tekitl-4.14.2/linux/Makefile:1228: recipe for target 
'modules' failed
make[5]: *** Waiting for unfinished jobs
MKPIGGY arch/x86/boot/compressed/piggy.S
AS  arch/x86/boot/compressed/piggy.o
DATAREL arch/x86/boot/compressed/vmlinux
LD  arch/x86/boot/compressed/vmlinux
ZOFFSET arch/x86/boot/zoffset.h
OBJCOPY arch/x86/boot/vmlinux.bin
AS  arch/x86/boot/header.o
LD  arch/x86/boot/setup.elf
OBJCOPY arch/x86/boot/setup.bin
BUILD   arch/x86/boot/bzImage
Setup is 17212 bytes (padded to 17408 bytes).
System is 4433 kB
CRC 231e180a
Kernel: arch/x86/boot/bzImage is ready  (#1)
make[4]: *** [sub-make] Error 2
Makefile:146: recipe for target 'sub-make' failed
make[3]: *** [__sub-make] Error 2
Makefile:24: recipe for target '__sub-make' failed
make[3]: Leaving directory 
'/usr/tzinti/build/kernel/tekitl-4.14.2/linux/debian/build/build_amd64_none_amd64'
make[2]: *** [debian/stamps/build_amd64_none_amd64] Error 2
debian/rules.real:190: recipe for target 'debian/stamps/build_amd64_none_amd64' 
failed
make[2]: Leaving directory '/usr/tzinti/build/kernel/tekitl-4.14.2/linux'
make[1]: *** [binary-arch_amd64_none_amd64_real] Error 2
debian/rules.gen:24: recipe for target 'binary-arch_amd64_none_amd64_real' 
failed
make[1]: Leaving directory '/usr/tzinti/build/kernel/tekitl-4.14.2/linux'
make: *** [binary-arch] Error 2
debian/rules:50: recipe for target 'binary-arch' failed
dpkg-buildpackage: error: fakeroot debian/rules binary-arch gave error exit 
status 2


Best Professional Regards.


Thanks again, Ed.


Best Professional Regards.

Re: Reiser4 for Linux-4.14, Reiser4progs-1.2.0, Libaal-1.0.7, Format 4.0.2

2017-11-28 Thread Metztli Information Technology 
Appreciated Ed.

> Hello,
>
> Please, download reiser4-for-4.14.1.patch which contains the fixup.
>
Updated patch works but had a rough time during the build procedure because 
zstd is used by btrfs as well:
...
some modules are in more than one package
debian/reiser4-modules-4.14.0-1+reiser4.0.2-amd64-di 
lib/modules/4.14.0-1+reiser4.0.2-amd64/kernel/lib/xxhash.ko
debian/btrfs-modules-4.14.0-1+reiser4.0.2-amd64-di 
lib/modules/4.14.0-1+reiser4.0.2-amd64/kernel/lib/xxhash.ko
debian/reiser4-modules-4.14.0-1+reiser4.0.2-amd64-di 
lib/modules/4.14.0-1+reiser4.0.2-amd64/kernel/lib/zstd/zstd_compress.ko
debian/btrfs-modules-4.14.0-1+reiser4.0.2-amd64-di 
lib/modules/4.14.0-1+reiser4.0.2-amd64/kernel/lib/zstd/zstd_compress.ko
debian/reiser4-modules-4.14.0-1+reiser4.0.2-amd64-di 
lib/modules/4.14.0-1+reiser4.0.2-amd64/kernel/lib/zstd/zstd_decompress.ko
debian/btrfs-modules-4.14.0-1+reiser4.0.2-amd64-di 
lib/modules/4.14.0-1+reiser4.0.2-amd64/kernel/lib/zstd/zstd_decompress.ko
command exited with status 1
make[2]: *** [install-udeb_amd64] Error 2
debian/rules.real:498: recipe for target 'install-udeb_amd64' failed
make[2]: Leaving directory '/usr/tzinti/build/kernel/tekitl-4.14.2/linux'
make[1]: *** [binary-arch_amd64] Error 2
debian/rules.gen:18: recipe for target 'binary-arch_amd64' failed
make[1]: Leaving directory '/usr/tzinti/build/kernel/tekitl-4.14.2/linux'
make: *** [binary-arch] Error 2
debian/rules:50: recipe for target 'binary-arch' failed
dpkg-buildpackage: error: fakeroot debian/rules binary-arch gave error exit 
status 2

< https://pbs.twimg.com/media/DPuO9nKU8AEMTgx.jpg:large >

Accordingly, in order for the build to proceed past the kernel-wedge show 
stopper, I had to

touch debian/installer/amd64/ignore-dups
< https://github.com/pexip/os-kernel-wedge >
i.e.,

% kernel-wedge help find-dups
find-dups kernel-name

Find duplicate modules. Pass the kernel name.

Return 1 if any duplicates are found, unless $KW_CHECK_NONFATAL is
non-empty or the configuration file 'ignore-dups' exists.
--

And the build procedure completed successfully at long last.

>
> On 11/27/2017 03:37 PM, Metztli Information Technology wrote:
>>
>> Niltze, Ed-
>>
>>
>> I've built libaal-1.0.7 and Reiser4progs-1.2.0 Debian packages for AMD64 
>> successfully and currently testing in a virtual machine.
>>
>> I've applied reiser4-for-4.14.0 patch to upstream kernel 4.14.2; Debian 
>> packaging for 4.14.2-xyz required GCC-7 for kernel build
>>
>>   -- which I installed including relevant dependencies. Yet I have 
>> experienced (twice) the appended tail show stopper error:
>> ...
>>
>>CC  arch/x86/boot/compressed/pagetable.o
>>CC  arch/x86/boot/compressed/eboot.o
>>AS  arch/x86/boot/compressed/efi_stub_64.o
>>AS  arch/x86/boot/compressed/efi_thunk_64.o
>>CC  arch/x86/boot/compressed/misc.o
>>XZKERN  arch/x86/boot/compressed/vmlinux.bin.xz
>> ERROR: "find_get_pages_range" [fs/reiser4/reiser4.ko] undefined!
>> make[6]: *** [__modpost] Error 1
>> /usr/tzinti/build/kernel/tekitl-4.14.2/linux/scripts/Makefile.modpost:92: 
>> recipe for target '__modpost' failed
>> make[5]: *** [modules] Error 2
>> /usr/tzinti/build/kernel/tekitl-4.14.2/linux/Makefile:1228: recipe for 
>> target 'modules' failed
>> make[5]: *** Waiting for unfinished jobs
>>MKPIGGY arch/x86/boot/compressed/piggy.S
>>AS  arch/x86/boot/compressed/piggy.o
>>DATAREL arch/x86/boot/compressed/vmlinux
>>LD  arch/x86/boot/compressed/vmlinux
>>ZOFFSET arch/x86/boot/zoffset.h
>>OBJCOPY arch/x86/boot/vmlinux.bin
>>AS  arch/x86/boot/header.o
>>LD  arch/x86/boot/setup.elf
>>OBJCOPY arch/x86/boot/setup.bin
>>BUILD   arch/x86/boot/bzImage
>> Setup is 17212 bytes (padded to 17408 bytes).
>> System is 4433 kB
>> CRC 231e180a
>> Kernel: arch/x86/boot/bzImage is ready  (#1)
>> make[4]: *** [sub-make] Error 2
>> Makefile:146: recipe for target 'sub-make' failed
>> make[3]: *** [__sub-make] Error 2
>> Makefile:24: recipe for target '__sub-make' failed
>> make[3]: Leaving directory 
>> '/usr/tzinti/build/kernel/tekitl-4.14.2/linux/debian/build/build_amd64_none_amd64'
>> make[2]: *** [debian/stamps/build_amd64_none_amd64] Error 2
>> debian/rules.real:190: recipe for target 
>> 'debian/stamps/build_amd64_none_amd64' failed
>> make[2]: Leaving directory '/usr/tzinti/build/kernel/tekitl-4.14.2/linux'
>> make[1]: *** [binary-arch_amd64_none_amd64_real] Error 2
>> debian/rules.gen:24: recipe for target 'binary-arch_amd64_none_amd64_real' 
>> failed
>> make[1]: Leaving directory '/usr/tzinti/build/kernel/tekitl-4.14.2/linux'
>> make: *** [binary-arch] Error 2
>> debian/rules:50: recipe for target 'binary-arch' failed
>> dpkg-buildpackage: error: fakeroot debian/rules binary-arch gave error exit 
>> status 2
>>
>>
>> Best Professional Regards.
>>
>

Thanks again, Ed.


Best Professional Regards.

-- 
Jose R R
http://metztli.it

Bug#872560: Related issues

2017-11-28 Thread Yuri D'Elia 
FYI, this also has implications for systemd.
See the following bug report:

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

and the related upstream:

  https://github.com/systemd/systemd/issues/7054