public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ed Tomlinson <edt@aei.ca>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: sedat.dilek@gmail.com, Greg KH <gregkh@suse.de>,
	LKML <linux-kernel@vger.kernel.org>,
	penberg@kernel.org, arthur@psw.ro, wylda@volny.cz
Subject: Re: Linux 2.6.35.2
Date: Sat, 14 Aug 2010 19:39:53 -0400	[thread overview]
Message-ID: <201008141939.54277.edt@aei.ca> (raw)
In-Reply-To: <AANLkTinP3Kh4Gjnkx2ycr34W6SVqLsBh7yMsGuoU7pAD@mail.gmail.com>

On Saturday 14 August 2010 17:56:58 Linus Torvalds wrote:
> On Sat, Aug 14, 2010 at 12:47 PM, Ed Tomlinson <edt@aei.ca> wrote:
> > On Saturday 14 August 2010 14:47:45 Linus Torvalds wrote:
> >>
> >> Just to verify: you have CONFIG_HIGHPTE enabled on a x86-32 kernel,
> >> right? I'd have expected this to not ever show up anywhere else, and
> >> I'm just verifying that there isn't anything else going on. I'm
> >> appending the commit message, the patch hasn't changed.
> >
> > No.  I have a x86-64 based kernel (amd64).
> 
> Hmm. On x86-64, pte_unmap() is a no-op. So moving it around should not
> matter one whit. We don't even have a debug mode to turn it into some
> kind of "check that we use it properly in an atomic region" which we
> _could_ do.
> 
> Can you send me the messages you saw without that patch? There's
> something odd going on here. I don't like the fact that the patch
> apparently makes a difference for you. It shouldn't.

Linus,

Not to worry - looks like the problems here were due to a bad inode.
I just did not hit it when restarting with the  patch added.  When I
rebuilt the kernel without the patch it hit the fs/inode problem during
boot.  A manual fsck seems to have fixed things.

Ed Tomlinson

  reply	other threads:[~2010-08-14 23:42 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-14 12:37 Linux 2.6.35.2 Sedat Dilek
2010-08-14 17:14 ` Linus Torvalds
2010-08-14 17:27   ` Sedat Dilek
2010-08-14 17:31     ` Linus Torvalds
2010-08-14 18:27       ` Ed Tomlinson
2010-08-14 18:47         ` Linus Torvalds
2010-08-14 19:01           ` wylda
2010-08-14 19:01           ` Sedat Dilek
2010-08-14 19:47           ` Ed Tomlinson
2010-08-14 21:56             ` Linus Torvalds
2010-08-14 23:39               ` Ed Tomlinson [this message]
2010-08-14 20:34           ` Sedat Dilek
  -- strict thread matches above, loose matches on Subject: below --
2010-08-13 21:23 Greg KH
2010-08-13 21:23 ` Greg KH
2010-08-14  6:53   ` Heinz Diehl
2010-08-14 13:40     ` Greg KH
2010-08-14 10:35 ` Arthur Titeica
2010-08-14 11:21   ` Pekka Enberg
2010-08-14 13:39     ` Greg KH
2010-08-14 14:08       ` Arthur Titeica
2010-08-14 15:10         ` Bjarke Istrup Pedersen
2010-08-14 16:56         ` Heiko Carstens

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=201008141939.54277.edt@aei.ca \
    --to=edt@aei.ca \
    --cc=arthur@psw.ro \
    --cc=gregkh@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=penberg@kernel.org \
    --cc=sedat.dilek@gmail.com \
    --cc=torvalds@linux-foundation.org \
    --cc=wylda@volny.cz \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox