Re: Fwd: Re: Section 4 No. 9,10 Failed was occurred by IPv6 Ready Logo Conformance Test

2016-04-19 Thread Yuki Machida
Hi Hagen, On 2016年04月15日 22:59, Hagen Paul Pfeifer wrote: On April 15, 2016 at 10:47 AM Yuki Machida <machida.y...@jp.fujitsu.com> wrote: commit 9d289715eb5c252ae15bd547cb252ca547a3c4f2 Author: Hagen Paul Pfeifer <ha...@jauu.net> Date: Thu Jan 15 22:34:25 2015 +0100 ipv6:

Fwd: Re: Section 4 No. 9,10 Failed was occurred by IPv6 Ready Logo Conformance Test

2016-04-15 Thread Yuki Machida
Hi, I doesn't report this issue to contributers of commit 9d28971 yet. sorry. I resend my information. Regards, Yuki Machida Forwarded Message Subject: Re: Section 4 No. 9,10 Failed was occurred by IPv6 Ready Logo Conformance Test Date: Mon, 4 Apr 2016 15:43:47 +0900 From

Re: Backport Security Fix for CVE-2015-8787 to v4.1

2016-04-10 Thread Yuki Machida
Hi Pablo, On 2016年04月11日 13:42, Yuki Machida wrote: Hi Pablo, On 2016年04月07日 23:46, Pablo Neira Ayuso wrote: On Thu, Apr 07, 2016 at 03:40:30PM +0900, Yuki Machida wrote: Hi David, I conformed that a patch of CVE-2015-8787 not applied at v4.1.21. Could you please apply a patch for 4.1

Re: Backport Security Fix for CVE-2015-8787 to v4.1

2016-04-10 Thread Yuki Machida
Hi Pablo, On 2016年04月07日 23:46, Pablo Neira Ayuso wrote: On Thu, Apr 07, 2016 at 03:40:30PM +0900, Yuki Machida wrote: Hi David, I conformed that a patch of CVE-2015-8787 not applied at v4.1.21. Could you please apply a patch for 4.1-stable ? CVE-2015-8787 Upstream commit

Backport Security Fix for CVE-2015-8787 to v4.1

2016-04-07 Thread Yuki Machida
Hi David, I conformed that a patch of CVE-2015-8787 not applied at v4.1.21. Could you please apply a patch for 4.1-stable ? CVE-2015-8787 Upstream commit 94f9cd81436c85d8c3a318ba92e236ede73752fc Regards, Yuki Machida

Re: Section 4 No. 9,10 Failed was occurred by IPv6 Ready Logo Conformance Test

2016-04-04 Thread Yuki Machida
Hi Roy, On 2016年04月01日 17:00, Yuki Machida wrote: > Hi Roy, > > Thank you for your advice. > I am very glad. > > Futher comment below. > > On 2016年04月01日 16:43, Rongqing Li wrote: >> >> >> On 2016年04月01日 15:31, Yuki Machida wrote: >>> Hi al

Re: Section 4 No. 9,10 Failed was occurred by IPv6 Ready Logo Conformance Test

2016-04-01 Thread Yuki Machida
Hi Roy, Thank you for your advice. I am very glad. Futher comment below. On 2016年04月01日 16:43, Rongqing Li wrote: > > > On 2016年04月01日 15:31, Yuki Machida wrote: >> Hi all, >> >> I tested 4.6-rc1 by IPv6 Ready Logo Core Conformance Test. >> 4.6-rc1 has some F

Section 4 No. 9,10 Failed was occurred by IPv6 Ready Logo Conformance Test

2016-04-01 Thread Yuki Machida
: V6LC_5_0_0 Target Device : Intel D510MO (Atom D510) List of FAILs Section 4: RFC 1981 - Path MTU Discovery for IPv6 - Test v6LC.4.1.6: Receiving MTU Below IPv6 Minimum Link MTU - No. 9 Part A: MTU equal to 56 - No.10 Part B: MTU equal to 1279 Regards, Yuki Machida

Re: Reboot Failed was occurred after v4.4-rc1 during IPv6 Ready Logo Conformance Test

2016-03-31 Thread Yuki Machida
On 2016年03月31日 16:09, Yuki Machida wrote: > Hi all, > > Reboot Failed was occurred at Linux Kernel after v4.4-rc1 during IPv6 Ready > Logo Conformance Test. > Not Fix a bug in v4.5-rc7 yet. > I will conform that it fix a bug in v4.6-rc1. I conform that it was not occurr

Reboot Failed was occurred after v4.4-rc1 during IPv6 Ready Logo Conformance Test

2016-03-31 Thread Yuki Machida
D510MO (Atom D510) I conform that random testcases are failed. (e.g. No.5, No.130, No.131, No.134, No.167 and No.168) Regards, Yuki Machida

