From: "David S. Miller" <davem@davemloft.net>
To: dipankar@in.ibm.com
Cc: linux-kernel@vger.kernel.org, torvalds@osdl.org, akpm@osdl.org
Subject: Re: [PATCH]: Brown paper bag in fs/file.c?
Date: Wed, 14 Sep 2005 12:57:50 -0700 (PDT) [thread overview]
Message-ID: <20050914.125750.05416211.davem@davemloft.net> (raw)
In-Reply-To: <20050914191842.GA6315@in.ibm.com>
From: Dipankar Sarma <dipankar@in.ibm.com>
Date: Thu, 15 Sep 2005 00:48:42 +0530
> __free_fdtable() is used only when the fdarray/fdset are vmalloced
> (use of the workqueue) or there is a race between two expand_files().
> That might be why we haven't seen this cause any explicit problem
> so far.
>
> This would be an appropriate patch - (untested). I will update
> as soon as testing is done.
Thanks.
I still can't figure out what causes my sparc64 bug. Somehow a
kmalloc() chunk of file pointers gets freed too early, the SLAB is
shrunk due to memory pressure so the page containing that object gets
freed, that page ends up as an anonymous page in userspace, but filp
writes from the older usage occurs and corrupts the page.
I wonder if we simply leave a stale pointer around to the older
fd array in some case.
next prev parent reply other threads:[~2005-09-14 19:57 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-14 18:31 David S. Miller
2005-09-14 18:48 ` David S. Miller
2005-09-14 19:05 ` David S. Miller
2005-09-14 19:18 ` Dipankar Sarma
2005-09-14 19:57 ` David S. Miller [this message]
2005-09-14 20:15 ` Dipankar Sarma
2005-09-14 20:29 ` David S. Miller
2005-09-14 21:17 ` [PATCH] reorder struct files_struct Eric Dumazet
2005-09-14 21:35 ` Peter Staubach
2005-09-14 22:02 ` Dipankar Sarma
2005-09-14 22:17 ` Andrew Morton
2005-09-14 22:42 ` Eric Dumazet
2005-09-14 22:50 ` Dipankar Sarma
2005-09-14 23:19 ` Eric Dumazet
2005-09-15 4:54 ` Dipankar Sarma
2005-09-15 6:17 ` Eric Dumazet
2005-09-15 9:35 ` Dipankar Sarma
2005-09-15 17:11 ` Eric Dumazet
2005-09-15 21:06 ` [PATCH]: Brown paper bag in fs/file.c? David S. Miller
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=20050914.125750.05416211.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=akpm@osdl.org \
--cc=dipankar@in.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.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
all inboxes | Powered by JetHome®