From: Bamvor Jian Zhang <bamvor.zhangjian@huawei.com>
To: Catalin Marinas <catalin.marinas@arm.com>
Cc: linux-arch@vger.kernel.org, mpe@ellerman.id.au,
benh@kernel.crashing.org, deller@gmx.de,
"dingtianhong@huawei.com" <dingtianhong@huawei.com>,
heiko.carstens@de.ibm.com,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Will Deacon <Will.Deacon@arm.com>,
jejb@parisc-linux.org, cmetcalf@ezchip.com,
"lizefan@huawei.com" <lizefan@huawei.com>,
paulus@samba.org, ralf@linux-mips.org, hpa@zytor.com,
schwidefsky@de.ibm.com, tglx@linutronix.de, mingo@redhat.com,
davem@davemloft.net,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] compat: Fix endian issue in union sigval
Date: Tue, 17 Feb 2015 15:15:15 +0800 [thread overview]
Message-ID: <54E2EA83.8080800@huawei.com> (raw)
In-Reply-To: <20150213104455.GA3508@e104818-lin.cambridge.arm.com>
On 2015/2/13 18:44, Catalin Marinas wrote:
> On Fri, Feb 13, 2015 at 04:00:43PM +0800, Bamvor Jian Zhang wrote:
>> On 2015/2/11 23:40, Catalin Marinas wrote:
>>> On Wed, Feb 11, 2015 at 07:22:08PM +0800, Bamvor Jian Zhang wrote:
>>>> On 2015/2/10 20:27, Catalin Marinas wrote:
>>>>> On Tue, Feb 10, 2015 at 10:10:11AM +0000, Zhang Jian(Bamvor) wrote:
>> ...
>>> The native sigval_t is also a union but on 64-bit big endian, the
>>> sival_int overlaps with the most significant 32-bit of the sival_ptr.
>>> So reading sival_int would always be 0. When the compat siginfo is
>>> copied to user, arm64 reads the native sival_ptr (si_ptr) and converts
>>> it to the compat one, getting the correct 32-bit value. However, other
>>> architectures access sival_int (si_int) instead which breaks with your
>>> get_compat_sigevent() changes.
>>>
>>>>> I think the correct fix is in the arm64 code:
>>>>
>>>> The following code could fix my issue.
>>>
>>> Without any parts of your patch?
>>
>> Yes. As you mentioned above, sival_int overlaps the most significant 32bit
>> of the sival_ptr, it seems that your patch is right if sival_ptr is less than
>> 32bit.
>
> I don't follow you here. sival_ptr is greater than 32-bit on a 64-bit
> kernel.
Sorry for confuse. I was considering if the pointer in sival_ptr is greater
than 32bit in 64bit application. But it seems that it is not relative to my
issue: We only talk about the 32bit application here.
>>> I think that's correct fix since in the SIGEV_THREAD mq_notify case, we
>>> would not deliver a signal as notification, so the sival_int value is
>>> irrelevant (it would be 0 for big-endian compat tasks because of the
>>> sigval_t union on 64-bit).
>>>
>>> Your patch would work as well but you have to change all the other
>>> architectures to use si_ptr when copying to a compat siginfo.
>>
>> Yeah, it seems that my patch is useful only if the sival_ptr is bigger
>> than 32bit. It need the similar changes with following catalin's patch
>> in the following 64bit architecture:
>>
>> x86: arch/x86/ia32/ia32_signal.c
>
> That's a little endian architecture and the use of ptr_to_compat() looks
> fine to me.
>
>> tile, s390: arch/xxx/kernel/compat_signal.c
>
> s390 uses si_int already, as in my proposed arm64 patch.
>
> tile seems to be bi-endian, though I couldn't see a Kconfig option, nor
> something defining __BIG_ENDIAN__ in headers or Makefile. I guess it's
> coming from the compiler directly. Anyway, on big endian tile, I we have
> the same issue as on big endian arm64.
>
>> parisc, sparc, mips: arch/xxx/kernel/signal32.c
>
> paris, sparc and mips all use si_int instead of si_ptr, so that's fine.
>
>> powerpc: arch/xxx/kernel/signal_32.c
>
> Same for powerpc, it uses si_int instead of si_ptr.
>
>> cc these maintainers for input.
>
> I think it's only tile that needs fixing for big endian, something like
> the arm64 patch below:
Agree. I was thinking if it is not very clear that app write to si_ptr in
userspace while kernel only read/write si_int.
regards
bamvor
>>>>> diff --git a/arch/arm64/kernel/signal32.c b/arch/arm64/kernel/signal32.c
>>>>> index e299de396e9b..32601939a3c8 100644
>>>>> --- a/arch/arm64/kernel/signal32.c
>>>>> +++ b/arch/arm64/kernel/signal32.c
>>>>> @@ -154,8 +154,7 @@ int copy_siginfo_to_user32(compat_siginfo_t __user *to, const siginfo_t *from)
>>>>> case __SI_TIMER:
>>>>> err |= __put_user(from->si_tid, &to->si_tid);
>>>>> err |= __put_user(from->si_overrun, &to->si_overrun);
>>>>> - err |= __put_user((compat_uptr_t)(unsigned long)from->si_ptr,
>>>>> - &to->si_ptr);
>>>>> + err |= __put_user(from->si_int, &to->si_int);
>>>>> break;
>>>>> case __SI_POLL:
>>>>> err |= __put_user(from->si_band, &to->si_band);
>>>>> @@ -184,7 +183,7 @@ int copy_siginfo_to_user32(compat_siginfo_t __user *to, const siginfo_t *from)
>>>>> case __SI_MESGQ: /* But this is */
>>>>> err |= __put_user(from->si_pid, &to->si_pid);
>>>>> err |= __put_user(from->si_uid, &to->si_uid);
>>>>> - err |= __put_user((compat_uptr_t)(unsigned long)from->si_ptr, &to->si_ptr);
>>>>> + err |= __put_user(from->si_int, &to->si_int);
>>>>> break;
>>>>> case __SI_SYS:
>>>>> err |= __put_user((compat_uptr_t)(unsigned long)
>
WARNING: multiple messages have this Message-ID (diff)
From: Bamvor Jian Zhang <bamvor.zhangjian@huawei.com>
To: Catalin Marinas <catalin.marinas@arm.com>
Cc: linux-arch@vger.kernel.org, heiko.carstens@de.ibm.com,
davem@davemloft.net, benh@kernel.crashing.org, deller@gmx.de,
hpa@zytor.com, Will Deacon <Will.Deacon@arm.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
ralf@linux-mips.org, jejb@parisc-linux.org, cmetcalf@ezchip.com,
"lizefan@huawei.com" <lizefan@huawei.com>,
paulus@samba.org, mpe@ellerman.id.au,
"dingtianhong@huawei.com" <dingtianhong@huawei.com>,
schwidefsky@de.ibm.com, tglx@linutronix.de, mingo@redhat.com,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] compat: Fix endian issue in union sigval
Date: Tue, 17 Feb 2015 15:15:15 +0800 [thread overview]
Message-ID: <54E2EA83.8080800@huawei.com> (raw)
Message-ID: <20150217071515.3GX34C1GEk3aFFBsWN4IDAmV4YOAbyWgDTMRKM90p6I@z> (raw)
In-Reply-To: <20150213104455.GA3508@e104818-lin.cambridge.arm.com>
On 2015/2/13 18:44, Catalin Marinas wrote:
> On Fri, Feb 13, 2015 at 04:00:43PM +0800, Bamvor Jian Zhang wrote:
>> On 2015/2/11 23:40, Catalin Marinas wrote:
>>> On Wed, Feb 11, 2015 at 07:22:08PM +0800, Bamvor Jian Zhang wrote:
>>>> On 2015/2/10 20:27, Catalin Marinas wrote:
>>>>> On Tue, Feb 10, 2015 at 10:10:11AM +0000, Zhang Jian(Bamvor) wrote:
>> ...
>>> The native sigval_t is also a union but on 64-bit big endian, the
>>> sival_int overlaps with the most significant 32-bit of the sival_ptr.
>>> So reading sival_int would always be 0. When the compat siginfo is
>>> copied to user, arm64 reads the native sival_ptr (si_ptr) and converts
>>> it to the compat one, getting the correct 32-bit value. However, other
>>> architectures access sival_int (si_int) instead which breaks with your
>>> get_compat_sigevent() changes.
>>>
>>>>> I think the correct fix is in the arm64 code:
>>>>
>>>> The following code could fix my issue.
>>>
>>> Without any parts of your patch?
>>
>> Yes. As you mentioned above, sival_int overlaps the most significant 32bit
>> of the sival_ptr, it seems that your patch is right if sival_ptr is less than
>> 32bit.
>
> I don't follow you here. sival_ptr is greater than 32-bit on a 64-bit
> kernel.
Sorry for confuse. I was considering if the pointer in sival_ptr is greater
than 32bit in 64bit application. But it seems that it is not relative to my
issue: We only talk about the 32bit application here.
>>> I think that's correct fix since in the SIGEV_THREAD mq_notify case, we
>>> would not deliver a signal as notification, so the sival_int value is
>>> irrelevant (it would be 0 for big-endian compat tasks because of the
>>> sigval_t union on 64-bit).
>>>
>>> Your patch would work as well but you have to change all the other
>>> architectures to use si_ptr when copying to a compat siginfo.
>>
>> Yeah, it seems that my patch is useful only if the sival_ptr is bigger
>> than 32bit. It need the similar changes with following catalin's patch
>> in the following 64bit architecture:
>>
>> x86: arch/x86/ia32/ia32_signal.c
>
> That's a little endian architecture and the use of ptr_to_compat() looks
> fine to me.
>
>> tile, s390: arch/xxx/kernel/compat_signal.c
>
> s390 uses si_int already, as in my proposed arm64 patch.
>
> tile seems to be bi-endian, though I couldn't see a Kconfig option, nor
> something defining __BIG_ENDIAN__ in headers or Makefile. I guess it's
> coming from the compiler directly. Anyway, on big endian tile, I we have
> the same issue as on big endian arm64.
>
>> parisc, sparc, mips: arch/xxx/kernel/signal32.c
>
> paris, sparc and mips all use si_int instead of si_ptr, so that's fine.
>
>> powerpc: arch/xxx/kernel/signal_32.c
>
> Same for powerpc, it uses si_int instead of si_ptr.
>
>> cc these maintainers for input.
>
> I think it's only tile that needs fixing for big endian, something like
> the arm64 patch below:
Agree. I was thinking if it is not very clear that app write to si_ptr in
userspace while kernel only read/write si_int.
regards
bamvor
>>>>> diff --git a/arch/arm64/kernel/signal32.c b/arch/arm64/kernel/signal32.c
>>>>> index e299de396e9b..32601939a3c8 100644
>>>>> --- a/arch/arm64/kernel/signal32.c
>>>>> +++ b/arch/arm64/kernel/signal32.c
>>>>> @@ -154,8 +154,7 @@ int copy_siginfo_to_user32(compat_siginfo_t __user *to, const siginfo_t *from)
>>>>> case __SI_TIMER:
>>>>> err |= __put_user(from->si_tid, &to->si_tid);
>>>>> err |= __put_user(from->si_overrun, &to->si_overrun);
>>>>> - err |= __put_user((compat_uptr_t)(unsigned long)from->si_ptr,
>>>>> - &to->si_ptr);
>>>>> + err |= __put_user(from->si_int, &to->si_int);
>>>>> break;
>>>>> case __SI_POLL:
>>>>> err |= __put_user(from->si_band, &to->si_band);
>>>>> @@ -184,7 +183,7 @@ int copy_siginfo_to_user32(compat_siginfo_t __user *to, const siginfo_t *from)
>>>>> case __SI_MESGQ: /* But this is */
>>>>> err |= __put_user(from->si_pid, &to->si_pid);
>>>>> err |= __put_user(from->si_uid, &to->si_uid);
>>>>> - err |= __put_user((compat_uptr_t)(unsigned long)from->si_ptr, &to->si_ptr);
>>>>> + err |= __put_user(from->si_int, &to->si_int);
>>>>> break;
>>>>> case __SI_SYS:
>>>>> err |= __put_user((compat_uptr_t)(unsigned long)
>
WARNING: multiple messages have this Message-ID (diff)
From: bamvor.zhangjian@huawei.com (Bamvor Jian Zhang)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] compat: Fix endian issue in union sigval
Date: Tue, 17 Feb 2015 15:15:15 +0800 [thread overview]
Message-ID: <54E2EA83.8080800@huawei.com> (raw)
In-Reply-To: <20150213104455.GA3508@e104818-lin.cambridge.arm.com>
On 2015/2/13 18:44, Catalin Marinas wrote:
> On Fri, Feb 13, 2015 at 04:00:43PM +0800, Bamvor Jian Zhang wrote:
>> On 2015/2/11 23:40, Catalin Marinas wrote:
>>> On Wed, Feb 11, 2015 at 07:22:08PM +0800, Bamvor Jian Zhang wrote:
>>>> On 2015/2/10 20:27, Catalin Marinas wrote:
>>>>> On Tue, Feb 10, 2015 at 10:10:11AM +0000, Zhang Jian(Bamvor) wrote:
>> ...
>>> The native sigval_t is also a union but on 64-bit big endian, the
>>> sival_int overlaps with the most significant 32-bit of the sival_ptr.
>>> So reading sival_int would always be 0. When the compat siginfo is
>>> copied to user, arm64 reads the native sival_ptr (si_ptr) and converts
>>> it to the compat one, getting the correct 32-bit value. However, other
>>> architectures access sival_int (si_int) instead which breaks with your
>>> get_compat_sigevent() changes.
>>>
>>>>> I think the correct fix is in the arm64 code:
>>>>
>>>> The following code could fix my issue.
>>>
>>> Without any parts of your patch?
>>
>> Yes. As you mentioned above, sival_int overlaps the most significant 32bit
>> of the sival_ptr, it seems that your patch is right if sival_ptr is less than
>> 32bit.
>
> I don't follow you here. sival_ptr is greater than 32-bit on a 64-bit
> kernel.
Sorry for confuse. I was considering if the pointer in sival_ptr is greater
than 32bit in 64bit application. But it seems that it is not relative to my
issue: We only talk about the 32bit application here.
>>> I think that's correct fix since in the SIGEV_THREAD mq_notify case, we
>>> would not deliver a signal as notification, so the sival_int value is
>>> irrelevant (it would be 0 for big-endian compat tasks because of the
>>> sigval_t union on 64-bit).
>>>
>>> Your patch would work as well but you have to change all the other
>>> architectures to use si_ptr when copying to a compat siginfo.
>>
>> Yeah, it seems that my patch is useful only if the sival_ptr is bigger
>> than 32bit. It need the similar changes with following catalin's patch
>> in the following 64bit architecture:
>>
>> x86: arch/x86/ia32/ia32_signal.c
>
> That's a little endian architecture and the use of ptr_to_compat() looks
> fine to me.
>
>> tile, s390: arch/xxx/kernel/compat_signal.c
>
> s390 uses si_int already, as in my proposed arm64 patch.
>
> tile seems to be bi-endian, though I couldn't see a Kconfig option, nor
> something defining __BIG_ENDIAN__ in headers or Makefile. I guess it's
> coming from the compiler directly. Anyway, on big endian tile, I we have
> the same issue as on big endian arm64.
>
>> parisc, sparc, mips: arch/xxx/kernel/signal32.c
>
> paris, sparc and mips all use si_int instead of si_ptr, so that's fine.
>
>> powerpc: arch/xxx/kernel/signal_32.c
>
> Same for powerpc, it uses si_int instead of si_ptr.
>
>> cc these maintainers for input.
>
> I think it's only tile that needs fixing for big endian, something like
> the arm64 patch below:
Agree. I was thinking if it is not very clear that app write to si_ptr in
userspace while kernel only read/write si_int.
regards
bamvor
>>>>> diff --git a/arch/arm64/kernel/signal32.c b/arch/arm64/kernel/signal32.c
>>>>> index e299de396e9b..32601939a3c8 100644
>>>>> --- a/arch/arm64/kernel/signal32.c
>>>>> +++ b/arch/arm64/kernel/signal32.c
>>>>> @@ -154,8 +154,7 @@ int copy_siginfo_to_user32(compat_siginfo_t __user *to, const siginfo_t *from)
>>>>> case __SI_TIMER:
>>>>> err |= __put_user(from->si_tid, &to->si_tid);
>>>>> err |= __put_user(from->si_overrun, &to->si_overrun);
>>>>> - err |= __put_user((compat_uptr_t)(unsigned long)from->si_ptr,
>>>>> - &to->si_ptr);
>>>>> + err |= __put_user(from->si_int, &to->si_int);
>>>>> break;
>>>>> case __SI_POLL:
>>>>> err |= __put_user(from->si_band, &to->si_band);
>>>>> @@ -184,7 +183,7 @@ int copy_siginfo_to_user32(compat_siginfo_t __user *to, const siginfo_t *from)
>>>>> case __SI_MESGQ: /* But this is */
>>>>> err |= __put_user(from->si_pid, &to->si_pid);
>>>>> err |= __put_user(from->si_uid, &to->si_uid);
>>>>> - err |= __put_user((compat_uptr_t)(unsigned long)from->si_ptr, &to->si_ptr);
>>>>> + err |= __put_user(from->si_int, &to->si_int);
>>>>> break;
>>>>> case __SI_SYS:
>>>>> err |= __put_user((compat_uptr_t)(unsigned long)
>
WARNING: multiple messages have this Message-ID (diff)
From: Bamvor Jian Zhang <bamvor.zhangjian@huawei.com>
To: Catalin Marinas <catalin.marinas@arm.com>
Cc: <linux-arch@vger.kernel.org>, <heiko.carstens@de.ibm.com>,
<davem@davemloft.net>, <benh@kernel.crashing.org>,
<deller@gmx.de>, <hpa@zytor.com>,
Will Deacon <Will.Deacon@arm.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
<ralf@linux-mips.org>, <jejb@parisc-linux.org>,
<cmetcalf@ezchip.com>, "lizefan@huawei.com" <lizefan@huawei.com>,
<paulus@samba.org>, <mpe@ellerman.id.au>,
"dingtianhong@huawei.com" <dingtianhong@huawei.com>,
<schwidefsky@de.ibm.com>, <tglx@linutronix.de>,
<mingo@redhat.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] compat: Fix endian issue in union sigval
Date: Tue, 17 Feb 2015 15:15:15 +0800 [thread overview]
Message-ID: <54E2EA83.8080800@huawei.com> (raw)
In-Reply-To: <20150213104455.GA3508@e104818-lin.cambridge.arm.com>
On 2015/2/13 18:44, Catalin Marinas wrote:
> On Fri, Feb 13, 2015 at 04:00:43PM +0800, Bamvor Jian Zhang wrote:
>> On 2015/2/11 23:40, Catalin Marinas wrote:
>>> On Wed, Feb 11, 2015 at 07:22:08PM +0800, Bamvor Jian Zhang wrote:
>>>> On 2015/2/10 20:27, Catalin Marinas wrote:
>>>>> On Tue, Feb 10, 2015 at 10:10:11AM +0000, Zhang Jian(Bamvor) wrote:
>> ...
>>> The native sigval_t is also a union but on 64-bit big endian, the
>>> sival_int overlaps with the most significant 32-bit of the sival_ptr.
>>> So reading sival_int would always be 0. When the compat siginfo is
>>> copied to user, arm64 reads the native sival_ptr (si_ptr) and converts
>>> it to the compat one, getting the correct 32-bit value. However, other
>>> architectures access sival_int (si_int) instead which breaks with your
>>> get_compat_sigevent() changes.
>>>
>>>>> I think the correct fix is in the arm64 code:
>>>>
>>>> The following code could fix my issue.
>>>
>>> Without any parts of your patch?
>>
>> Yes. As you mentioned above, sival_int overlaps the most significant 32bit
>> of the sival_ptr, it seems that your patch is right if sival_ptr is less than
>> 32bit.
>
> I don't follow you here. sival_ptr is greater than 32-bit on a 64-bit
> kernel.
Sorry for confuse. I was considering if the pointer in sival_ptr is greater
than 32bit in 64bit application. But it seems that it is not relative to my
issue: We only talk about the 32bit application here.
>>> I think that's correct fix since in the SIGEV_THREAD mq_notify case, we
>>> would not deliver a signal as notification, so the sival_int value is
>>> irrelevant (it would be 0 for big-endian compat tasks because of the
>>> sigval_t union on 64-bit).
>>>
>>> Your patch would work as well but you have to change all the other
>>> architectures to use si_ptr when copying to a compat siginfo.
>>
>> Yeah, it seems that my patch is useful only if the sival_ptr is bigger
>> than 32bit. It need the similar changes with following catalin's patch
>> in the following 64bit architecture:
>>
>> x86: arch/x86/ia32/ia32_signal.c
>
> That's a little endian architecture and the use of ptr_to_compat() looks
> fine to me.
>
>> tile, s390: arch/xxx/kernel/compat_signal.c
>
> s390 uses si_int already, as in my proposed arm64 patch.
>
> tile seems to be bi-endian, though I couldn't see a Kconfig option, nor
> something defining __BIG_ENDIAN__ in headers or Makefile. I guess it's
> coming from the compiler directly. Anyway, on big endian tile, I we have
> the same issue as on big endian arm64.
>
>> parisc, sparc, mips: arch/xxx/kernel/signal32.c
>
> paris, sparc and mips all use si_int instead of si_ptr, so that's fine.
>
>> powerpc: arch/xxx/kernel/signal_32.c
>
> Same for powerpc, it uses si_int instead of si_ptr.
>
>> cc these maintainers for input.
>
> I think it's only tile that needs fixing for big endian, something like
> the arm64 patch below:
Agree. I was thinking if it is not very clear that app write to si_ptr in
userspace while kernel only read/write si_int.
regards
bamvor
>>>>> diff --git a/arch/arm64/kernel/signal32.c b/arch/arm64/kernel/signal32.c
>>>>> index e299de396e9b..32601939a3c8 100644
>>>>> --- a/arch/arm64/kernel/signal32.c
>>>>> +++ b/arch/arm64/kernel/signal32.c
>>>>> @@ -154,8 +154,7 @@ int copy_siginfo_to_user32(compat_siginfo_t __user *to, const siginfo_t *from)
>>>>> case __SI_TIMER:
>>>>> err |= __put_user(from->si_tid, &to->si_tid);
>>>>> err |= __put_user(from->si_overrun, &to->si_overrun);
>>>>> - err |= __put_user((compat_uptr_t)(unsigned long)from->si_ptr,
>>>>> - &to->si_ptr);
>>>>> + err |= __put_user(from->si_int, &to->si_int);
>>>>> break;
>>>>> case __SI_POLL:
>>>>> err |= __put_user(from->si_band, &to->si_band);
>>>>> @@ -184,7 +183,7 @@ int copy_siginfo_to_user32(compat_siginfo_t __user *to, const siginfo_t *from)
>>>>> case __SI_MESGQ: /* But this is */
>>>>> err |= __put_user(from->si_pid, &to->si_pid);
>>>>> err |= __put_user(from->si_uid, &to->si_uid);
>>>>> - err |= __put_user((compat_uptr_t)(unsigned long)from->si_ptr, &to->si_ptr);
>>>>> + err |= __put_user(from->si_int, &to->si_int);
>>>>> break;
>>>>> case __SI_SYS:
>>>>> err |= __put_user((compat_uptr_t)(unsigned long)
>
next prev parent reply other threads:[~2015-02-17 7:15 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-10 10:10 [PATCH] compat: Fix endian issue in union sigval Zhang Jian(Bamvor)
2015-02-10 10:10 ` Zhang Jian(Bamvor)
2015-02-10 12:27 ` Catalin Marinas
2015-02-10 12:27 ` Catalin Marinas
2015-02-11 11:22 ` Bamvor Jian Zhang
2015-02-11 11:22 ` Bamvor Jian Zhang
2015-02-11 11:22 ` Bamvor Jian Zhang
2015-02-11 15:40 ` Catalin Marinas
2015-02-11 15:40 ` Catalin Marinas
2015-02-13 8:00 ` Bamvor Jian Zhang
2015-02-13 8:00 ` Bamvor Jian Zhang
2015-02-13 8:00 ` Bamvor Jian Zhang
2015-02-13 10:44 ` Catalin Marinas
2015-02-13 10:44 ` Catalin Marinas
2015-02-13 21:56 ` Chris Metcalf
2015-02-13 21:56 ` Chris Metcalf
2015-02-13 21:56 ` Chris Metcalf
2015-02-14 11:22 ` Catalin Marinas
2015-02-14 11:22 ` Catalin Marinas
2015-02-14 11:22 ` Catalin Marinas
2015-02-17 6:42 ` Bamvor Jian Zhang
2015-02-17 6:42 ` Bamvor Jian Zhang
2015-02-17 6:42 ` Bamvor Jian Zhang
2015-02-21 4:05 ` Chris Metcalf
2015-02-21 4:05 ` Chris Metcalf
2015-02-21 4:05 ` Chris Metcalf
2015-02-21 4:05 ` Chris Metcalf
2015-02-24 21:54 ` Chris Metcalf
2015-02-24 21:54 ` Chris Metcalf
2015-02-24 21:54 ` Chris Metcalf
2015-02-24 21:54 ` Chris Metcalf
2015-02-25 10:37 ` Catalin Marinas
2015-02-25 10:37 ` Catalin Marinas
2015-03-16 19:04 ` [PATCH] tile: use si_int instead of si_ptr for compat_siginfo Chris Metcalf
2015-03-16 19:04 ` Chris Metcalf
2015-03-16 19:04 ` Chris Metcalf
2015-03-23 12:02 ` Catalin Marinas
2015-03-23 12:02 ` Catalin Marinas
2015-03-24 20:51 ` Chris Metcalf
2015-03-24 20:51 ` Chris Metcalf
2015-03-24 20:51 ` Chris Metcalf
2015-04-17 16:56 ` Chris Metcalf
2015-04-17 16:56 ` Chris Metcalf
2015-04-17 16:56 ` Chris Metcalf
2015-02-17 7:15 ` Bamvor Jian Zhang [this message]
2015-02-17 7:15 ` [PATCH] compat: Fix endian issue in union sigval Bamvor Jian Zhang
2015-02-17 7:15 ` Bamvor Jian Zhang
2015-02-17 7:15 ` Bamvor Jian Zhang
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=54E2EA83.8080800@huawei.com \
--to=bamvor.zhangjian@huawei.com \
--cc=Will.Deacon@arm.com \
--cc=benh@kernel.crashing.org \
--cc=catalin.marinas@arm.com \
--cc=cmetcalf@ezchip.com \
--cc=davem@davemloft.net \
--cc=deller@gmx.de \
--cc=dingtianhong@huawei.com \
--cc=heiko.carstens@de.ibm.com \
--cc=hpa@zytor.com \
--cc=jejb@parisc-linux.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lizefan@huawei.com \
--cc=mingo@redhat.com \
--cc=mpe@ellerman.id.au \
--cc=paulus@samba.org \
--cc=ralf@linux-mips.org \
--cc=schwidefsky@de.ibm.com \
--cc=tglx@linutronix.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.