From: Fan Du <fengyuleidian0615@gmail.com>
To: David Miller <davem@davemloft.net>
Cc: fan.du@intel.com, steffen.klassert@secunet.com,
herbert@gondor.apana.org.au, netdev@vger.kernel.org
Subject: Re: [PATCH ipsec-next] xfrm: Do not parse 32bits compiled xfrm netlink msg on 64bits host
Date: Tue, 27 Jan 2015 15:44:36 +0800 [thread overview]
Message-ID: <54C741E4.2000009@gmail.com> (raw)
In-Reply-To: <20150126.233938.513240875461315013.davem@davemloft.net>
于 2015年01月27日 15:39, David Miller 写道:
> From: Fan Du <fan.du@intel.com>
> Date: Tue, 27 Jan 2015 10:54:22 +0800
>
>> @@ -2419,6 +2419,11 @@ static int xfrm_user_rcv_msg(struct sk_buff *skb, struct nlmsghdr *nlh)
>> const struct xfrm_link *link;
>> int type, err;
>>
>> +#ifdef CONFIG_COMPAT
>> + if (is_compat_task())
>> + return -EPERM;
>> +#endif
>> +
>
> This seems more like an unsupported operation rather then a permission
> problem.
>
how about *ENOTSUPP* ?
--
No zuo no die but I have to try.
next prev parent reply other threads:[~2015-01-27 7:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-27 2:54 [PATCH ipsec-next] xfrm: Do not parse 32bits compiled xfrm netlink msg on 64bits host Fan Du
2015-01-27 7:39 ` David Miller
2015-01-27 7:44 ` Fan Du [this message]
2015-01-27 8:12 ` David Miller
2015-01-27 23:32 ` Bill Fink
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=54C741E4.2000009@gmail.com \
--to=fengyuleidian0615@gmail.com \
--cc=davem@davemloft.net \
--cc=fan.du@intel.com \
--cc=herbert@gondor.apana.org.au \
--cc=netdev@vger.kernel.org \
--cc=steffen.klassert@secunet.com \
/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;
as well as URLs for NNTP newsgroup(s).