public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Daniel Aragonés" <danarag@gmail.com>
To: Jiri Slaby <jirislaby@gmail.com>
Cc: Andrew Morton <akpm@osdl.org>,
	Pekka Enberg <penberg@cs.helsinki.fi>,
	Arjan van de Ven <arjan@infradead.org>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH/RFC] minix filesystem update to V3 diffed to 2.6.17-rc3
Date: Mon, 01 May 2006 20:50:09 +0200	[thread overview]
Message-ID: <44565861.3000907@gmail.com> (raw)
In-Reply-To: <44564B34.6020109@gmail.com>

Jiri Slaby wrote:

> Ok, which error?
> 
> regards,

Hi all,

Well, I have the error notice no longer at hand, but it was of the family of unreferenceable addresses. Do not forget that this fragment of code is related to functions included in bitops.h, and are 
architecture dependent and written in assembler.

By other hand, the dump core produced if kfree is employed, is already known and indexed through Google. So I am forced to set 'offset = NULL' in order to reassign the same old location to the next 
recurrence of kmalloc. So, things stay controlled.

What I can tell you for sure is that, employing this code, file after file writings and erasings of directories containing about 6.000 files to and from a Minix partition from Linux, filling and 
emptying spaces of 200 MB for testing, don't show any bad signal of memory leakage employing blocksizes of 4K which force the use of 'offset'.

Regards,

Daniel

  reply	other threads:[~2006-05-01 18:51 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-01 13:05 [PATCH/RFC] minix filesystem update to V3 diffed to 2.6.17-rc3 Daniel Aragonés
2006-05-01 13:41 ` Jiri Slaby
2006-05-01 17:03 ` Andrew Morton
2006-05-01 17:19   ` Daniel Aragonés
2006-05-01 17:54     ` Jiri Slaby
2006-05-01 18:50       ` Daniel Aragonés [this message]
2006-05-01 20:30       ` Joshua Hudson
2006-05-06 16:29 ` Al Viro
2006-05-06 16:37   ` Al Viro
2006-05-06 22:04     ` minixfs bitmaps and associated lossage Al Viro
2006-05-06 22:25       ` Matthew Wilcox
2006-05-06 22:26       ` Linus Torvalds
2006-05-06 23:10         ` Al Viro
2006-05-06 23:42           ` Linus Torvalds
2006-05-07  7:37             ` Al Viro
2006-05-07  7:35       ` Pavel Machek

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=44565861.3000907@gmail.com \
    --to=danarag@gmail.com \
    --cc=akpm@osdl.org \
    --cc=arjan@infradead.org \
    --cc=jirislaby@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=penberg@cs.helsinki.fi \
    /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