Re: Hung up was occurred after v4.4-rc1 during IPv6 Ready Logo Conformance Test

2016-03-19 Thread Yuki Machida
Hi Martin, Thank you for your reply. Sorry for the delay. On 2016年03月10日 15:39, Martin KaFai Lau wrote: On Thu, Mar 10, 2016 at 01:21:05PM +0900, Yuki Machida wrote: Hi all, Hung up was occurred at Linux Kernel after v4.4-rc1 during IPv6 Ready Logo Conformance Test. Not Fix a bug in v4.5

Hung up was occurred after v4.4-rc1 during IPv6 Ready Logo Conformance Test

2016-03-09 Thread Yuki Machida
on Intel D510MO (Atom D510). It is using userland build with yocto project. Test Environment Test Specification : 4.0.6 Tool Version: REL_3_3_2 Test Program Version: V6LC_5_0_0 Target Device : Intel D510MO (Atom D510) Regards, Yuki Machida

Re: [PATCH stable v2 1/1] net/ipv6: add sysctl option accept_ra_min_hop_limit

2016-02-19 Thread Yuki Machida
ping? thanks. On 2016年02月03日 10:56, Yuki Machida wrote: > Please apply the following patch to v4.1.x. > > By commit 6fd99094de2b ("ipv6: Don't reduce hop limit for an interface") > that have been added in the 4.0-rc7, it no longer comply with RFC4861. > This problem has

Re: [PATCH 1/1] net/ipv6: add sysctl option accept_ra_min_hop_limit

2016-02-02 Thread Yuki Machida
Hi Yoshifuji-san. On 2016年01月18日 17:33, YOSHIFUJI Hideaki wrote: > Hi, > > Yuki Machida wrote: >> Hi, Yoshifuji-san >> >> It is currently under investigation. >> It takes still time. >> >> Futher comment below. >> >> On 2016年0

[PATCH stable v2 1/1] net/ipv6: add sysctl option accept_ra_min_hop_limit

2016-02-02 Thread Yuki Machida
Please apply the following patch to v4.1.x. By commit 6fd99094de2b ("ipv6: Don't reduce hop limit for an interface") that have been added in the 4.0-rc7, it no longer comply with RFC4861. This problem has been fixed in the commit 8013d1d7eafb ("net/ipv6: add sysctl option

Re: [PATCH 4.1] [media] media/vivid-osd: fix info leak in ioctl

2016-01-27 Thread Yuki Machida
Hi Greg, On 2016年01月26日 02:18, Greg KH wrote: On Mon, Jan 25, 2016 at 07:42:18PM +0900, Yuki Machida wrote: commit eda98796aff0d9bf41094b06811f5def3b4c333c upstream. The vivid_fb_ioctl() code fails to initialize the 16 _reserved bytes of struct fb_vblank after the ->hcount member.

Re: [PATCH 4.1] [media] media/vivid-osd: fix info leak in ioctl

2016-01-25 Thread Yuki Machida
It has sent to the wrong Mainling List. sorry. On 2016年01月25日 19:42, Yuki Machida wrote: commit eda98796aff0d9bf41094b06811f5def3b4c333c upstream. The vivid_fb_ioctl() code fails to initialize the 16 _reserved bytes of struct fb_vblank after the ->hcount member. Add an explicit memse

[PATCH 4.1] [media] media/vivid-osd: fix info leak in ioctl

2016-01-25 Thread Yuki Machida
off-by: Salva Peiró <speir...@gmail.com> Signed-off-by: Hans Verkuil <hans.verk...@cisco.com> Signed-off-by: Mauro Carvalho Chehab <mche...@osg.samsung.com> Signed-off-by: Yuki Machida <machida.y...@jp.fujitsu.com> --- drivers/media/platform/vivid/vivid-osd.c | 1 + 1 file ch

Re: [PATCH 1/1] net/ipv6: add sysctl option accept_ra_min_hop_limit

2016-01-05 Thread Yuki Machida
Hi, Yoshifuji-san. Thanks for your kindly check. I will correct it in Patch v2. Best Regards, Yuki Machida On 2016年01月05日 19:17, YOSHIFUJI Hideaki wrote: > Hi, Machida-san. > > Yuki Machida wrote: >> Please apply the following patch to v4.1.x. >> >> By ommit 6fd990

[PATCH 1/1] net/ipv6: add sysctl option accept_ra_min_hop_limit

2016-01-04 Thread Yuki Machida
Please apply the following patch to v4.1.x. By ommit 6fd99094de2b ("ipv6: Don't reduce hop limit for an interface") that have been added in the 4.0-rc7, it no longer comply with RFC4861. This problem has been fixed in the commit 8013d1d7eafb ("net/ipv6: add sysctl option