All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tejun Heo <htejun@gmail.com>
To: richard -rw- weinberger <richard.weinberger@gmail.com>
Cc: Chris Frey <cdfrey@foursquare.net>,
	Jens Axboe <jaxboe@fusionio.com>,
	Richard Weinberger <richard@nod.at>,
	Andrew Morton <akpm@linux-foundation.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"jdike@addtoit.com" <jdike@addtoit.com>,
	"user-mode-linux-devel@lists.sourceforge.net"
	<user-mode-linux-devel@lists.sourceforge.net>,
	"user-mode-linux-user@lists.sourceforge.net"
	<user-mode-linux-user@lists.sourceforge.net>,
	"janjaap@bos.nl" <janjaap@bos.nl>,
	"geert@linux-m68k.org" <geert@linux-m68k.org>,
	"martin.petersen@oracle.com" <martin.petersen@oracle.com>,
	"adobriyan@gmail.com" <adobriyan@gmail.com>,
	"syzop@vulnscan.org" <syzop@vulnscan.org>
Subject: Re: [PATCH 1/1] um: ubd: Fix data corruption
Date: Thu, 14 Oct 2010 20:03:40 +0200	[thread overview]
Message-ID: <4CB745FC.5090504@gmail.com> (raw)
In-Reply-To: <AANLkTi=ni-zEfCMXLR8BJyPQcwzEKAUKYs4uH7ur12Fk@mail.gmail.com>

Hello,

On 10/14/2010 04:20 PM, richard -rw- weinberger wrote:
> It does not work for me.
> But the error is a different one. :-)
> Without your patch I've never got this kernel trace.
> 
> [   59.850000] kworker/0:1: page allocation failure. order:0, mode:0x20

Hmm... you're seeing out of memory condition.  If the code screws up
filesystem access, I suppose it could make that happen too but can you
please check the configuration just in case (especially the memory
size)?  Also, if you can reliably reproduce the filesystem corruption
w/o the patch, can you please tell me how to do it?

Thanks.

-- 
tejun


  reply	other threads:[~2010-10-14 18:03 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-28 21:47 [PATCH 1/1] um: ubd: Fix data corruption Richard Weinberger
2010-09-28 22:00 ` Andrew Morton
2010-09-28 22:00   ` Andrew Morton
2010-09-28 22:13   ` Richard Weinberger
2010-09-28 22:52     ` Chris Frey
2010-09-28 23:10       ` Jens Axboe
2010-09-29  0:48         ` Janjaap Bos
2010-09-29  1:29         ` Chris Frey
2010-09-29  5:21           ` Jens Axboe
2010-09-29  6:34             ` Chris Frey
2010-10-04 16:37               ` Tejun Heo
2010-10-04 19:51                 ` Chris Frey
2010-10-05  8:23                   ` Tejun Heo
2010-10-05 20:31                     ` Chris Frey
2010-10-07  7:58                       ` Jens Axboe
2010-10-07 20:23                         ` Chris Frey
2010-10-14 13:14                           ` Tejun Heo
2010-10-14 14:20                             ` richard -rw- weinberger
2010-10-14 18:03                               ` Tejun Heo [this message]
2010-10-14 21:24                                 ` Richard Weinberger
2010-10-15  4:47                             ` Chris Frey
2010-10-02 17:27             ` richard -rw- weinberger
2010-09-29  3:30     ` Chris Frey

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=4CB745FC.5090504@gmail.com \
    --to=htejun@gmail.com \
    --cc=adobriyan@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=cdfrey@foursquare.net \
    --cc=geert@linux-m68k.org \
    --cc=janjaap@bos.nl \
    --cc=jaxboe@fusionio.com \
    --cc=jdike@addtoit.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=martin.petersen@oracle.com \
    --cc=richard.weinberger@gmail.com \
    --cc=richard@nod.at \
    --cc=syzop@vulnscan.org \
    --cc=user-mode-linux-devel@lists.sourceforge.net \
    --cc=user-mode-linux-user@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.