[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20150526102239.GA466@swordfish>
Date: Tue, 26 May 2015 19:22:39 +0900
From: Sergey Senozhatsky <sergey.senozhatsky.work@...il.com>
To: Daniel Phillips <daniel@...nq.net>
Cc: Jan Kara <jack@...e.cz>, David Lang <david@...g.hm>,
Rik van Riel <riel@...hat.com>,
linux-fsdevel@...r.kernel.org, tux3@...3.org,
linux-kernel@...r.kernel.org,
OGAWA Hirofumi <hirofumi@...l.parknet.co.jp>
Subject: Re: [FYI] tux3: Core changes
On (05/26/15 01:08), Daniel Phillips wrote:
> On Tuesday, May 26, 2015 12:09:10 AM PDT, Jan Kara wrote:
> > E.g. video drivers (or infiniband or direct IO for that matter) which
> >have buffers in user memory (may be mmapped file), grab references to pages
> >and hand out PFNs of those pages to the hardware to store data in them...
> >If you fork a page after the driver has handed PFNs to the hardware, you've
> >just lost all the writes hardware will do.
>
> Hi Jan,
>
> The page forked because somebody wrote to it with write(2) or mmap write at
> the same time as a video driver (or infiniband or direct IO) was doing io to
> it. Isn't the application trying hard to lose data in that case? It would
> not need page fork to lose data that way.
>
Hello,
is it possible to page-fork-bomb the system by some 'malicious' app?
-ss
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists