All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chen Gang <gang.chen@asianux.com>
To: Jan Kara <jack@suse.cz>
Cc: Theodore Ts'o <tytso@mit.edu>,
	akpm@linux-foundation.org, linux-ext4@vger.kernel.org
Subject: Re: [Suggestion] fs/ext3: memory leak by calling set_qf_name or clear_qf_name, many times.
Date: Mon, 14 Jan 2013 10:29:16 +0800	[thread overview]
Message-ID: <50F36D7C.2020107@asianux.com> (raw)
In-Reply-To: <50EB8EDA.3020709@asianux.com>

于 2013年01月08日 11:13, Chen Gang 写道:
> 于 2013年01月08日 03:54, Jan Kara 写道:
>> > On Fri 04-01-13 13:39:37, Chen Gang wrote:
>>> >>   if what I guess is true
>>> >>     it seems we have to duplicate memory for old_opts in ext3_remount.
>>> >>     and for clear_qf_name, set_qf_name, ext3_remount:
>>> >>       use normal memory allocation and free ways instead of current using.
>> >   Yes. Updated patch attached.
>> > 
>   at least for me, Jan Kara's patch is ok. thanks.
> 
>   welcome another members (especially Theodore Ts'o) to giving confirmation or completion.
>   also welcome to checking this suggestion whether valid for fs/ext4.

  I will send a relative patch for fs/ext4, just according to Jan Kara's patch.
  I will send it within 2 weeks (excuse me, I have to do another things this week).

  welcome any additional suggestions and completions.

  thanks.

-- 
Chen Gang

Asianux Corporation
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

      reply	other threads:[~2013-01-14  2:28 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-26  5:04 [Suggestion] fs/ext3: memory leak by calling set_qf_name or clear_qf_name, many times Chen Gang
2012-12-27  8:06 ` Chen Gang
2012-12-31 12:06 ` Jan Kara
2013-01-04  5:39   ` Chen Gang
2013-01-07 19:54     ` Jan Kara
2013-01-08  3:13       ` Chen Gang
2013-01-14  2:29         ` Chen Gang [this message]

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=50F36D7C.2020107@asianux.com \
    --to=gang.chen@asianux.com \
    --cc=akpm@linux-foundation.org \
    --cc=jack@suse.cz \
    --cc=linux-ext4@vger.kernel.org \
    --cc=tytso@mit.edu \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.