All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sasha Levin <sasha.levin@oracle.com>
To: Andrey Ryabinin <a.ryabinin@samsung.com>,
	"Kirill A. Shutemov" <kirill@shutemov.name>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Andi Kleen <ak@linux.intel.com>,
	Matthew Wilcox <matthew.r.wilcox@intel.com>,
	Dave Hansen <dave.hansen@linux.intel.com>,
	Alexander Viro <viro@zeniv.linux.org.uk>,
	Dave Chinner <david@fromorbit.com>, Ning Qu <quning@gmail.com>,
	linux-mm@kvack.org, linux-fsdevel@vger.kernel.org,
	linux-kernel@vger.kernel.org, Dave Jones <davej@redhat.com>,
	stable@vger.kernel.org,
	"Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>,
	Mel Gorman <mgorman@suse.de>, Rik van Riel <riel@redhat.com>,
	Konstantin Khlebnikov <koct9i@gmail.com>,
	Hugh Dickins <hughd@google.com>
Subject: Re: [PATCH] mm: don't allow fault_around_bytes to be 0
Date: Mon, 28 Jul 2014 08:32:19 -0400	[thread overview]
Message-ID: <53D642D3.8020407@oracle.com> (raw)
In-Reply-To: <53D62599.6000605@samsung.com>

On 07/28/2014 06:27 AM, Andrey Ryabinin wrote:
>> Although, I'm not convinced that it caused the issue. Sasha, did you touch the
>> > debugfs handle?
>> > 
> I suppose trinity could change it, no? I've got the very same spew after setting fault_around_bytes to 0.

Not on purpose, but as Andrey said - it's very possible that trinity did.


Thanks,
Sasha

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

WARNING: multiple messages have this Message-ID (diff)
From: Sasha Levin <sasha.levin@oracle.com>
To: Andrey Ryabinin <a.ryabinin@samsung.com>,
	"Kirill A. Shutemov" <kirill@shutemov.name>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Andi Kleen <ak@linux.intel.com>,
	Matthew Wilcox <matthew.r.wilcox@intel.com>,
	Dave Hansen <dave.hansen@linux.intel.com>,
	Alexander Viro <viro@zeniv.linux.org.uk>,
	Dave Chinner <david@fromorbit.com>, Ning Qu <quning@gmail.com>,
	linux-mm@kvack.org, linux-fsdevel@vger.kernel.org,
	linux-kernel@vger.kernel.org, Dave Jones <davej@redhat.com>,
	stable@vger.kernel.org,
	"Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>,
	Mel Gorman <mgorman@suse.de>, Rik van Riel <riel@redhat.com>,
	Konstantin Khlebnikov <koct9i@gmail.com>,
	Hugh Dickins <hughd@google.com>
Subject: Re: [PATCH] mm: don't allow fault_around_bytes to be 0
Date: Mon, 28 Jul 2014 08:32:19 -0400	[thread overview]
Message-ID: <53D642D3.8020407@oracle.com> (raw)
In-Reply-To: <53D62599.6000605@samsung.com>

On 07/28/2014 06:27 AM, Andrey Ryabinin wrote:
>> Although, I'm not convinced that it caused the issue. Sasha, did you touch the
>> > debugfs handle?
>> > 
> I suppose trinity could change it, no? I've got the very same spew after setting fault_around_bytes to 0.

Not on purpose, but as Andrey said - it's very possible that trinity did.


Thanks,
Sasha

  parent reply	other threads:[~2014-07-28 12:32 UTC|newest]

