linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Anton Altaparmakov <aia21@cam.ac.uk>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Al Viro <viro@parcelfarce.linux.theplanet.co.uk>,
	vandrove@vc.cvut.cz, Andrew Morton <akpm@osdl.org>,
	linware@sh.cvut.cz, fsdevel <linux-fsdevel@vger.kernel.org>,
	lkml <linux-kernel@vger.kernel.org>
Subject: Re: Kernel bug: Bad page state: related to generic symlink code and mmap
Date: Fri, 19 Aug 2005 22:39:03 +0100 (BST)	[thread overview]
Message-ID: <Pine.LNX.4.60.0508192220440.7312@hermes-1.csi.cam.ac.uk> (raw)
In-Reply-To: <Pine.LNX.4.58.0508191352540.3412@g5.osdl.org>

On Fri, 19 Aug 2005, Linus Torvalds wrote:
> On Fri, 19 Aug 2005, Anton Altaparmakov wrote:
> > It does disable link caching.  But I didn't make this up.  This is exactly 
> > what smbfs uses.  I just copied smbfs given ncpfs copies almost everything 
> > smbfs does anyway...
> 
> Can you test whether the untested test-patch I sent out seems to work for 
> your case that bugs out? You'll probably get a few new "initialization 
> from incompatible pointer type" warnings, but I do believe that they 
> should be harmless at least on normal architectures.

Yes, sure.  I have applied your patch to our 2.6.11.4 tree (with the one 
liner change I emailed you just now) and have kicked off a compile.  I am 
afraid the actual testing will have to wait for tomorrow as I was actually 
on the way to bed and the make modules is taking forever or at least 
longer than I can keep my eyes open...

Best regards,

	Anton
-- 
Anton Altaparmakov <aia21 at cam.ac.uk> (replace at with @)
Unix Support, Computing Service, University of Cambridge, CB2 3QH, UK
Linux NTFS maintainer / IRC: #ntfs on irc.freenode.net
WWW: http://linux-ntfs.sf.net/ & http://www-stu.christs.cam.ac.uk/~aia21/

  reply	other threads:[~2005-08-19 21:39 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-19 11:14 Kernel bug: Bad page state: related to generic symlink code and mmap Anton Altaparmakov
2005-08-19 14:20 ` Al Viro
2005-08-19 15:44   ` Anton Altaparmakov
2005-08-19 15:58     ` Al Viro
2005-08-19 16:07     ` Linus Torvalds
2005-08-19 16:21       ` Al Viro
2005-08-19 16:21       ` Linus Torvalds
2005-08-19 16:43         ` Linus Torvalds
2005-08-19 16:53           ` Al Viro
2005-08-19 18:02             ` Al Viro
2005-08-19 18:00               ` Christoph Hellwig
2005-08-19 19:38                 ` Al Viro
2005-08-19 19:41                   ` Matthew Wilcox
2005-08-19 19:43                     ` Al Viro
2005-08-19 21:19                       ` Christoph Hellwig
2005-08-19 20:35                   ` Linus Torvalds
2005-08-19 21:20                     ` Anton Altaparmakov
2005-08-19 21:35                       ` Linus Torvalds
2005-08-19 21:42                     ` Al Viro
2005-08-19 19:16               ` Mika Penttilä
2005-08-19 19:40                 ` Al Viro
2005-08-19 19:50                   ` Mika Penttilä
2005-08-19 20:46           ` Anton Altaparmakov
2005-08-19 20:55             ` Linus Torvalds
2005-08-19 21:39               ` Anton Altaparmakov [this message]
2005-08-19 22:04                 ` Linus Torvalds
2005-08-19 23:15                   ` Al Viro
2005-08-19 23:17                     ` Al Viro
2005-08-20  1:08                     ` Linus Torvalds
2005-08-20  1:15                       ` Al Viro
2005-08-20 12:49                   ` Anton Altaparmakov

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=Pine.LNX.4.60.0508192220440.7312@hermes-1.csi.cam.ac.uk \
    --to=aia21@cam.ac.uk \
    --cc=akpm@osdl.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linware@sh.cvut.cz \
    --cc=torvalds@osdl.org \
    --cc=vandrove@vc.cvut.cz \
    --cc=viro@parcelfarce.linux.theplanet.co.uk \
    /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;
as well as URLs for NNTP newsgroup(s).