linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: James W McMechan <mcmechanjw@juno.com>
To: hugh@veritas.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: Oops with tmpfs on both 2.4.22 & 2.6.0-test11
Date: Sun, 30 Nov 2003 18:59:11 -0800	[thread overview]
Message-ID: <20031130.185915.-1591395.7.mcmechanjw@juno.com> (raw)

Hello, I have a test program  which will generate the Oops easily.
No maintainer was listed for tmpfs and the best Google reference is
about 2 years back, and it does not seem to be about this issue.

This Oops both 2.4.22 and 2.6.0-test11
It results from a ARCH=um bugreport and I kept making the
test program shorter, now down to one executable line.

It oops with the list poison address on 2.6.0-test11
Neither myself nor William Lee Irwin III know what the
list_del(q);
list_add(q, &dentry->d_subdirs);
from fs/libfs.c:90 or 137 is intended to do but he suggested you might
know
I think that is where it is corrupting the list entries.

/* by James_McMechan at hotmail com */                                   
      
/* test2 program to Oops shmfs mounted at /dev/shm */
/* yes it is dumb but unprivileged users should not be able */
/* to Oops the kernel regardless of how dumb the program */
#include <sys/types.h>
#include <dirent.h>
main()
{/* off 0 is "." off 1 is ".." off 2 is empty */
        seekdir(opendir("/dev/shm"), (off_t) 2);
}

On Sun, 30 Nov 2003 20:51:01 -0800 William Lee Irwin III
<wli@holomorphy.com> writes:
> On Sun, Nov 30, 2003 at 06:06:41PM -0800, James W McMechan wrote:
> > Have you got a suggestion on who to bug, I have not found
> > maintainers on tmpfs or now the libfs section.
> 
> Hugh Dickins is highly clueful and generally maintains tmpfs. He's
> fixed bugs in fs/libfs.c before, too.
> 
> 
> -- wli

________________________________________________________________
The best thing to hit the internet in years - Juno SpeedBand!
Surf the web up to FIVE TIMES FASTER!
Only $14.95/ month - visit www.juno.com to sign up today!

             reply	other threads:[~2003-12-01  5:37 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-01  2:59 James W McMechan [this message]
2003-12-01 11:37 ` Oops with tmpfs on both 2.4.22 & 2.6.0-test11 Maneesh Soni
     [not found] <20031207.140732.-1654081.3.mcmechanjw@juno.com>
2003-12-08  5:10 ` Maneesh Soni
  -- strict thread matches above, loose matches on Subject: below --
2003-12-07 22:48 James McMechan
2003-12-03 11:06 James W McMechan
2003-12-03 12:02 ` Maneesh Soni
2003-12-01  2:06 James W McMechan
2003-12-01  4:51 ` William Lee Irwin III
2003-12-01  1:06 James W McMechan
2003-12-01  3:43 ` William Lee Irwin III
2003-11-30 21:17 James W McMechan
2003-12-01  1:21 ` William Lee Irwin III
2003-12-01  7:58   ` Andries Brouwer
2003-12-01  8:00     ` William Lee Irwin III
2003-11-30 17:34 James W McMechan
2003-11-30 20:06 ` William Lee Irwin III
2003-11-30 21:21   ` Oleg Drokin
2003-11-30 16:57 James W McMechan
2003-11-30 19:27 ` William Lee Irwin III

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=20031130.185915.-1591395.7.mcmechanjw@juno.com \
    --to=mcmechanjw@juno.com \
    --cc=hugh@veritas.com \
    --cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).