# Re: network regression: cannot rename netdev twice

- From: Kay Sievers \<hidden\>
- Date: 2012-01-31 11:59:09 
- List: netdev
- Page: https://ratatoskr.run/netdev/2012/01/3815887
- Thread: https://ratatoskr.run/netdev/2012/01/3815841/t.md

```text
On Tue, Jan 31, 2012 at 12:17, Jiri Slaby [ref] wrote:
> On 01/31/2012 12:13 PM, Kay Sievers wrote:

>> This is a command sequence you type manually?
>
> Yea, and it is working with 3.3.0-rc1-next-20120124_64+. Not with
> 3.3.0-rc1-next-20120131_64+.
>
>> You are sure that userspace is not working in the background,
>> triggered by uevents, and comes into your way here?
>
> Note that krtek exists after the first command. But cannot be renamed
> further.

Yeah, I can confirm the problem here. I works fine with earlier
kernels and fails with the latest -next:

# uname -r
3.3.0-rc1-next-20120131+
# modprobe dummy
# ip link set dummy0 name foo0
# ip link set foo0 name bar0
RTNETLINK answers: No such file or directory

Kay
```