From: Al Viro <viro@ZenIV.linux.org.uk>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Nick Piggin <npiggin@gmail.com>, Jana Saout <jana@saout.de>,
Joel Becker <jlbec@evilplan.org>,
linux-kernel@vger.kernel.org
Subject: Re: Oops with DCACHE_WORD_ACCESS and ocfs2, autofs4
Date: Thu, 3 May 2012 07:47:22 +0100 [thread overview]
Message-ID: <20120503064722.GN6871@ZenIV.linux.org.uk> (raw)
In-Reply-To: <CA+55aFwPgWqCPA=ao6XmZy56PaJZ4WC+hOZ_CHGWpo_zO425VA@mail.gmail.com>
On Wed, May 02, 2012 at 10:57:00PM -0700, Linus Torvalds wrote:
> There are multiple ways to fix this, including just marking that
> unaligned word access as being able to take an exception, but I had
> hoped to avoid having to do that. There are alternatives, like always
> padding allocations up by 7 bytes, but those are nasty too. So I'd
> like to understand what triggers this for Jana, it's possible we can
> just work around that particular issue.
What I'd really like to know is whether we can hit the same kind of "steps
off the end of page" crap on pagecache based symlinks with very long bodies.
The upper limit is 4K, which allows that sucker to reach the end of page
on most of the architectures. And that can be done on just about any fs
supporting symlinks at all - create a symlink with the long body (up to the
limit), something like (("./"x2047)."a").
next prev parent reply other threads:[~2012-05-03 6:47 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-30 12:27 Oops with DCACHE_WORD_ACCESS and ocfs2, autofs4 Jana Saout
2012-05-01 11:00 ` Joel Becker
2012-05-01 12:28 ` Jana Saout
2012-05-03 5:02 ` Nick Piggin
2012-05-03 5:57 ` Linus Torvalds
2012-05-03 5:57 ` Linus Torvalds
2012-05-03 6:23 ` Nick Piggin
2012-05-03 6:26 ` Nick Piggin
2012-05-03 6:38 ` H. Peter Anvin
2012-05-03 6:40 ` H. Peter Anvin
2012-05-03 6:54 ` David Miller
2012-05-03 6:57 ` H. Peter Anvin
2012-05-03 7:02 ` David Miller
2012-05-03 6:47 ` Al Viro [this message]
2012-05-03 16:15 ` Linus Torvalds
2012-05-03 17:30 ` Al Viro
2012-05-03 17:30 ` Linus Torvalds
2012-05-03 18:13 ` H. Peter Anvin
2012-05-03 18:23 ` Linus Torvalds
2012-05-03 18:27 ` H. Peter Anvin
2012-05-03 18:28 ` H. Peter Anvin
2012-05-03 18:48 ` David Miller
2012-05-03 21:23 ` H. Peter Anvin
2012-05-03 19:06 ` Linus Torvalds
2012-05-03 20:30 ` Jana Saout
2012-05-03 21:01 ` Linus Torvalds
2012-05-03 21:03 ` Jana Saout
2012-05-03 21:20 ` Linus Torvalds
2012-05-03 21:47 ` Jana Saout
2012-05-04 11:21 ` Jana Saout
2012-05-03 8:01 ` Jana Saout
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=20120503064722.GN6871@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=jana@saout.de \
--cc=jlbec@evilplan.org \
--cc=linux-kernel@vger.kernel.org \
--cc=npiggin@gmail.com \
--cc=torvalds@linux-foundation.org \
/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