[REGRESSION] 5.8-rc3: seccomp crash with Chromium, QtWebEngine and related browsers: seccomp-bpf failure in syscall 0072

2020-06-29 Thread Martin Steigerwald
Dear Andy, Kees, Will, dear kernel community, With 5.8-rc3 there is a seccomp related crash which prevents Chromium and QtWebEngine from starting: Bug 208369 - seccomp crash with Chromium, QtWebEngine and related browsers: seccomp-bpf failure in syscall 0072

Re: Linux 5.3-rc8

2019-09-19 Thread Martin Steigerwald
Dear Lennart. Lennart Poettering - 18.09.19, 15:53:25 CEST: > On Mi, 18.09.19 00:10, Martin Steigerwald (mar...@lichtvoll.de) wrote: > > > getrandom() will never "consume entropy" in a way that will block > > > any > > > users of getrandom(). If

Re: Linux 5.3-rc8

2019-09-17 Thread Martin Steigerwald
Matthew Garrett - 17.09.19, 23:52:00 CEST: > On Tue, Sep 17, 2019 at 11:38:33PM +0200, Martin Steigerwald wrote: > > My understanding of entropy always has been that only a certain > > amount of it can be produced in a certain amount of time. If that > > is wrong… please by al

Re: Linux 5.3-rc8

2019-09-17 Thread Martin Steigerwald
Ahmed S. Darwish - 17.09.19, 22:52:34 CEST: > On Tue, Sep 17, 2019 at 10:28:47PM +0200, Martin Steigerwald wrote: > [...] > > > I don't have any kernel logs old enough to see whether whether crng > > init times have been different with Systemd due to asking for > > r

Re: Linux 5.3-rc8

2019-09-17 Thread Martin Steigerwald
Willy Tarreau - 17.09.19, 19:29:29 CEST: > On Tue, Sep 17, 2019 at 07:13:28PM +0200, Lennart Poettering wrote: > > On Di, 17.09.19 18:21, Willy Tarreau (w...@1wt.eu) wrote: > > > On Tue, Sep 17, 2019 at 05:57:43PM +0200, Lennart Poettering > > > wrote: > > > > Note that calling getrandom(0) "too

Re: Linux 5.3-rc8

2019-09-17 Thread Martin Steigerwald
Willy Tarreau - 17.09.19, 18:21:37 CEST: > On Tue, Sep 17, 2019 at 05:57:43PM +0200, Lennart Poettering wrote: > > Note that calling getrandom(0) "too early" is not something people > > do > > on purpose. It happens by accident, i.e. because we live in a world > > where SSH or HTTPS or so is run

Re: Linux 5.3-rc8

2019-09-17 Thread Martin Steigerwald
Linus Torvalds - 17.09.19, 20:01:23 CEST: > > We can make boot hang in "sane", discoverable way. > > That is certainly a huge advantage, yes. Right now I suspect that what > has happened is that this has probably been going on as some > low-level background noise for a while, and people either

Re: Linux 5.3-rc8

2019-09-17 Thread Martin Steigerwald
Willy Tarreau - 17.09.19, 10:35:16 CEST: > On Tue, Sep 17, 2019 at 09:33:40AM +0200, Martin Steigerwald wrote: > > However this again would be burdening users with an issue they > > should > > not have to care about. Unless userspace developers care enough and > >

Re: Linux 5.3-rc8

2019-09-17 Thread Martin Steigerwald
Willy Tarreau - 17.09.19, 07:24:38 CEST: > On Mon, Sep 16, 2019 at 06:46:07PM -0700, Matthew Garrett wrote: > > >Well, the patch actually made getrandom() return en error too, but > > >you seem more interested in the hypotheticals than in arguing > > >actualities.> > > If you want to be safe,

a sane approach to random numbers (was: Re: Linux 5.3-rc8)

2019-09-17 Thread Martin Steigerwald
As this is not about Linux 5.3-rc8 anymore I took the liberty to change the subject. Linus Torvalds - 17.09.19, 01:05:47 CEST: > On Mon, Sep 16, 2019 at 4:02 PM Matthew Garrett > wrote: > > The semantics many people want for secure key generation is urandom, > > but with a guarantee that it's

Re: Linux 5.3-rc8

2019-09-14 Thread Martin Steigerwald
Ahmed S. Darwish - 14.09.19, 23:11:26 CEST: > > Yeah, the above is yet another example of completely broken garbage. > > > > You can't just wait and block at boot. That is simply 100% > > unacceptable, and always has been, exactly because that may > > potentially mean waiting forever since you

Re: DRM-based Oops viewer

2019-03-10 Thread Martin Steigerwald
Hell Ahmed. Ahmed S. Darwish - 10.03.19, 02:31: > Hello DRM/UEFI maintainers, > > Several years ago, I wrote a set of patches to dump the kernel > log to disk upon panic -- through BIOS INT 0x13 services. [1] > > The overwhelming response was that it's unsafe to do this in a > generic manner.

Re: Bug#919356: Licensing of include/linux/hash.h

