From: Linus Torvalds <torvalds@linux-foundation.org>
To: Markus Trippelsdorf <markus@trippelsdorf.de>
Cc: Theodore Tso <tytso@MIT.EDU>,
linux-kernel@vger.kernel.org, linux-ext4@vger.kernel.org
Subject: Re: ext4 2.6.35-rc2 regression (ext4: Make sure the MOVE_EXT ioctl can't overwrite append-only files)
Date: Sun, 6 Jun 2010 20:38:17 -0700 (PDT) [thread overview]
Message-ID: <alpine.LFD.2.00.1006062036240.3515@i5.linux-foundation.org> (raw)
In-Reply-To: <20100606172339.GA1778@arch.tripp.de>
On Sun, 6 Jun 2010, Markus Trippelsdorf wrote:
> On Sun, Jun 06, 2010 at 01:59:47PM +0200, Markus Trippelsdorf wrote:
> > On Sun, Jun 06, 2010 at 07:45:48AM -0400, Theodore Tso wrote:
> > >
> > > On Jun 6, 2010, at 4:16 AM, Markus Trippelsdorf wrote:
> > >
> > > > Commit 1f5a81e41f8b1a782c68d3843e9ec1bfaadf7d72
> > > > "ext4: Make sure the MOVE_EXT ioctl can't overwrite append-only files"
> > > > causes the following kernel BUG on my machine (x86_64):
> > > >
> > > > BUG: Bad page map in process mpd pte:720072000000000 pmd:11d2f7067
This is the same "VGA pattern": 07200720 is two spaces.
It causes lots of trouble, too bad it made it into -rc2. It has nothing to
do with ext4.
And I bet it gets fix by the same vt.c patch that apparently fixed some
KMS issues. Look on lkml for a "poison overwritten" subject line.
Or just revert 962400e8fd29981a7b166e463dd143b6ac6a3e76.
Linus
next prev parent reply other threads:[~2010-06-07 3:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-06 8:16 Markus Trippelsdorf
2010-06-06 8:57 ` Markus Trippelsdorf
2010-06-06 11:45 ` Theodore Tso
2010-06-06 11:59 ` Markus Trippelsdorf
2010-06-06 17:23 ` Markus Trippelsdorf
2010-06-07 3:38 ` Linus Torvalds [this message]
2010-06-07 6:32 ` 2.6.35-rc2 regression Markus Trippelsdorf
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=alpine.LFD.2.00.1006062036240.3515@i5.linux-foundation.org \
--to=torvalds@linux-foundation.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=markus@trippelsdorf.de \
--cc=tytso@MIT.EDU \
/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
all inboxes | Powered by JetHome®