mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Nathan Scott" <nathans@wobbly.melbourne.sgi.com>
To: Daniel Phillips <phillips@innominate.de>, linux-kernel@vger.kernel.org
Subject: Re: xfs mount opts (was: More better in mount(2))
Date: Mon, 8 Jan 2001 10:06:36 -0400	[thread overview]
Message-ID: <10101081006.ZM21224@wobbly.melbourne.sgi.com> (raw)
In-Reply-To: Daniel Phillips <phillips@innominate.de> "Re: More better in mount(2)" (Jan  5,  3:51pm)
In-Reply-To: <NBBBJGOOMDFADJDGDCPHIEPACJAA.law@sgi.com>  <10101051142.ZM11680@wobbly.melbourne.sgi.com>  <01010503292006.00477@gimli>  <10101051340.ZM14895@wobbly.melbourne.sgi.com>  <3A55DF78.F92AC570@innominate.de>

hi,

On Jan 5,  3:51pm, Daniel Phillips wrote:
> Subject: Re: More better in mount(2)
> Nathan Scott wrote:
> > On Jan 5,  3:26am, Daniel Phillips wrote:
> > > ...
> > > This filesystem mount option parsing code is completely ad hoc, and uses
> > > strtok which is horribly horribly broken.  (Do man strtok and read the
> > > 'Bugs' section.)
> > >
> > > It would be worth thinking about how to do this better.
> > 
> > hmm ... can't claim I wrote this code, just looked at it.
> > are you saying the kernel strtok is horribly broken or just
> > the way its being used here?  (and why?)
> 
> >From the man page:
> ...

yup, I did see that.  I've gone through the code and I can't
see anything wrong with it (tell me if I've missed something).
If the problem is simply that its using strtok, then this must
just be a perceived problem rather than an actual problem (the
data is copied, and noone uses it other than the parsing code,
afaict).

>From a look through how the other filesystems do this, it
seems most use strtok (including ext2).

cheers.

-- 
Nathan
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

      parent reply	other threads:[~2001-01-07 23:08 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <NBBBJGOOMDFADJDGDCPHIEPACJAA.law@sgi.com>
     [not found] ` <10101051142.ZM11680@wobbly.melbourne.sgi.com>
     [not found]   ` <01010503292006.00477@gimli>
     [not found]     ` <10101051340.ZM14895@wobbly.melbourne.sgi.com>
2001-01-05 14:51       ` More better in mount(2) Daniel Phillips
2001-01-05 20:26         ` Andreas Dilger
2001-01-08 14:06         ` Nathan Scott [this message]

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=10101081006.ZM21224@wobbly.melbourne.sgi.com \
    --to=nathans@wobbly.melbourne.sgi.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=phillips@innominate.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

Powered by JetHome