Re: DOS by unprivileged user

On Mon, Apr 30, 2018 at 12:00 PM, Ferry Toth wrote: > Op woensdag 25 april 2018 16:54:59 CEST schreef Alan Cox: >> > > I think memory allocation and io waits can't be decoupled from >> > > scheduling as they are now. >> > >> > The scheduler is not decoupled from either, it is

Re: DOS by unprivileged user

On Mon, Apr 30, 2018 at 12:00 PM, Ferry Toth wrote: > Op woensdag 25 april 2018 16:54:59 CEST schreef Alan Cox: >> > > I think memory allocation and io waits can't be decoupled from >> > > scheduling as they are now. >> > >> > The scheduler is not decoupled from either, it is intimately involved

Re: DOS by unprivileged user

Op woensdag 25 april 2018 16:54:59 CEST schreef Alan Cox: > > > I think memory allocation and io waits can't be decoupled from > > > scheduling as they are now. > > > > The scheduler is not decoupled from either, it is intimately involved > > in both. However, none of the decision making

Re: DOS by unprivileged user

Op woensdag 25 april 2018 16:54:59 CEST schreef Alan Cox: > > > I think memory allocation and io waits can't be decoupled from > > > scheduling as they are now. > > > > The scheduler is not decoupled from either, it is intimately involved > > in both. However, none of the decision making

Re: DOS by unprivileged user

On Wed, 2018-04-25 at 15:54 +0100, Alan Cox wrote: > > Classical Unix systems never had this problem because they respond to > thrashing by ensuring that all processes consumed CPU and made some > progress. Linux handles it by thrashing itself to dealth while BSD always > handled it by moving

Re: DOS by unprivileged user

On Wed, 2018-04-25 at 15:54 +0100, Alan Cox wrote: > > Classical Unix systems never had this problem because they respond to > thrashing by ensuring that all processes consumed CPU and made some > progress. Linux handles it by thrashing itself to dealth while BSD always > handled it by moving

Re: DOS by unprivileged user

On Wed, 2018-04-25 at 15:54 +0100, Alan Cox wrote: > > > I think memory allocation and io waits can't be decoupled from > > > scheduling as they are now. > > > > The scheduler is not decoupled from either, it is intimately involved > > in both. However, none of the decision making smarts for

Re: DOS by unprivileged user

On Wed, 2018-04-25 at 15:54 +0100, Alan Cox wrote: > > > I think memory allocation and io waits can't be decoupled from > > > scheduling as they are now. > > > > The scheduler is not decoupled from either, it is intimately involved > > in both. However, none of the decision making smarts for

Re: DOS by unprivileged user

> > I think memory allocation and io waits can't be decoupled from > > scheduling as they are now. > > The scheduler is not decoupled from either, it is intimately involved > in both. However, none of the decision making smarts for either reside > in the scheduler, nor should they. It belongs

Re: DOS by unprivileged user

> > I think memory allocation and io waits can't be decoupled from > > scheduling as they are now. > > The scheduler is not decoupled from either, it is intimately involved > in both. However, none of the decision making smarts for either reside > in the scheduler, nor should they. It belongs

Re: DOS by unprivileged user

On Sun, 2018-04-22 at 21:37 +0200, Ferry Toth wrote: > > Yes your memory hog scenario thoroughly wrecks the user experience, but > > the process scheduler in not the source of that wreckage, it's a memory > > management issue. With no constraints in place, anybody can just keep > > on allocating

Re: DOS by unprivileged user

On Sun, 2018-04-22 at 21:37 +0200, Ferry Toth wrote: > > Yes your memory hog scenario thoroughly wrecks the user experience, but > > the process scheduler in not the source of that wreckage, it's a memory > > management issue. With no constraints in place, anybody can just keep > > on allocating

Re: DOS by unprivileged user

On Sun 2018-04-22 18:27:38, Michal Hocko wrote: > On Sun 22-04-18 10:43:00, vcap...@pengaru.com wrote: > > On Sun, Apr 22, 2018 at 12:16:54PM +0200, Pavel Machek wrote: > > > On Thu 2018-04-19 21:13:35, Ferry Toth wrote: > > > > It appears any ordinary user can easily create a DOS on linux. > > >

Re: DOS by unprivileged user

On Sun 2018-04-22 18:27:38, Michal Hocko wrote: > On Sun 22-04-18 10:43:00, vcap...@pengaru.com wrote: > > On Sun, Apr 22, 2018 at 12:16:54PM +0200, Pavel Machek wrote: > > > On Thu 2018-04-19 21:13:35, Ferry Toth wrote: > > > > It appears any ordinary user can easily create a DOS on linux. > > >

Re: DOS by unprivileged user

