From: David Mosberger <davidm@napali.hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [jakub@redhat.com: Re: [brian.j.vandecoevering@intel.com: RE: [Linux-ia64] problems with ppp/ppp
Date: Fri, 12 Dec 2003 17:21:59 +0000 [thread overview]
Message-ID: <marc-linux-ia64-107125003407188@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-107124350029067@msgid-missing>
>>>>> On Fri, 12 Dec 2003 10:37:16 -0500, Bill Nottingham <notting@redhat.com> said:
Bill> Back long ago, I reported a problem with PPP on ia64:
Bill> http://www.gelato.unsw.edu.au/linux-ia64/0105/1641.html
Bill> We added the workaround in our tree for earlier releases, and
Bill> promptly forgot about it; however, someone reported that RHEL
Bill> 3 has the same issue (as we took the workaround out.)
Bill> Jakub noticed the following - does this explain the problem?
Yes, it sure does. Argh, passing functions to get/put-user macro
arguments. I suppose that's legal... ;-(
Bill> But, a function call clobbers r8. Guess a __typeof(x) __x Bill> (x); before __pu_err and s/x/__x/ is needed. Probably
Bill> __pu_addr decl should be moved before __pu_err is initialized
Bill> too, otherwise extern int *foo (); put_user (0, foo ()); might
Bill> not work properly.
Yeah, we need to be careful not to evalute any macro arguments while
using the special register-usage convention needed for the exception
handlers. It affects get_user(), too. Let me work on a patch.
--david
next prev parent reply other threads:[~2003-12-12 17:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-12 15:37 [jakub@redhat.com: Re: [brian.j.vandecoevering@intel.com: RE: [Linux-ia64] problems with ppp/pppd: p Bill Nottingham
2003-12-12 16:09 ` [jakub@redhat.com: Re: [brian.j.vandecoevering@intel.com: RE: [Linux-ia64] problems with ppp/ppp Bjorn Helgaas
2003-12-12 17:21 ` David Mosberger [this message]
2003-12-13 9:11 ` David Mosberger
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=marc-linux-ia64-107125003407188@msgid-missing \
--to=davidm@napali.hpl.hp.com \
--cc=linux-ia64@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