netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Stephen Biggs" <yrgrknmxpzlk@gawab.com>
To: yoshfuji@linux-ipv6.org, davem@davemloft.com, netdev@oss.sgi.com,
	yoshfuji@linux-ipv6.org, domen@coderock.org
Subject: Re: [patch 4/5] net/ipv6/ip6_flowlabel.c: copy_to_user return code
Date: Mon, 07 Mar 2005 09:13:42 +0200	[thread overview]
Message-ID: <422C1B46.21973.35151C@localhost> (raw)
In-Reply-To: <20050307.073843.09980515.yoshfuji@linux-ipv6.org>

Mr. Hideaki,

Thank you very much (domo arigato gozaimasu) for your feedback.  Please 
see below for my comments.

On 7 Mar 2005 at 7:38, B wrote:

> In article <20050307.073213.32943613.yoshfuji@linux-ipv6.org> (at Mon, 07 Mar 2005 07:32:13 +0900 (JST)), YOSHIFUJI Hideaki /  $B5HF#1QL@ (B <yoshfuji@linux-ipv6.org> says:
> 
> > In article <20050306222118.401D11ED3D@trashy.coderock.org> (at Sun, 06 Mar 2005 23:21:17 +0100), domen@coderock.org says:
> > 
> > > 
> > > compile warning cleanup - handle copy_to/from_user error 
> > > returns
> > 
> > Wrong. You introduce a leak.
> 
> Ah, sorry, not really,

Actually, you are correct.  This is one of my first attempts at a patch 
submittal and this is one of a few patches where I did not check for side 
effects.  I will try very much not to make that same mistake again.

> but I still think it is wrong:
> fl_intern() insert it to hash, and
> then you freed up the memory.
> I believe this is wrong.

Yes, you are completely correct, and thank you for catching this.

I will submit a more correct patch shortly.

> 
> --yoshfuji
> 

      reply	other threads:[~2005-03-07  7:13 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-06 22:21 [patch 4/5] net/ipv6/ip6_flowlabel.c: copy_to_user return code domen
2005-03-06 22:32 ` YOSHIFUJI Hideaki / 吉藤英明
2005-03-06 22:38   ` YOSHIFUJI Hideaki / 吉藤英明
2005-03-07  7:13     ` Stephen Biggs [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=422C1B46.21973.35151C@localhost \
    --to=yrgrknmxpzlk@gawab.com \
    --cc=davem@davemloft.com \
    --cc=domen@coderock.org \
    --cc=netdev@oss.sgi.com \
    --cc=yoshfuji@linux-ipv6.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).