On Sun 22-04-18 10:43:00, vcap...@pengaru.com wrote: > On Sun, Apr 22, 2018 at 12:16:54PM +0200, Pavel Machek wrote: > > On Thu 2018-04-19 21:13:35, Ferry Toth wrote: > > > It appears any ordinary user can easily create a DOS on linux. > > > > > > One sure way to reproduce this is to open gitk on

Re: DOS by unprivileged user

On Sun 22-04-18 10:43:00, vcap...@pengaru.com wrote: > On Sun, Apr 22, 2018 at 12:16:54PM +0200, Pavel Machek wrote: > > On Thu 2018-04-19 21:13:35, Ferry Toth wrote: > > > It appears any ordinary user can easily create a DOS on linux. > > > > > > One sure way to reproduce this is to open gitk on

Re: DOS by unprivileged user

On Sun, Apr 22, 2018 at 12:16:54PM +0200, Pavel Machek wrote: > On Thu 2018-04-19 21:13:35, Ferry Toth wrote: > > It appears any ordinary user can easily create a DOS on linux. > > > > One sure way to reproduce this is to open gitk on the linux kernel repo > > (SIC) on a machine with 8GB RAM 16

Re: DOS by unprivileged user

On Sun, Apr 22, 2018 at 12:16:54PM +0200, Pavel Machek wrote: > On Thu 2018-04-19 21:13:35, Ferry Toth wrote: > > It appears any ordinary user can easily create a DOS on linux. > > > > One sure way to reproduce this is to open gitk on the linux kernel repo > > (SIC) on a machine with 8GB RAM 16

Re: DOS by unprivileged user

On Thu 2018-04-19 21:13:35, Ferry Toth wrote: > It appears any ordinary user can easily create a DOS on linux. > > One sure way to reproduce this is to open gitk on the linux kernel repo > (SIC) on a machine with 8GB RAM 16 GB swap on a HDD with btrfs and quad core > + hyperthreading. But I

Re: DOS by unprivileged user

On Thu 2018-04-19 21:13:35, Ferry Toth wrote: > It appears any ordinary user can easily create a DOS on linux. > > One sure way to reproduce this is to open gitk on the linux kernel repo > (SIC) on a machine with 8GB RAM 16 GB swap on a HDD with btrfs and quad core > + hyperthreading. But I

Re: DOS by unprivileged user

On Fri, 2018-04-20 at 10:39 +0200, Ferry Toth wrote: > > Nevertheless I feel one process should not be allowed to harm other > processes by denying them resources. Even if when btrfs makes it easy > abuse I think the scheduler should have throttled gitk. Memory management is not in it's job

Re: DOS by unprivileged user

On Fri, 2018-04-20 at 10:39 +0200, Ferry Toth wrote: > > Nevertheless I feel one process should not be allowed to harm other > processes by denying them resources. Even if when btrfs makes it easy > abuse I think the scheduler should have throttled gitk. Memory management is not in it's job

Re: DOS by unprivileged user

Op vrijdag 20 april 2018 06:46:58 CEST schreef Mike Galbraith: > On Thu, 2018-04-19 at 21:13 +0200, Ferry Toth wrote: > > It appears any ordinary user can easily create a DOS on linux. > > > > One sure way to reproduce this is to open gitk on the linux kernel repo > > (SIC) on a machine with 8GB

Re: DOS by unprivileged user

Op vrijdag 20 april 2018 06:46:58 CEST schreef Mike Galbraith: > On Thu, 2018-04-19 at 21:13 +0200, Ferry Toth wrote: > > It appears any ordinary user can easily create a DOS on linux. > > > > One sure way to reproduce this is to open gitk on the linux kernel repo > > (SIC) on a machine with 8GB

Re: DOS by unprivileged user

On Thu, 2018-04-19 at 21:13 +0200, Ferry Toth wrote: > It appears any ordinary user can easily create a DOS on linux. > > One sure way to reproduce this is to open gitk on the linux kernel repo > (SIC) on a machine with 8GB RAM 16 GB swap on a HDD with btrfs and quad core > + hyperthreading.

Re: DOS by unprivileged user

On Thu, 2018-04-19 at 21:13 +0200, Ferry Toth wrote: > It appears any ordinary user can easily create a DOS on linux. > > One sure way to reproduce this is to open gitk on the linux kernel repo > (SIC) on a machine with 8GB RAM 16 GB swap on a HDD with btrfs and quad core > + hyperthreading.

DOS by unprivileged user

It appears any ordinary user can easily create a DOS on linux. One sure way to reproduce this is to open gitk on the linux kernel repo (SIC) on a machine with 8GB RAM 16 GB swap on a HDD with btrfs and quad core + hyperthreading. But I will be easy enough to get the same effect with more RAM,

DOS by unprivileged user

It appears any ordinary user can easily create a DOS on linux. One sure way to reproduce this is to open gitk on the linux kernel repo (SIC) on a machine with 8GB RAM 16 GB swap on a HDD with btrfs and quad core + hyperthreading. But I will be easy enough to get the same effect with more RAM,