public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Martin Dalecki <dalecki@evision-ventures.com>
To: Andries.Brouwer@cwi.nl
Cc: linux-kernel@vger.kernel.org
Subject: Re: PATCH for 2.4.3 - tinny mount code cleanup (kernel 0.97  compatibility)
Date: Fri, 27 Apr 2001 11:52:29 +0200	[thread overview]
Message-ID: <3AE9415D.A6F65CAC@evision-ventures.com> (raw)
In-Reply-To: <UTC200104261723.TAA20960.aeb@vlet.cwi.nl>

Andries.Brouwer@cwi.nl wrote:
> 
>     From: Martin Dalecki <dalecki@evision-ventures.com>
> 
>     The attached patch is fixing georgeous "backward compatibility"
>     in the mount system command. It is removing two useless defines in
>     the kernel headers and finally doubles the number of possible
>     flags for the mount command.
> 
>     Please apply.
> 
> You have it all backwards. Your patch halves the number of
> possible flags. The present kernel can use 32 (or 31) flags.
> 
>     @@ -1317,10 +1313,6 @@
>          struct super_block *sb;
>          int retval = 0;
> 
>     -    /* Discard magic */
>     -    if ((flags & MS_MGC_MSK) == MS_MGC_VAL)
>     -        flags &= ~MS_MGC_MSK;
>     -
>          /* Basic sanity checks */
> 
>          if (!dir_name || !*dir_name || !memchr(dir_name, 0, PAGE_SIZE))
> 
> You see what this code does: if the top half has this old magic
> (as it has today in 100% of all Linux installations),
> then the top half is ignored.
> If the value is non-conventional, it can be used to mean something.
> 
> Maybe you did not realize that mount still puts that value there?

Oops typo in find ./ ... grep on my side  maybe?

Anyway at least the comment there is at best missleading...

> The mount we use today will be around for many years to come.
> This "discard magic" part cannot be removed within five years.
> 
> Andries
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/

-- 
- phone: +49 214 8656 283
- job:   eVision-Ventures AG, LEV .de (MY OPINIONS ARE MY OWN!)
- langs: de_DE.ISO8859-1, en_US, pl_PL.ISO8859-2, last ressort:
ru_RU.KOI8-R

  reply	other threads:[~2001-04-27 10:04 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-26 17:23 PATCH for 2.4.3 - tinny mount code cleanup (kernel 0.97 compatibility) Andries.Brouwer
2001-04-27  9:52 ` Martin Dalecki [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-04-26  8:51 Martin Dalecki

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=3AE9415D.A6F65CAC@evision-ventures.com \
    --to=dalecki@evision-ventures.com \
    --cc=Andries.Brouwer@cwi.nl \
    --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