public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Alex Scheele" <alex@packetstorm.nu>
To: <l.s.r@web.de>
Cc: "Dave Jones" <davej@suse.de>, "Lkml" <linux-kernel@vger.kernel.org>
Subject: RE: [patch][2.5.4-dj4] cleanup to use strsep for fs/fat/inode.c
Date: Sun, 10 Feb 2002 15:27:47 +0100	[thread overview]
Message-ID: <IOEMLDKDBECBHMIOCKODKENACJAA.alex@packetstorm.nu> (raw)
In-Reply-To: <20020210141918.3552d0fc.l.s.r@web.de>

> > This patch changes all use of strtok() to strsep().
> > Strtok() isn't SMP/thread safe. strsep is considered safer.
> 
> OK, but ...
> 
> > -       for (this_char = strtok(options,","); this_char;
> > -            this_char = strtok(NULL,",")) {
> 
> This _does not_ change the value of 'options'.
> 
> > +       while ((this_char = strsep(&options,",")) != NULL) {
> 
> This _does_ change the value of 'options'. Problem is, it's
> used later. Same is true for your patch to fs/vfat/namei.c.

Ok, sorry seems i overlooked that. Patches, for both files, below 
should fix it.

Cheers,
--
	Alex (alex@packetstorm.nu)


diff -uN linux-2.5.3-dj4/fs/vfat/namei.c linux/fs/vfat/namei.c
--- linux-2.5.3-dj4/fs/vfat/namei.c     Mon Jan 28 22:20:44 2002
+++ linux/fs/vfat/namei.c       Sun Feb 10 15:28:26 2002
@@ -97,6 +97,7 @@
 static int parse_options(char *options,        struct fat_mount_options *opts)
 {
        char *this_char,*value,save,*savep;
+       char *optptr = options;
        int ret, val;

        opts->unicode_xlate = opts->posixfs = 0;
@@ -114,7 +115,9 @@
        save = 0;
        savep = NULL;
        ret = 1;
-       for (this_char = strtok(options,","); this_char; this_char = strtok(NULL,",")) {
+       while ((this_char = strsep(&optptr,",")) != NULL) {
+               if (!*this_char)
+                       continue;
                if ((value = strchr(this_char,'=')) != NULL) {
                        save = *value;
                        savep = value;
diff -uN linux-2.5.3-dj4/fs/fat/inode.c linux/fs/fat/inode.c
--- linux-2.5.3-dj4/fs/fat/inode.c      Sat Feb  9 21:57:39 2002
+++ linux/fs/fat/inode.c        Sun Feb 10 15:51:42 2002
@@ -203,7 +203,7 @@
                         char *cvf_format, char *cvf_options)
 {
        char *this_char,*value,save,*savep;
-       char *p;
+       char *p, *optptr = options;
        int ret = 1, len;

        opts->name_check = 'n';
@@ -223,8 +223,9 @@
                goto out;
        save = 0;
        savep = NULL;
-       for (this_char = strtok(options,","); this_char;
-            this_char = strtok(NULL,",")) {
+       while ((this_char = strsep(&optptr,",")) != NULL) {
+               if (!*this_char)
+                       continue;
                if ((value = strchr(this_char,'=')) != NULL) {
                        save = *value;
                        savep = value;




  reply	other threads:[~2002-02-10 14:28 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-10 13:19 [patch][2.5.4-dj4] cleanup to use strsep for fs/fat/inode.c René Scharfe
2002-02-10 14:27 ` Alex Scheele [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-02-10  1:48 Alex Scheele

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=IOEMLDKDBECBHMIOCKODKENACJAA.alex@packetstorm.nu \
    --to=alex@packetstorm.nu \
    --cc=davej@suse.de \
    --cc=l.s.r@web.de \
    --cc=linux-kernel@vger.kernel.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