Including STRTOK_R in a LSM

I am aware strtok was removed from the kernel in 2002. However strtok_r is more desirable than strsep as I do not want to know about 'blank fields' (2 consecutive delimiters). Is it acceptable to simply include the strtok_r code in my security module? or should I create a wrapper for strsep to ignore blanks?

Thanks,

Z. Cliffe Schreuders

Please cc me.
-
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/

---

• Follow-Ups:
  • Re: Including STRTOK_R in a LSM
    • From: Jan Engelhardt <[email protected]>

• Prev by Date: RE : Re: RE : Re: x86 setup code rewrite in C - revised
• Next by Date: Re: *at syscalls for xattrs?
• Previous by thread: [GIT PULL] LED updates
• Next by thread: Re: Including STRTOK_R in a LSM
• 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]