2019-02-12 Thread Martin Steigerwald
On 2/11/19 11:27 PM, Ben Finney wrote: > Martin Steigerwald writes: > >> Well the file has in its header: >> >> /* Fast hashing routine for a long. >>(C) 2002 William Lee Irwin III, IBM */ >> >> /* >> * Knuth recommends primes in approxim

Re: Bug#919356: Licensing of include/linux/hash.h

2019-02-12 Thread Martin Steigerwald
Jens Axboe - 12.02.19, 17:16: > On 2/11/19 11:27 PM, Ben Finney wrote: > > Martin Steigerwald writes: > >> Well the file has in its header: > >> > >> /* Fast hashing routine for a long. > >> > >>(C) 2002 William Lee Irwin III, IBM

Re: [REGRESSION] 5.0-rc2: iptables -nvL consumes 100% of CPU and hogs memory with kernel 5.0-rc2

2019-01-15 Thread Martin Steigerwald
Florian Westphal - 15.01.19, 11:15: > Michal Kubecek wrote: > > > I upgraded to self-compiled 5.0-rc2 today and found the machine to > > > be slow after startup. I saw iptables consuming 100% CPU, it only > > > responded to SIGKILL. It got restarted several times, probably by > > > some systemd

[REGRESSION] 5.0-rc2: iptables -nvL consumes 100% of CPU and hogs memory with kernel 5.0-rc2

2019-01-14 Thread Martin Steigerwald
Hi! Does that ring a bell with someone? For now I just downgraded, no time for detailed analysis. Debian bug report at: iptables -nvL consumes 100% of CPU and hogs memory with kernel 5.0-rc2 https://bugs.debian.org/919325 4.20 works, 5.0-rc2 showed this issue with iptables. Configurations

Re: [PATCH v2] Document /proc/pid PID reuse behavior

2018-11-07 Thread Martin Steigerwald
Michal Hocko - 07.11.18, 17:00: > > > otherwise anybody could simply DoS the system > > > by consuming all available pids. > > > > People can do that today using the instrument of terror widely known > > as fork(2). The only thing standing between fork(2) and a full > > process table is

Re: [PATCH v2] Document /proc/pid PID reuse behavior

2018-11-07 Thread Martin Steigerwald
Michal Hocko - 07.11.18, 17:00: > > > otherwise anybody could simply DoS the system > > > by consuming all available pids. > > > > People can do that today using the instrument of terror widely known > > as fork(2). The only thing standing between fork(2) and a full > > process table is

Re: [REGRESSION 4.19-rc2] sometimes hangs with black screen when resuming from suspend or hibernation (was: Re: Linux 4.19-rc2)

2018-10-26 Thread Martin Steigerwald
This regression is gone with 4.19-rc8. Thanks, Martin Martin Steigerwald - 11.09.18, 09:53: […] > Linus Torvalds - 02.09.18, 23:45: > > As usual, the rc2 release is pretty small. People are taking a > > With 4.19-rc2 this ThinkPad T520 with i5 Sandybrdige sometimes hangs >

Re: [REGRESSION 4.19-rc2] sometimes hangs with black screen when resuming from suspend or hibernation (was: Re: Linux 4.19-rc2)

2018-10-26 Thread Martin Steigerwald
This regression is gone with 4.19-rc8. Thanks, Martin Martin Steigerwald - 11.09.18, 09:53: […] > Linus Torvalds - 02.09.18, 23:45: > > As usual, the rc2 release is pretty small. People are taking a > > With 4.19-rc2 this ThinkPad T520 with i5 Sandybrdige sometimes hangs >

Re: Linux 4.19-rc4 released, an apology, and a maintainership note

2018-09-30 Thread Martin Steigerwald
l...@lkcl.net - 30.09.18, 14:09: > > That written: Quite some of the rude mails that contained swearwords > > I read from you have been about code, not persons. I think this is > > an important distinction. I do not have much of an issue with > > swearing at code :), especially when it is in some

Re: Linux 4.19-rc4 released, an apology, and a maintainership note

2018-09-30 Thread Martin Steigerwald
l...@lkcl.net - 30.09.18, 14:09: > > That written: Quite some of the rude mails that contained swearwords > > I read from you have been about code, not persons. I think this is > > an important distinction. I do not have much of an issue with > > swearing at code :), especially when it is in some

Re: Code of Conduct: Let's revamp it.

2018-09-26 Thread Martin Steigerwald
Pavel Machek - 25.09.18, 15:28: > > > > > Your above argument that the Code of Conduct is problematic > > > > > because of who wrote it seems to contradict your statement > > > > > that we shall judge by code (or text) alone. > > > > > > > > I think there are important differences between code to

Re: Code of Conduct: Let's revamp it.

2018-09-26 Thread Martin Steigerwald
Pavel Machek - 25.09.18, 15:28: > > > > > Your above argument that the Code of Conduct is problematic > > > > > because of who wrote it seems to contradict your statement > > > > > that we shall judge by code (or text) alone. > > > > > > > > I think there are important differences between code to

Re: Code of Conduct: Let's revamp it.

2018-09-21 Thread Martin Steigerwald
Hello Christoph. Christoph Conrads - 20.09.18, 23:18: > The CoC is extremely ambiguously written for an enforceable document, > any behavior disliked by the maintainers can be punished, and the > level of naivete of the maintainers defending it is suprising for > such a far reaching document.

Re: Code of Conduct: Let's revamp it.

2018-09-21 Thread Martin Steigerwald
Hello Christoph. Christoph Conrads - 20.09.18, 23:18: > The CoC is extremely ambiguously written for an enforceable document, > any behavior disliked by the maintainers can be punished, and the > level of naivete of the maintainers defending it is suprising for > such a far reaching document.

Re: [PATCH security-next v2 00/26] LSM: Explict LSM ordering

2018-09-20 Thread Martin Steigerwald
Kees Cook - 20.09.18, 18:23: > v2: > - add "lsm.order=" and CONFIG_LSM_ORDER instead of overloading > "security=" - reorganize introduction of ordering logic code > > Updated cover letter: > > This refactors the LSM registration and initialization infrastructure > to more centrally support

Re: [PATCH security-next v2 00/26] LSM: Explict LSM ordering

2018-09-20 Thread Martin Steigerwald
Kees Cook - 20.09.18, 18:23: > v2: > - add "lsm.order=" and CONFIG_LSM_ORDER instead of overloading > "security=" - reorganize introduction of ordering logic code > > Updated cover letter: > > This refactors the LSM registration and initialization infrastructure > to more centrally support

Re: […] an apology, and a maintainership note

2018-09-17 Thread Martin Steigerwald
Martin Steigerwald - 17.09.18, 09:57: > Dear Linus. > > Linus Torvalds - 16.09.18, 21:22: > > This is my reality. I am not an emotionally empathetic kind of > > person and that probably doesn't come as a big surprise to anybody. > > Least of all me. The fact

Re: […] an apology, and a maintainership note

2018-09-17 Thread Martin Steigerwald
Martin Steigerwald - 17.09.18, 09:57: > Dear Linus. > > Linus Torvalds - 16.09.18, 21:22: > > This is my reality. I am not an emotionally empathetic kind of > > person and that probably doesn't come as a big surprise to anybody. > > Least of all me. The fact

Re: […] an apology, and a maintainership note

2018-09-17 Thread Martin Steigerwald
Dear Linus. Linus Torvalds - 16.09.18, 21:22: > This is my reality. I am not an emotionally empathetic kind of person > and that probably doesn't come as a big surprise to anybody. Least > of all me. The fact that I then misread people and don't realize > (for years) how badly I've judged a

Re: […] an apology, and a maintainership note

2018-09-17 Thread Martin Steigerwald
Dear Linus. Linus Torvalds - 16.09.18, 21:22: > This is my reality. I am not an emotionally empathetic kind of person > and that probably doesn't come as a big surprise to anybody. Least > of all me. The fact that I then misread people and don't realize > (for years) how badly I've judged a

Re: [Intel-gfx] [REGRESSION 4.19-rc2] sometimes hangs with black screen when resuming from suspend or hibernation (was: Re: Linux 4.19-rc2)

2018-09-12 Thread Martin Steigerwald
Ville Syrjälä - 12.09.18, 19:10: > On Tue, Sep 11, 2018 at 12:17:05PM +0200, Martin Steigerwald wrote: > > Cc´d Intel Gfx mailing list, in case somebody there knows something: > > > > Cc´d Thorsten for regression tracking… forgot initially. Can also > > open bug report

Re: [Intel-gfx] [REGRESSION 4.19-rc2] sometimes hangs with black screen when resuming from suspend or hibernation (was: Re: Linux 4.19-rc2)

2018-09-12 Thread Martin Steigerwald
Ville Syrjälä - 12.09.18, 19:10: > On Tue, Sep 11, 2018 at 12:17:05PM +0200, Martin Steigerwald wrote: > > Cc´d Intel Gfx mailing list, in case somebody there knows something: > > > > Cc´d Thorsten for regression tracking… forgot initially. Can also > > open bug report

Re: [REGRESSION 4.19-rc2] sometimes hangs with black screen when resuming from suspend or hibernation (was: Re: Linux 4.19-rc2)

2018-09-11 Thread Martin Steigerwald
:01 AM Martin Steigerwald wrote: > > Hi. > > > > Linus Torvalds - 02.09.18, 23:45: > > > As usual, the rc2 release is pretty small. People are taking a > > > > With 4.19-rc2 this ThinkPad T520 with i5 Sandybrdige sometimes hangs > > with black

Re: [REGRESSION 4.19-rc2] sometimes hangs with black screen when resuming from suspend or hibernation (was: Re: Linux 4.19-rc2)

2018-09-11 Thread Martin Steigerwald
:01 AM Martin Steigerwald wrote: > > Hi. > > > > Linus Torvalds - 02.09.18, 23:45: > > > As usual, the rc2 release is pretty small. People are taking a > > > > With 4.19-rc2 this ThinkPad T520 with i5 Sandybrdige sometimes hangs > > with black

[REGRESSION 4.19-rc2] sometimes hangs with black screen when resuming from suspend or hibernation (was: Re: Linux 4.19-rc2)

2018-09-11 Thread Martin Steigerwald
Hi. Linus Torvalds - 02.09.18, 23:45: > As usual, the rc2 release is pretty small. People are taking a With 4.19-rc2 this ThinkPad T520 with i5 Sandybrdige sometimes hangs with black screen when resuming from suspend or hibernation. With 4.18.1 it did not. Of course there have been userspace

[REGRESSION 4.19-rc2] sometimes hangs with black screen when resuming from suspend or hibernation (was: Re: Linux 4.19-rc2)

2018-09-11 Thread Martin Steigerwald
Hi. Linus Torvalds - 02.09.18, 23:45: > As usual, the rc2 release is pretty small. People are taking a With 4.19-rc2 this ThinkPad T520 with i5 Sandybrdige sometimes hangs with black screen when resuming from suspend or hibernation. With 4.18.1 it did not. Of course there have been userspace

Re: POSIX violation by writeback error

2018-09-05 Thread Martin Steigerwald
Rogier Wolff - 05.09.18, 10:04: > On Wed, Sep 05, 2018 at 09:39:58AM +0200, Martin Steigerwald wrote: > > Rogier Wolff - 05.09.18, 09:08: > > > So when a mail queuer puts mail the mailq files and the mail > > > processor can get them out of there intact, nobody is goin

Re: POSIX violation by writeback error

2018-09-05 Thread Martin Steigerwald
Rogier Wolff - 05.09.18, 10:04: > On Wed, Sep 05, 2018 at 09:39:58AM +0200, Martin Steigerwald wrote: > > Rogier Wolff - 05.09.18, 09:08: > > > So when a mail queuer puts mail the mailq files and the mail > > > processor can get them out of there intact, nobody is goin

Re: POSIX violation by writeback error

2018-09-05 Thread Martin Steigerwald
Rogier Wolff - 05.09.18, 09:08: > So when a mail queuer puts mail the mailq files and the mail processor > can get them out of there intact, nobody is going to notice. (I know > mail queuers should call fsync and report errors when that fails, but > there are bound to be applications where

Re: POSIX violation by writeback error

2018-09-05 Thread Martin Steigerwald
Rogier Wolff - 05.09.18, 09:08: > So when a mail queuer puts mail the mailq files and the mail processor > can get them out of there intact, nobody is going to notice. (I know > mail queuers should call fsync and report errors when that fails, but > there are bound to be applications where

Re: POSIX violation by writeback error

2018-09-05 Thread Martin Steigerwald
Jeff Layton - 04.09.18, 17:44: > > - If the following read() could be served by a page in memory, just > > returns the data. If the following read() could not be served by a > > page in memory and the inode/address_space has a writeback error > > mark, returns EIO. If there is a writeback error on

Re: POSIX violation by writeback error

2018-09-05 Thread Martin Steigerwald
Jeff Layton - 04.09.18, 17:44: > > - If the following read() could be served by a page in memory, just > > returns the data. If the following read() could not be served by a > > page in memory and the inode/address_space has a writeback error > > mark, returns EIO. If there is a writeback error on

Re: Amiga RDB partition support for disks >= 2 TB

2018-06-28 Thread Martin Steigerwald
Martin Steigerwald - 28.06.18, 13:30: > jdow - 28.06.18, 12:00: > > On 20180628 01:16, Martin Steigerwald wrote: > […] > > > >> That brings to the fore an interesting question. Why bother with > > >> RDBs > > >> over 2TB unless you want

Re: Amiga RDB partition support for disks >= 2 TB

2018-06-28 Thread Martin Steigerwald
Martin Steigerwald - 28.06.18, 13:30: > jdow - 28.06.18, 12:00: > > On 20180628 01:16, Martin Steigerwald wrote: > […] > > > >> That brings to the fore an interesting question. Why bother with > > >> RDBs > > >> over 2TB unless you want

Re: Amiga RDB partition support for disks >= 2 TB

2018-06-28 Thread Martin Steigerwald
jdow - 28.06.18, 12:00: > On 20180628 01:16, Martin Steigerwald wrote: […] > >> That brings to the fore an interesting question. Why bother with > >> RDBs > >> over 2TB unless you want a disk with one single partition? This > >> Win10 > >> monst

Re: Amiga RDB partition support for disks >= 2 TB

2018-06-28 Thread Martin Steigerwald
jdow - 28.06.18, 12:00: > On 20180628 01:16, Martin Steigerwald wrote: […] > >> That brings to the fore an interesting question. Why bother with > >> RDBs > >> over 2TB unless you want a disk with one single partition? This > >> Win10 > >> monst

Amiga RDB partition support for disks >= 2 TB (was: Re: moving affs + RDB partition support to staging?)

2018-06-28 Thread Martin Steigerwald
r > >>>>>>> than > >>>>>>> enabling use of disk and partitions larger than 2 TB (which > >>>>>>> may have > >>>>>>> ramifications with filesystems on these partitions). So > >>>>>>&

Amiga RDB partition support for disks >= 2 TB (was: Re: moving affs + RDB partition support to staging?)

2018-06-28 Thread Martin Steigerwald
r > >>>>>>> than > >>>>>>> enabling use of disk and partitions larger than 2 TB (which > >>>>>>> may have > >>>>>>> ramifications with filesystems on these partitions). So > >>>>>>&

Amiga RDB partition support for disks >= 2 TB (was: Re: moving affs + RDB partition support to staging?)

2018-06-28 Thread Martin Steigerwald
t;>>> may have found a few issues when he looked at the AFFS code so > >>>>>> I > >>>>>> won't > >>>>>> say more). Anyway partitioning tools and filesystems are > >>>>>> unrelated

Amiga RDB partition support for disks >= 2 TB (was: Re: moving affs + RDB partition support to staging?)

2018-06-28 Thread Martin Steigerwald
t;>>> may have found a few issues when he looked at the AFFS code so > >>>>>> I > >>>>>> won't > >>>>>> say more). Anyway partitioning tools and filesystems are > >>>>>> unrelated

Re: Amiga RDB partition support for disks >= 2 TB (was: Re: moving affs + RDB partition support to staging?)

2018-06-28 Thread Martin Steigerwald
rt in native OS, but spare myself the extra kernel option stuff. It is Michael´s call tough, as he submits the patch. And if he chooses to be on a safer side than this, that is fine with me. Thanks, Martin > On 20180627 01:03, Martin Steigerwald wrote: > > Dear Joanne. > >

Re: Amiga RDB partition support for disks >= 2 TB (was: Re: moving affs + RDB partition support to staging?)

2018-06-28 Thread Martin Steigerwald
rt in native OS, but spare myself the extra kernel option stuff. It is Michael´s call tough, as he submits the patch. And if he chooses to be on a safer side than this, that is fine with me. Thanks, Martin > On 20180627 01:03, Martin Steigerwald wrote: > > Dear Joanne. > >

Re: moving affs + RDB partition support to staging?

2018-06-27 Thread Martin Steigerwald
t;>> was getting tied into a gordian knot. > >>>> > >>>> {^_^} > >>>> > >>>> On 20180625 19:23, Michael Schmitz wrote: > >>>>> Joanne, > >>>>> > >>>>> Mart

Re: moving affs + RDB partition support to staging?

2018-06-27 Thread Martin Steigerwald
t;>> was getting tied into a gordian knot. > >>>> > >>>> {^_^} > >>>> > >>>> On 20180625 19:23, Michael Schmitz wrote: > >>>>> Joanne, > >>>>> > >>>>> Mart

Re: moving affs + RDB partition support to staging?

2018-06-27 Thread Martin Steigerwald
21:19:09 merkaba kernel: [ 7891.844055] sd 7:0:0:0: [sdb] > >>>> Attached SCSI disk > >>>> > >>>> so it's indeed a case of self inflicted damage (RDSK (512) means > >>>> 512 > >>>> byte blocks) and can be worked around by

Re: moving affs + RDB partition support to staging?

2018-06-27 Thread Martin Steigerwald
21:19:09 merkaba kernel: [ 7891.844055] sd 7:0:0:0: [sdb] > >>>> Attached SCSI disk > >>>> > >>>> so it's indeed a case of self inflicted damage (RDSK (512) means > >>>> 512 > >>>> byte blocks) and can be worked around by

Re: moving affs + RDB partition support to staging?

2018-06-26 Thread Martin Steigerwald
gt;> If memory serves the RDBs think in blocks rather than bytes so it > >> should work up to 2 gigablocks whatever your block size is. 512 > >> blocks is 219902322 bytes. But that wastes just a WHOLE LOT of > >> disk in block maps. Go up to 4096 or 8192. The

Re: moving affs + RDB partition support to staging?

2018-06-26 Thread Martin Steigerwald
gt;> If memory serves the RDBs think in blocks rather than bytes so it > >> should work up to 2 gigablocks whatever your block size is. 512 > >> blocks is 219902322 bytes. But that wastes just a WHOLE LOT of > >> disk in block maps. Go up to 4096 or 8192. The

Re: moving affs + RDB partition support to staging?

2018-06-26 Thread Martin Steigerwald
Michael. Michael Schmitz - 26.06.18, 04:23: > Joanne, > > Martin's boot log (including your patch) says: > > Jun 19 21:19:09 merkaba kernel: [ 7891.843284] sdb: RDSK (512) sdb1 > (LNX^@)(res 2 spb 1) sdb2 (JXF^D)(res 2 spb 1) sdb3 (DOS^C)(res 2 spb > 4) > Jun 19 21:19:09 merkaba kernel: [

Re: moving affs + RDB partition support to staging?

2018-06-26 Thread Martin Steigerwald
Michael. Michael Schmitz - 26.06.18, 04:23: > Joanne, > > Martin's boot log (including your patch) says: > > Jun 19 21:19:09 merkaba kernel: [ 7891.843284] sdb: RDSK (512) sdb1 > (LNX^@)(res 2 spb 1) sdb2 (JXF^D)(res 2 spb 1) sdb3 (DOS^C)(res 2 spb > 4) > Jun 19 21:19:09 merkaba kernel: [

Re: moving affs + RDB partition support to staging? (was: Re: Moving unmaintained filesystems to staging)

2018-06-25 Thread Martin Steigerwald
68k build host. Thanks, Martin > > Cheers, > > Michael > > Am 24.06.18 um 21:06 schrieb Martin Steigerwald: > > Hi. > > > > Michael Schmitz - 27.04.18, 04:11: > >> test results at https://bugzilla.kernel.org/show_bug.cgi?id=43511 > >&

Re: moving affs + RDB partition support to staging? (was: Re: Moving unmaintained filesystems to staging)

2018-06-25 Thread Martin Steigerwald
68k build host. Thanks, Martin > > Cheers, > > Michael > > Am 24.06.18 um 21:06 schrieb Martin Steigerwald: > > Hi. > > > > Michael Schmitz - 27.04.18, 04:11: > >> test results at https://bugzilla.kernel.org/show_bug.cgi?id=43511 > >&

Re: moving affs + RDB partition support to staging? (was: Re: Moving unmaintained filesystems to staging)

2018-06-24 Thread Martin Steigerwald
Hi. Michael Schmitz - 27.04.18, 04:11: > test results at https://bugzilla.kernel.org/show_bug.cgi?id=43511 > indicate the RDB parser bug is fixed by the patch given there, so if > Martin now submits the patch, all should be well? Ok, better be honest than having anyone waiting for it: I do not

Re: moving affs + RDB partition support to staging? (was: Re: Moving unmaintained filesystems to staging)

2018-06-24 Thread Martin Steigerwald
Hi. Michael Schmitz - 27.04.18, 04:11: > test results at https://bugzilla.kernel.org/show_bug.cgi?id=43511 > indicate the RDB parser bug is fixed by the patch given there, so if > Martin now submits the patch, all should be well? Ok, better be honest than having anyone waiting for it: I do not

Linux on Intel x86: How to disable Hyperthreading

2018-06-23 Thread Martin Steigerwald
Cc´d people for X86 architecture in MAINTAINERS. Hi! According to https://www.kuketz-blog.de/tlbleed-neue-sicherheitsluecken-bei-intel-cpus/ in https://www.blackhat.com/us-18/briefings/schedule/#tlbleed-when-protecting-your-cpu-caches-is-not-enough-10149 (Firefox and Chromium with current

Linux on Intel x86: How to disable Hyperthreading

2018-06-23 Thread Martin Steigerwald
Cc´d people for X86 architecture in MAINTAINERS. Hi! According to https://www.kuketz-blog.de/tlbleed-neue-sicherheitsluecken-bei-intel-cpus/ in https://www.blackhat.com/us-18/briefings/schedule/#tlbleed-when-protecting-your-cpu-caches-is-not-enough-10149 (Firefox and Chromium with current

Re: moving affs + RDB partition support to staging?

2018-05-07 Thread Martin Steigerwald
Michael Schmitz - 07.05.18, 04:40: > Al, > > I don't think there is USB sticks with affs on them as yet. There > isn't even USB host controller support for Amiga hardware (yet). > > Last I tried USB on m68k (Atari, 060 accelerator) the desktop > experience was such that I'd rather not repeat

Re: moving affs + RDB partition support to staging?

2018-05-07 Thread Martin Steigerwald
Michael Schmitz - 07.05.18, 04:40: > Al, > > I don't think there is USB sticks with affs on them as yet. There > isn't even USB host controller support for Amiga hardware (yet). > > Last I tried USB on m68k (Atari, 060 accelerator) the desktop > experience was such that I'd rather not repeat

Re: moving affs + RDB partition support to staging?

2018-05-06 Thread Martin Steigerwald
Al Viro - 06.05.18, 02:59: > On Thu, Apr 26, 2018 at 12:45:41PM +0200, John Paul Adrian Glaubitz wrote: > > Exactly. It works fine as is: > > > > root@elgar:~> uname -a > > Linux elgar 4.16.0-rc2-amiga-16784-ga8917fc #650 Mon Mar 5 15:32:52 > > NZDT 2018 m68k GNU/Linux root@elgar:~> mount

Re: moving affs + RDB partition support to staging?

2018-05-06 Thread Martin Steigerwald
Al Viro - 06.05.18, 02:59: > On Thu, Apr 26, 2018 at 12:45:41PM +0200, John Paul Adrian Glaubitz wrote: > > Exactly. It works fine as is: > > > > root@elgar:~> uname -a > > Linux elgar 4.16.0-rc2-amiga-16784-ga8917fc #650 Mon Mar 5 15:32:52 > > NZDT 2018 m68k GNU/Linux root@elgar:~> mount

Re: moving affs + RDB partition support to staging?

2018-05-06 Thread Martin Steigerwald
John Paul Adrian Glaubitz - 06.05.18, 10:52: > On 04/27/2018 03:26 AM, jdow wrote: > > And before I forget there are two features of the RDBs that I > > heartily recommend never implementing on Linux. They were good > > ideas at the time; but, times changed. The RDBs are capable of > > storing a

Re: moving affs + RDB partition support to staging?

2018-05-06 Thread Martin Steigerwald
John Paul Adrian Glaubitz - 06.05.18, 10:52: > On 04/27/2018 03:26 AM, jdow wrote: > > And before I forget there are two features of the RDBs that I > > heartily recommend never implementing on Linux. They were good > > ideas at the time; but, times changed. The RDBs are capable of > > storing a

Spectre V2: Eight new security holes in Intel processors

2018-05-03 Thread Martin Steigerwald
Hello. It seems there are eight new security holes alongside the Spectre/ Meltdown CPU design issues: https://www.heise.de/security/meldung/Spectre-NG-Intel-Prozessoren-von-neuen-hochriskanten-Sicherheitsluecken-betroffen-4039302.html (german language only, only found german language reports

Spectre V2: Eight new security holes in Intel processors

2018-05-03 Thread Martin Steigerwald
Hello. It seems there are eight new security holes alongside the Spectre/ Meltdown CPU design issues: https://www.heise.de/security/meldung/Spectre-NG-Intel-Prozessoren-von-neuen-hochriskanten-Sicherheitsluecken-betroffen-4039302.html (german language only, only found german language reports

Re: moving affs + RDB partition support to staging? (was: Re: Moving unmaintained filesystems to staging)

2018-04-27 Thread Martin Steigerwald
Geert Uytterhoeven - 26.04.18, 13:08: > On Thu, Apr 26, 2018 at 12:28 PM, Martin Steigerwald > > <mar...@lichtvoll.de> wrote: > > You probably put your stick into a cave with ancient sleeping > > dragons > > > > Added in linux-m68k mailing list, as

Re: moving affs + RDB partition support to staging? (was: Re: Moving unmaintained filesystems to staging)

2018-04-27 Thread Martin Steigerwald
Geert Uytterhoeven - 26.04.18, 13:08: > On Thu, Apr 26, 2018 at 12:28 PM, Martin Steigerwald > > wrote: > > You probably put your stick into a cave with ancient sleeping > > dragons > > > > Added in linux-m68k mailing list, as they likely have an opini

Re: Moving unmaintained filesystems to staging

2018-04-26 Thread Martin Steigerwald
Pavel Machek - 26.04.18, 08:11: > On Wed 2018-04-25 08:46:02, Matthew Wilcox wrote: > > Recently ncpfs got moved to staging. Also recently, we had some > > fuzzer developers report bugs in hfs, which they deem a security > > hole because Ubuntu attempts to automount an inserted USB device as > >

Re: Moving unmaintained filesystems to staging

2018-04-26 Thread Martin Steigerwald
Pavel Machek - 26.04.18, 08:11: > On Wed 2018-04-25 08:46:02, Matthew Wilcox wrote: > > Recently ncpfs got moved to staging. Also recently, we had some > > fuzzer developers report bugs in hfs, which they deem a security > > hole because Ubuntu attempts to automount an inserted USB device as > >

moving affs + RDB partition support to staging? (was: Re: Moving unmaintained filesystems to staging)

2018-04-26 Thread Martin Steigerwald
itete Nachricht -- Betreff: Re: Partitions: Amiga RDB partition on 2 TB disk way too big, while OK in AmigaOS 4.1 Datum: Montag, 18. Juni 2012, 03:28:48 CEST Von: jdow <j...@earthlink.net> An: Martin Steigerwald <mar...@lichtvoll.de> Kopie: Geert Uytterhoeven

moving affs + RDB partition support to staging? (was: Re: Moving unmaintained filesystems to staging)

2018-04-26 Thread Martin Steigerwald
itete Nachricht -- Betreff: Re: Partitions: Amiga RDB partition on 2 TB disk way too big, while OK in AmigaOS 4.1 Datum: Montag, 18. Juni 2012, 03:28:48 CEST Von: jdow An: Martin Steigerwald Kopie: Geert Uytterhoeven , linux- ker...@vger.kernel.org, Jens Axboe , linux- m...@vger.kerne

Re: [PATCH] blk-mq: start request gstate with gen 1

2018-04-23 Thread Martin Steigerwald
Hi Jianchao. jianchao.wang - 17.04.18, 16:34: > On 04/17/2018 08:10 PM, Martin Steigerwald wrote: > > For testing it I add it to 4.16.2 with the patches I have already? > > You could try to only apply this patch to have a test. :) I tested 4.16.3 with just your patch (+ the

Re: [PATCH] blk-mq: start request gstate with gen 1

2018-04-23 Thread Martin Steigerwald
Hi Jianchao. jianchao.wang - 17.04.18, 16:34: > On 04/17/2018 08:10 PM, Martin Steigerwald wrote: > > For testing it I add it to 4.16.2 with the patches I have already? > > You could try to only apply this patch to have a test. :) I tested 4.16.3 with just your patch (+ the

Re: [PATCH] blk-mq: start request gstate with gen 1

2018-04-23 Thread Martin Steigerwald
Hi Jianchao. jianchao.wang - 17.04.18, 16:34: > On 04/17/2018 08:10 PM, Martin Steigerwald wrote: > > For testing it I add it to 4.16.2 with the patches I have already? > > You could try to only apply this patch to have a test. Compiling now to have a test. Thanks, -- Martin

Re: [PATCH] blk-mq: start request gstate with gen 1

2018-04-23 Thread Martin Steigerwald
Hi Jianchao. jianchao.wang - 17.04.18, 16:34: > On 04/17/2018 08:10 PM, Martin Steigerwald wrote: > > For testing it I add it to 4.16.2 with the patches I have already? > > You could try to only apply this patch to have a test. Compiling now to have a test. Thanks, -- Martin

Re: [PATCH] blk-mq: start request gstate with gen 1

2018-04-17 Thread Martin Steigerwald
m> > Cc: Tejun Heo <t...@kernel.org> > Cc: Ming Lei <ming@redhat.com> > Cc: Martin Steigerwald <mar...@lichtvoll.de> > Cc: sta...@vger.kernel.org > Signed-off-by: Jianchao Wang <jianchao.w.w...@oracle.com> > --- > block/blk-core.c | 4 > bloc

Re: [PATCH] blk-mq: start request gstate with gen 1

2018-04-17 Thread Martin Steigerwald
_2] blk-mq_fix race between complete and BLK_EH_RESET_TIMER.mbox' > For scsi, this will cause scsi_times_out to be invoked before the > scsi_cmnd is not initialized, scsi_cmnd->device is still NULL at > the moment, then we will get crash. > > Cc: Bart Van Assche > Cc: Tejun

Re: [PATCH] blk-mq: Directly schedule q->timeout_work when aborting a request

2018-04-10 Thread Martin Steigerwald
Martin Steigerwald - 10.04.18, 20:43: > Tejun Heo - 03.04.18, 00:04: > > Request abortion is performed by overriding deadline to now and > > scheduling timeout handling immediately. For the latter part, the > > code was using mod_timer(timeout, 0) which can't guarantee th

Re: [PATCH] blk-mq: Directly schedule q->timeout_work when aborting a request

2018-04-10 Thread Martin Steigerwald
Martin Steigerwald - 10.04.18, 20:43: > Tejun Heo - 03.04.18, 00:04: > > Request abortion is performed by overriding deadline to now and > > scheduling timeout handling immediately. For the latter part, the > > code was using mod_timer(timeout, 0) which can't guarantee th

Re: [PATCH] blk-mq: Directly schedule q->timeout_work when aborting a request

2018-04-10 Thread Martin Steigerwald
Tejun Heo - 03.04.18, 00:04: > Request abortion is performed by overriding deadline to now and > scheduling timeout handling immediately. For the latter part, the > code was using mod_timer(timeout, 0) which can't guarantee that the > timer runs afterwards. Let's schedule the underlying work

Re: [PATCH] blk-mq: Directly schedule q->timeout_work when aborting a request

2018-04-10 Thread Martin Steigerwald
Tejun Heo - 03.04.18, 00:04: > Request abortion is performed by overriding deadline to now and > scheduling timeout handling immediately. For the latter part, the > code was using mod_timer(timeout, 0) which can't guarantee that the > timer runs afterwards. Let's schedule the underlying work

Re: [Possible REGRESSION, 4.16-rc4] Error updating SMART data during runtime and could not connect to lvmetad at some boot attempts

2018-04-10 Thread Martin Steigerwald
Hans de Goede - 19.03.18, 10:50: > > Martin (or someone else): Could you gibe a status update? I have this > > issue on my list or regressions, but it's hard to follow as two > > different issues seem to be discussed. Or is it just one issue? Did the > > patch/discussion that Bart pointed to help?

Re: [Possible REGRESSION, 4.16-rc4] Error updating SMART data during runtime and could not connect to lvmetad at some boot attempts

2018-04-10 Thread Martin Steigerwald
Hans de Goede - 19.03.18, 10:50: > > Martin (or someone else): Could you gibe a status update? I have this > > issue on my list or regressions, but it's hard to follow as two > > different issues seem to be discussed. Or is it just one issue? Did the > > patch/discussion that Bart pointed to help?

Re: [Possible REGRESSION, 4.16-rc4] Error updating SMART data during runtime and could not connect to lvmetad at some boot attempts

2018-03-19 Thread Martin Steigerwald
Hi Thorsten. Hans de Goede - 19.03.18, 10:50: > On 19-03-18 10:42, Thorsten Leemhuis wrote: > > Hi! On 11.03.2018 09:20, Martin Steigerwald wrote: > >> Since 4.16-rc4 (upgraded from 4.15.2 which worked) I have an issue > > > >> with SMART checks occassiona

Re: [Possible REGRESSION, 4.16-rc4] Error updating SMART data during runtime and could not connect to lvmetad at some boot attempts

2018-03-19 Thread Martin Steigerwald
Hi Thorsten. Hans de Goede - 19.03.18, 10:50: > On 19-03-18 10:42, Thorsten Leemhuis wrote: > > Hi! On 11.03.2018 09:20, Martin Steigerwald wrote: > >> Since 4.16-rc4 (upgraded from 4.15.2 which worked) I have an issue > > > >> with SMART checks occassiona

Re: [Possible REGRESSION, 4.16-rc4] Error updating SMART data during runtime and could not connect to lvmetad at some boot attempts

2018-03-18 Thread Martin Steigerwald
Hi Hans. Hans de Goede - 18.03.18, 22:34: > On 14-03-18 13:48, Martin Steigerwald wrote: > > Hans de Goede - 14.03.18, 12:05: > >> Hi, > >> > >> On 14-03-18 12:01, Martin Steigerwald wrote: > >>> Hans de Goede - 11.03.18, 15:37: > >&

Re: [Possible REGRESSION, 4.16-rc4] Error updating SMART data during runtime and could not connect to lvmetad at some boot attempts

2018-03-18 Thread Martin Steigerwald
Hi Hans. Hans de Goede - 18.03.18, 22:34: > On 14-03-18 13:48, Martin Steigerwald wrote: > > Hans de Goede - 14.03.18, 12:05: > >> Hi, > >> > >> On 14-03-18 12:01, Martin Steigerwald wrote: > >>> Hans de Goede - 11.03.18, 15:37: > >&

Re: [Possible REGRESSION, 4.16-rc4] Error updating SMART data during runtime and could not connect to lvmetad at some boot attempts

2018-03-15 Thread Martin Steigerwald
Martin Steigerwald - 14.03.18, 12:01: > Hans de Goede - 11.03.18, 15:37: > > Hi Martin, > > > > On 11-03-18 09:20, Martin Steigerwald wrote: > > > Hello. > > > > > > Since 4.16-rc4 (upgraded from 4.15.2 which worked) I have an issue &g

Re: [Possible REGRESSION, 4.16-rc4] Error updating SMART data during runtime and could not connect to lvmetad at some boot attempts

2018-03-15 Thread Martin Steigerwald
Martin Steigerwald - 14.03.18, 12:01: > Hans de Goede - 11.03.18, 15:37: > > Hi Martin, > > > > On 11-03-18 09:20, Martin Steigerwald wrote: > > > Hello. > > > > > > Since 4.16-rc4 (upgraded from 4.15.2 which worked) I have an issue &g

  1   2   3   4   5   >