On Wed, May 15, 2019 at 08:20:35AM -0700, Matthew Wilcox wrote:
> On Wed, May 15, 2019 at 05:04:06PM +0200, Greg Kroah-Hartman wrote:
> > > Greg, can you consider 6daef95b8c914866a46247232a048447fff97279 for
> > > backporting to stable? Nobody realised it was a bugfix at the time it
> > > went
W dniu 15.05.2019 o 17:18, Matthew Wilcox pisze:
> On Wed, May 15, 2019 at 08:02:17AM -0700, Eric Dumazet wrote:
>> On Wed, May 15, 2019 at 7:43 AM Matthew Wilcox wrote:
>>> You're seeing a race between page_address(page) being called twice.
>>> Between those two calls, something has caused the
On Wed, May 15, 2019 at 08:20:35AM -0700, Matthew Wilcox wrote:
> On Wed, May 15, 2019 at 05:04:06PM +0200, Greg Kroah-Hartman wrote:
> > > Greg, can you consider 6daef95b8c914866a46247232a048447fff97279 for
> > > backporting to stable? Nobody realised it was a bugfix at the time it
> > > went
On Wed, May 15, 2019 at 05:04:06PM +0200, Greg Kroah-Hartman wrote:
> > Greg, can you consider 6daef95b8c914866a46247232a048447fff97279 for
> > backporting to stable? Nobody realised it was a bugfix at the time it
> > went in. I suspect there aren't too many of us running HIGHMEM kernels
> > any
On Wed, May 15, 2019 at 08:02:17AM -0700, Eric Dumazet wrote:
> On Wed, May 15, 2019 at 7:43 AM Matthew Wilcox wrote:
> > You're seeing a race between page_address(page) being called twice.
> > Between those two calls, something has caused the page to be removed from
> > the page_address_map()
On Wed, May 15, 2019 at 07:43:52AM -0700, Matthew Wilcox wrote:
> > > W dniu 25.04.2019 o 11:25, Lech Perczak pisze:
> > >> Some time ago, after upgrading the Kernel on our i.MX6Q-based boards to
> > >> mainline 4.18, and now to LTS 4.19 line, during stress tests we started
> > >> noticing
On Wed, May 15, 2019 at 7:43 AM Matthew Wilcox wrote:
>
> > > W dniu 25.04.2019 o 11:25, Lech Perczak pisze:
> > >> Some time ago, after upgrading the Kernel on our i.MX6Q-based boards to
> > >> mainline 4.18, and now to LTS 4.19 line, during stress tests we started
> > >> noticing strange
> > W dniu 25.04.2019 o 11:25, Lech Perczak pisze:
> >> Some time ago, after upgrading the Kernel on our i.MX6Q-based boards to
> >> mainline 4.18, and now to LTS 4.19 line, during stress tests we started
> >> noticing strange warnings coming from 'read' syscall, when
> >> page_copy_sane()
Hi,
W dniu 26.04.2019 o 10:42, Lech Perczak pisze:
> Cc linux...@kvack.org
>
> W dniu 25.04.2019 o 11:25, Lech Perczak pisze:
>> Hello,
>>
>> Some time ago, after upgrading the Kernel on our i.MX6Q-based boards to
>> mainline 4.18, and now to LTS 4.19 line, during stress tests we started
>>
Cc linux...@kvack.org
W dniu 25.04.2019 o 11:25, Lech Perczak pisze:
> Hello,
>
> Some time ago, after upgrading the Kernel on our i.MX6Q-based boards to
> mainline 4.18, and now to LTS 4.19 line, during stress tests we started
> noticing strange warnings coming from 'read' syscall, when
Hello,
Some time ago, after upgrading the Kernel on our i.MX6Q-based boards to
mainline 4.18, and now to LTS 4.19 line, during stress tests we started
noticing strange warnings coming from 'read' syscall, when page_copy_sane()
check failed. Typical reproducibility is up to ~4 events per 24h.
11 matches
Mail list logo