netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: YOSHIFUJI Hideaki <yoshfuji@linux-ipv6.org>
To: Stefan Richter <stefanr@s5r6.in-berlin.de>
Cc: netdev@vger.kernel.org, linux1394-devel@lists.sourceforge.net,
	davem@davemloft.net, YOSHIFUJI Hideaki <yoshfuji@linux-ipv6.org>
Subject: Re: [net-next (TAKE 2) 3/4] firewire net, ipv4 arp: Extend hardware address and remove driver-level packet inspection.
Date: Mon, 11 Feb 2013 01:32:48 +0900	[thread overview]
Message-ID: <5117CBB0.3030000@linux-ipv6.org> (raw)
In-Reply-To: <20130210151056.3e6e9f53@stein>

(2013年02月10日 23:10), Stefan Richter wrote:
> On Feb 10 YOSHIFUJI Hideaki wrote:
>> @@ -1140,18 +1051,6 @@ static int fwnet_broadcast_start(struct fwnet_device *dev)
>>  	unsigned long offset;
>>  	unsigned u;
>>  
>> -	if (dev->local_fifo == FWNET_NO_FIFO_ADDR) {
>> -		dev->handler.length = 4096;
>> -		dev->handler.address_callback = fwnet_receive_packet;
>> -		dev->handler.callback_data = dev;
>> -
>> -		retval = fw_core_add_address_handler(&dev->handler,
>> -					&fw_high_memory_region);
>> -		if (retval < 0)
>> -			goto failed_initial;
>> -
>> -		dev->local_fifo = dev->handler.offset;
>> -	}
>>  
>>  	max_receive = 1U << (dev->card->max_receive + 1);
>>  	num_packets = (FWNET_ISO_PAGE_COUNT * PAGE_SIZE) / max_receive;
>> @@ -1234,8 +1133,6 @@ static int fwnet_broadcast_start(struct fwnet_device *dev)
>>  	dev->broadcast_rcv_context = NULL;
>>   failed_context_create:
>>  	fw_core_remove_address_handler(&dev->handler);
>> - failed_initial:
>> -	dev->local_fifo = FWNET_NO_FIFO_ADDR;
>>  
>>  	return retval;
>>  }
> 
> [...]
> 
>> @@ -1546,12 +1421,21 @@ static int fwnet_probe(struct device *_dev)
>>  	dev->broadcast_rcv_context = NULL;
>>  	dev->broadcast_xmt_max_payload = 0;
>>  	dev->broadcast_xmt_datagramlabel = 0;
>> -	dev->local_fifo = FWNET_NO_FIFO_ADDR;
>>  	dev->queued_datagrams = 0;
>>  	INIT_LIST_HEAD(&dev->peer_list);
>>  	dev->card = card;
>>  	dev->netdev = net;
>>  
>> +	dev->handler.length = 4096;
>> +	dev->handler.address_callback = fwnet_receive_packet;
>> +	dev->handler.callback_data = dev;
>> +
>> +	ret = fw_core_add_address_handler(&dev->handler, &fw_high_memory_region);
>> +	if (ret < 0)
>> +		goto out;
>> +
>> +	dev->local_fifo = dev->handler.offset;
>> +
>>  	/*
>>  	 * Use the RFC 2734 default 1500 octets or the maximum payload
>>  	 * as initial MTU
> 
> If at all possible, please put changes of this kind into a separate
> patch.
> 
> I get a distinct feeling that the error handling paths in
> fwnet_broadcast_start() and in fwnet_probe() respectively became buggy now.
> This would be easier to verify if shifting this code was done in a separate
> change.

Will do.

--yoshfuji

  reply	other threads:[~2013-02-10 16:32 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-10  9:02 [net-next (TAKE 2) 3/4] firewire net, ipv4 arp: Extend hardware address and remove driver-level packet inspection YOSHIFUJI Hideaki
2013-02-10 14:10 ` Stefan Richter
2013-02-10 16:32   ` YOSHIFUJI Hideaki [this message]
2013-02-10 14:31 ` Stefan Richter

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=5117CBB0.3030000@linux-ipv6.org \
    --to=yoshfuji@linux-ipv6.org \
    --cc=davem@davemloft.net \
    --cc=linux1394-devel@lists.sourceforge.net \
    --cc=netdev@vger.kernel.org \
    --cc=stefanr@s5r6.in-berlin.de \
    /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).