mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: Michael Tokarev <mjt@tls.msk.ru>
Cc: Arnd Bergmann <arnd@arndb.de>,
	Linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: compat ioctl32 for /dev/snapshot?
Date: Mon, 13 Jul 2009 22:21:16 +0200	[thread overview]
Message-ID: <20090713202116.GB2569@elf.ucw.cz> (raw)
In-Reply-To: <4A5AD963.5070908@msgid.tls.msk.ru>

On Mon 2009-07-13 10:51:15, Michael Tokarev wrote:
> Arnd Bergmann wrote:
>> On Sunday 12 July 2009, Michael Tokarev wrote:
>>> As I mentioned in my first email, I'm not the right person to
>>> do the patch.  But regardless, I spent about a day understanding
>>> this stuff (or trying to, anyway) - 100% useless day - and when
>>> I thought I have a patch someone else spoken up and said this
>>> way (compat_ioctl) is the wrong approach now.  And sent another,
>>> also trivial patch, adding compat calls right to the proper
>>> place in kernel/power.c.  Which (the patch) has been ignored
>>> too.
>>
>> I never got a reply from you saying whether or not the patch
>> I sent actually worked. If you or someone else can confirm it,
>> I'll resend with the fixes you mentioned.
>
> In order to (try to) check if it works or not, another userspace
> component has to be fixed to support 32/64 bit mode.  It's uswsusp,
> which currently assumes swap space structures are all 32bits.  So
> it isn't possible to immediately check if it works or not -- just
> ioctl(s) aren't enough.  Complete fix (kernel+user space) requires
> both, fixing all remaining (yet unknown) issues in old and new
> code on the way.

Well, there seems to be single structure in s2disk; that does not seem
that hard to fix.

> For now, I think it's best to let Pavel or Rafael to decide what
> to do with all this.

I don't currently have easy access to 64bit machine, so I guess it is
up to someone else.

-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

  reply	other threads:[~2009-07-13 20:21 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-04  9:29 Michael Tokarev
2009-05-04  9:35 ` Andi Kleen
2009-05-04 10:55   ` Michael Tokarev
2009-05-04 11:12     ` Andi Kleen
2009-05-04 21:55       ` Rafael J. Wysocki
2009-05-05 11:38         ` Arnd Bergmann
2009-05-05 11:43           ` Michael Tokarev
2009-05-05 23:13             ` Rafael J. Wysocki
2009-05-04 11:52     ` Arnd Bergmann
2009-05-04 22:26       ` Michael Tokarev
2009-05-05 10:58         ` Arnd Bergmann
2009-05-04 21:58 ` Rafael J. Wysocki
2009-07-10 16:21 ` Pavel Machek
2009-07-12  0:19   ` Michael Tokarev
2009-07-12 15:07     ` Arnd Bergmann
2009-07-13  6:51       ` Michael Tokarev
2009-07-13 20:21         ` Pavel Machek [this message]
2009-07-14  6:57           ` Michael Tokarev
2009-07-14  9:55             ` Pavel Machek

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=20090713202116.GB2569@elf.ucw.cz \
    --to=pavel@ucw.cz \
    --cc=arnd@arndb.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mjt@tls.msk.ru \
    /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

all inboxes | Powered by JetHome®