Re: [PATCH 4/4] atm/ambassador: kmalloc + memset conversion to kzalloc

In message <[email protected]>,"Rober
t P. J. Day" writes:
>> > in any event, i just thought i'd point it out.  if you're absolutely
>> > sure there will never be another call to setup_dev() from somewhere
>> > else, then, yes, it's safe.
>>
>> I understood your opinions. and partially agree with you.
>> But isn't it a unfounded fear?
>
>i don't know, i just thought i'd mention it.  if no one thinks it's an
>issue, it's certainly fine with me.

its very unlikely that setup_dev() is likely to be called from another
code path.  this patch looks fine to me.  i will take it and get it
submitted on the next merge.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• References:
  • Re: [PATCH 4/4] atm/ambassador: kmalloc + memset conversion to kzalloc
    • From: "Robert P. J. Day" <[email protected]>

• Prev by Date: RE: [PATCH 1/1] scsi: megaraid_sas - Fix random failure of DCDB cmds with sense info
• Next by Date: Re: XFS related Oops (suspend/resume related)
• Previous by thread: Re: [PATCH 4/4] atm/ambassador: kmalloc + memset conversion to kzalloc
• Next by thread: [PATCH 3/4] fib_hash: kmalloc + memset conversion to kzalloc
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]