All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Weinberger <richard@nod.at>
To: "Toralf Förster" <toralf.foerster@gmx.de>
Cc: UML devel <user-mode-linux-devel@lists.sourceforge.net>
Subject: Re: [uml-devel] trinity commit 23dc478aba breaks syscall "mremap" at a 32 bit user mode linux
Date: Sat, 26 Jul 2014 22:07:36 +0200	[thread overview]
Message-ID: <53D40A88.7030902@nod.at> (raw)
In-Reply-To: <53D40919.8040803@gmx.de>

Am 26.07.2014 22:01, schrieb Toralf Förster:
> On 05/01/2014 02:33 PM, Richard Weinberger wrote:
>> BTW: If you hit "BUG: failure at mm/filemap.c:202/__delete_from_page_cache()!",
>> this is a known issue https://lkml.org/lkml/2014/4/15/577
> 
> Since I do exclude the "madvise" syscall from fuzz testing I do no longer run into this issue
> (at least with recent git tree).
> 
> But there's still this unsolved issue in the kernel, or ?

AFAIK the resolution is near.
Please see thread "PROBLEM: repeated remap_file_pages on tmpfs triggers bug on process exit".
If you still face the issue it may UML specific.

Thanks,
//richard

------------------------------------------------------------------------------
Want fast and easy access to all the code in your enterprise? Index and
search up to 200,000 lines of code with a free copy of Black Duck
Code Sight - the same software that powers the world's largest code
search on Ohloh, the Black Duck Open Hub! Try it now.
http://p.sf.net/sfu/bds
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel

  reply	other threads:[~2014-07-26 20:07 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-30 18:19 [uml-devel] trinity commit 23dc478aba breaks syscall "mremap" at a 32 bit user mode linux Toralf Förster
2014-04-30 18:19 ` Toralf Förster
2014-05-01  9:22 ` [uml-devel] " Richard Weinberger
2014-05-01  9:22   ` Richard Weinberger
2014-05-01 10:29   ` Toralf Förster
2014-05-01 10:29     ` Toralf Förster
2014-05-01 12:33     ` Richard Weinberger
2014-05-01 12:33       ` Richard Weinberger
2014-05-01 15:15       ` Toralf Förster
2014-05-01 15:15         ` Toralf Förster
2014-05-01 20:57         ` Richard Weinberger
2014-05-01 20:57           ` Richard Weinberger
2014-05-01 21:34           ` Toralf Förster
2014-05-01 21:34             ` Toralf Förster
2014-05-02  7:21             ` Richard Weinberger
2014-05-02  7:21               ` Richard Weinberger
2014-05-02  7:46             ` Richard Weinberger
2014-05-02  7:46               ` Richard Weinberger
2014-05-02 14:07               ` Toralf Förster
2014-05-02 14:07                 ` Toralf Förster
2014-05-02 14:14                 ` Richard Weinberger
2014-05-02 14:14                   ` Richard Weinberger
2014-07-12 17:16                   ` Toralf Förster
2014-07-12 18:04                     ` Richard Weinberger
2014-05-02  6:43           ` stian
2014-05-02  9:48             ` Richard Weinberger
2014-07-26 20:01       ` Toralf Förster
2014-07-26 20:07         ` Richard Weinberger [this message]
2014-07-26 21:21           ` Toralf Förster

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=53D40A88.7030902@nod.at \
    --to=richard@nod.at \
    --cc=toralf.foerster@gmx.de \
    --cc=user-mode-linux-devel@lists.sourceforge.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.