Thread overview: 73+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-27 19:53 [PATCHv3 0/2] mm: map few pages around fault address if they are in page cache Kirill A. Shutemov
2014-02-27 19:53 ` Kirill A. Shutemov
2014-02-27 19:53 ` [PATCHv3 1/2] mm: introduce vm_ops->map_pages() Kirill A. Shutemov
2014-02-27 19:53   ` Kirill A. Shutemov
2014-02-27 21:59   ` Dave Hansen
2014-02-27 21:59     ` Dave Hansen
2014-02-27 22:06     ` Linus Torvalds
2014-02-27 22:06       ` Linus Torvalds
2014-02-27 22:34       ` Dave Hansen
2014-02-27 22:34         ` Dave Hansen
2014-02-28  0:18         ` Kirill A. Shutemov
2014-02-28  0:18           ` Kirill A. Shutemov
2014-02-28 11:50         ` Benjamin Herrenschmidt
2014-02-28 11:50           ` Benjamin Herrenschmidt
2014-02-27 22:08     ` Andrew Morton
2014-02-27 22:08       ` Andrew Morton
2014-03-03 23:16   ` Andrew Morton
2014-03-04  1:26     ` Kirill A. Shutemov
2014-03-04  1:26       ` Kirill A. Shutemov
2014-03-04  1:26       ` Kirill A. Shutemov
2014-03-05  0:04     ` Rusty Russell
2014-03-05  0:04       ` Rusty Russell
2014-03-05 20:02       ` Andrew Morton
2014-03-05 20:02         ` Andrew Morton
2014-07-24  3:33   ` Sasha Levin
2014-07-24  3:33     ` Sasha Levin
2014-07-24  6:53     ` Andrey Ryabinin
2014-07-24  6:53       ` Andrey Ryabinin
2014-07-24 12:48       ` Sasha Levin
2014-07-24 12:48         ` Sasha Levin
2014-07-24 13:05     ` Sasha Levin
2014-07-24 13:05       ` Sasha Levin
2014-07-24 13:30       ` Konstantin Khlebnikov
2014-07-24 13:30         ` Konstantin Khlebnikov
2014-07-28  7:43     ` [PATCH] mm: don't allow fault_around_bytes to be 0 Andrey Ryabinin
2014-07-28  7:43       ` Andrey Ryabinin
2014-07-28  7:47       ` Andrey Ryabinin
2014-07-28  7:47         ` Andrey Ryabinin
2014-07-28  9:36       ` Kirill A. Shutemov
2014-07-28  9:36         ` Kirill A. Shutemov
2014-07-28  9:36         ` Kirill A. Shutemov
2014-07-28 10:27         ` Andrey Ryabinin
2014-07-28 10:27           ` Andrey Ryabinin
2014-07-28 10:27           ` Andrey Ryabinin
2014-07-28 10:27           ` Andrey Ryabinin
2014-07-28 10:52           ` Kirill A. Shutemov
2014-07-28 10:52             ` Kirill A. Shutemov
2014-07-28 12:32           ` Sasha Levin [this message]
2014-07-28 12:32             ` Sasha Levin
2014-07-28 22:43           ` David Rientjes
2014-07-28 22:43             ` David Rientjes
2014-07-28 15:26         ` Dave Hansen
2014-07-28 15:26           ` Dave Hansen
2014-02-27 19:53 ` [PATCHv3 2/2] mm: implement ->map_pages for page cache Kirill A. Shutemov
2014-02-27 19:53   ` Kirill A. Shutemov
2014-02-27 21:47   ` Andrew Morton
2014-02-27 21:47     ` Andrew Morton
2014-02-28  0:31     ` Kirill A. Shutemov
2014-02-28  0:31       ` Kirill A. Shutemov
2014-04-02 18:03   ` Konstantin Khlebnikov
2014-04-02 18:03     ` Konstantin Khlebnikov
2014-04-02 19:07     ` Kirill A. Shutemov
2014-04-02 19:07       ` Kirill A. Shutemov
2014-02-27 21:28 ` [PATCHv3 0/2] mm: map few pages around fault address if they are in " Linus Torvalds
2014-02-27 21:28   ` Linus Torvalds
2014-02-28  0:10   ` Kirill A. Shutemov
2014-02-28  0:10     ` Kirill A. Shutemov
2014-02-28  3:52     ` Wilcox, Matthew R
2014-02-28  3:52       ` Wilcox, Matthew R
2014-02-28 23:08     ` Linus Torvalds
2014-02-28 23:08       ` Linus Torvalds
2014-03-12 14:22   ` Kirill A. Shutemov
2014-03-12 14:22     ` Kirill A. Shutemov

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=53D642D3.8020407@oracle.com \
    --to=sasha.levin@oracle.com \
    --cc=a.ryabinin@samsung.com \
    --cc=ak@linux.intel.com \
    --cc=akpm@linux-foundation.org \
    --cc=dave.hansen@linux.intel.com \
    --cc=davej@redhat.com \
    --cc=david@fromorbit.com \
    --cc=hughd@google.com \
    --cc=kirill.shutemov@linux.intel.com \
    --cc=kirill@shutemov.name \
    --cc=koct9i@gmail.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=matthew.r.wilcox@intel.com \
    --cc=mgorman@suse.de \
    --cc=quning@gmail.com \
    --cc=riel@redhat.com \
    --cc=stable@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    --cc=viro@zeniv.linux.org.uk \
    /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.