public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Michael Tokarev <mjt@tls.msk.ru>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Ian Kent <raven@themaw.net>,
	"stable@kernel.org" <stable@kernel.org>,
	autofs@vger.kernel.org,
	Linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Breaking userspace? Re: 3.0.24 broke aufofs on mixed 32/64bit environment
Date: Tue, 24 Apr 2012 20:16:54 +0400	[thread overview]
Message-ID: <4F96D1F6.80701@msgid.tls.msk.ru> (raw)
In-Reply-To: <4F96D0E7.9060000@msgid.tls.msk.ru>

On 24.04.2012 20:12, Michael Tokarev wrote:
> On 24.04.2012 19:08, Linus Torvalds wrote:

>>> Kernel has been shipping with this brokeness for quite
>>> some time, namely, since introduction of autofs4, dated
>>> Mon Mar 27 01:14:55 2006 -0800 (commit 5c0a32fc2cd0).
>>

>> Actually, that's just not true. The *main* users of the interface seem
>> to have never fixed anything. As far as I know, neither the upstream
>> autofs tools nor several of the big distributions ever had patches to
>> make 32-bit autofs work with the old broken 64-bit compat layer.
[]
> I don't know how old this code is, but it definitely is in the
> 5.0.1 upstream tarball, and the file there is dated
> Feb-20, 2007 - at least 3 years after the initial bug in kernel.

I meant to say "about a year after the initial bug in kernel".

And I think it was me who found the original issue, -- i mean,
discovered that it does not work, not found the real bug - but
I don't remember anymore.  This stuff looks very familiar for
some reason however... ;)

Thanks,

/mjt

  reply	other threads:[~2012-04-24 16:16 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <4F94222C.6080608@msgid.tls.msk.ru>
     [not found] ` <1335172741.2226.10.camel@perseus.themaw.net>
     [not found]   ` <4F958352.7050106@msgid.tls.msk.ru>
     [not found]     ` <4F95897B.2040103@msgid.tls.msk.ru>
2012-04-23 18:07       ` Breaking userspace? Re: 3.0.24 broke aufofs on mixed 32/64bit environment Michael Tokarev
2012-04-24  1:25         ` Ian Kent
2012-04-24  3:40           ` Ian Kent
2012-04-24  4:06             ` Michael Tokarev
2012-04-24 15:08         ` Linus Torvalds
2012-04-24 16:12           ` Michael Tokarev
2012-04-24 16:16             ` Michael Tokarev [this message]
2012-04-24 19:53             ` Linus Torvalds
2012-04-24 20:42               ` Thomas Meyer
2012-04-24 21:01                 ` Linus Torvalds
2012-04-25  4:05                   ` Michael Tokarev
2012-04-25  4:08                     ` Linus Torvalds

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=4F96D1F6.80701@msgid.tls.msk.ru \
    --to=mjt@tls.msk.ru \
    --cc=autofs@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=raven@themaw.net \
    --cc=stable@kernel.org \
    --cc=torvalds@linux-foundation.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