Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1457902 > unrolled thread
| Started by | Valdis.Kletnieks@vt.edu |
|---|---|
| First post | 2016-08-08 18:40 +0200 |
| Last post | 2016-08-09 05:30 +0200 |
| Articles | 6 — 3 participants |
Back to article view | Back to linux.kernel
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
Re: [lkp] [fs] 45ec18d5c7: BUG: KASAN: user-memory-access on address 00007f90291c7ec0 Valdis.Kletnieks@vt.edu - 2016-08-08 18:40 +0200
Re: [lkp] [fs] 45ec18d5c7: BUG: KASAN: user-memory-access on address 00007f90291c7ec0 Al Viro <viro@ZenIV.linux.org.uk> - 2016-08-09 03:30 +0200
Re: [lkp] [fs] 45ec18d5c7: BUG: KASAN: user-memory-access on address 00007f90291c7ec0 Ye Xiaolong <xiaolong.ye@intel.com> - 2016-08-09 05:30 +0200
Re: [lkp] [fs] 45ec18d5c7: BUG: KASAN: user-memory-access on address 00007f90291c7ec0 Ye Xiaolong <xiaolong.ye@intel.com> - 2016-08-09 03:30 +0200
Re: [lkp] [fs] 45ec18d5c7: BUG: KASAN: user-memory-access on address 00007f90291c7ec0 Valdis.Kletnieks@vt.edu - 2016-08-09 04:20 +0200
Re: [lkp] [fs] 45ec18d5c7: BUG: KASAN: user-memory-access on address 00007f90291c7ec0 Ye Xiaolong <xiaolong.ye@intel.com> - 2016-08-09 05:30 +0200
| From | Valdis.Kletnieks@vt.edu |
|---|---|
| Date | 2016-08-08 18:40 +0200 |
| Subject | Re: [lkp] [fs] 45ec18d5c7: BUG: KASAN: user-memory-access on address 00007f90291c7ec0 |
| Message-ID | <s3VKN-3JN-9@gated-at.bofh.it> |
[Multipart message — attachments visible in raw view] — view raw
On Sun, 07 Aug 2016 22:02:42 +0800, kernel test robot said:
> FYI, we noticed the following commit:
>
> https://github.com/0day-ci/linux
> Nicholas-Krause/fs-Fix-kmemleak-leak-warning-in-getname_flags-about-working-on-unitialized-memory/20160804-055054
> commit 45ec18d5c713bccb9807782f0dca29b92ba99784 ("fs:Fix kmemleak leak warning in getname_flags about working on unitialized memory")
The real question here is why the 0day system was even bothering to try
compiling and booting a patch from somebody who has a long record of failing
to do so with patches before submission. Actually looking at the patch
in question shows that little or no thought or testing was done (hint:
look at it, and wonder in amazement why there's a dump_stack() call where
it is....)
In other words - how did this patch get into a tree that 0day listens to?
[toc] | [next] | [standalone]
| From | Al Viro <viro@ZenIV.linux.org.uk> |
|---|---|
| Date | 2016-08-09 03:30 +0200 |
| Subject | Re: [lkp] [fs] 45ec18d5c7: BUG: KASAN: user-memory-access on address 00007f90291c7ec0 |
| Message-ID | <s441H-OA-3@gated-at.bofh.it> |
| In reply to | #1457902 |
On Tue, Aug 09, 2016 at 09:17:58AM +0800, Ye Xiaolong wrote:
> On 08/08, Valdis.Kletnieks@vt.edu wrote:
> >On Sun, 07 Aug 2016 22:02:42 +0800, kernel test robot said:
> >
> >> FYI, we noticed the following commit:
> >>
> >> https://github.com/0day-ci/linux
> >> Nicholas-Krause/fs-Fix-kmemleak-leak-warning-in-getname_flags-about-working-on-unitialized-memory/20160804-055054
> >> commit 45ec18d5c713bccb9807782f0dca29b92ba99784 ("fs:Fix kmemleak leak warning in getname_flags about working on unitialized memory")
> >
> >The real question here is why the 0day system was even bothering to try
> >compiling and booting a patch from somebody who has a long record of failing
> >to do so with patches before submission. Actually looking at the patch
> >in question shows that little or no thought or testing was done (hint:
> >look at it, and wonder in amazement why there's a dump_stack() call where
> >it is....)
> >
> >In other words - how did this patch get into a tree that 0day listens to?
>
> 0Day has a service to automatically capture every patchset sent to LKML, and convert
> email patchset to git branches by applying them on top of different
> trees heuristically.
*raised eyebrows*
I really hope they are doing both builds and testing in a heavily isolated
environments, then. Because you've just described an attack vector it's
vulnerable to...
[toc] | [prev] | [next] | [standalone]
| From | Ye Xiaolong <xiaolong.ye@intel.com> |
|---|---|
| Date | 2016-08-09 05:30 +0200 |
| Subject | Re: [lkp] [fs] 45ec18d5c7: BUG: KASAN: user-memory-access on address 00007f90291c7ec0 |
| Message-ID | <s45TP-1Zf-7@gated-at.bofh.it> |
| In reply to | #1458361 |
On 08/09, Al Viro wrote:
>On Tue, Aug 09, 2016 at 09:17:58AM +0800, Ye Xiaolong wrote:
>> On 08/08, Valdis.Kletnieks@vt.edu wrote:
>> >On Sun, 07 Aug 2016 22:02:42 +0800, kernel test robot said:
>> >
>> >> FYI, we noticed the following commit:
>> >>
>> >> https://github.com/0day-ci/linux
>> >> Nicholas-Krause/fs-Fix-kmemleak-leak-warning-in-getname_flags-about-working-on-unitialized-memory/20160804-055054
>> >> commit 45ec18d5c713bccb9807782f0dca29b92ba99784 ("fs:Fix kmemleak leak warning in getname_flags about working on unitialized memory")
>> >
>> >The real question here is why the 0day system was even bothering to try
>> >compiling and booting a patch from somebody who has a long record of failing
>> >to do so with patches before submission. Actually looking at the patch
>> >in question shows that little or no thought or testing was done (hint:
>> >look at it, and wonder in amazement why there's a dump_stack() call where
>> >it is....)
>> >
>> >In other words - how did this patch get into a tree that 0day listens to?
>>
>> 0Day has a service to automatically capture every patchset sent to LKML, and convert
>> email patchset to git branches by applying them on top of different
>> trees heuristically.
>
>*raised eyebrows*
>
>I really hope they are doing both builds and testing in a heavily isolated
>environments, then. Because you've just described an attack vector it's
>vulnerable to...
Yes, they are doing test in a heavily isolated environments with chroot,
no suid and isolated network.
[toc] | [prev] | [next] | [standalone]
| From | Ye Xiaolong <xiaolong.ye@intel.com> |
|---|---|
| Date | 2016-08-09 03:30 +0200 |
| Subject | Re: [lkp] [fs] 45ec18d5c7: BUG: KASAN: user-memory-access on address 00007f90291c7ec0 |
| Message-ID | <s441H-OA-5@gated-at.bofh.it> |
| In reply to | #1457902 |
On 08/08, Valdis.Kletnieks@vt.edu wrote:
>On Sun, 07 Aug 2016 22:02:42 +0800, kernel test robot said:
>
>> FYI, we noticed the following commit:
>>
>> https://github.com/0day-ci/linux
>> Nicholas-Krause/fs-Fix-kmemleak-leak-warning-in-getname_flags-about-working-on-unitialized-memory/20160804-055054
>> commit 45ec18d5c713bccb9807782f0dca29b92ba99784 ("fs:Fix kmemleak leak warning in getname_flags about working on unitialized memory")
>
>The real question here is why the 0day system was even bothering to try
>compiling and booting a patch from somebody who has a long record of failing
>to do so with patches before submission. Actually looking at the patch
>in question shows that little or no thought or testing was done (hint:
>look at it, and wonder in amazement why there's a dump_stack() call where
>it is....)
>
>In other words - how did this patch get into a tree that 0day listens to?
0Day has a service to automatically capture every patchset sent to LKML, and convert
email patchset to git branches by applying them on top of different
trees heuristically.
[toc] | [prev] | [next] | [standalone]
| From | Valdis.Kletnieks@vt.edu |
|---|---|
| Date | 2016-08-09 04:20 +0200 |
| Message-ID | <s44O5-1op-1@gated-at.bofh.it> |
| In reply to | #1458363 |
[Multipart message — attachments visible in raw view] — view raw
On Tue, 09 Aug 2016 09:17:58 +0800, Ye Xiaolong said: > On 08/08, Valdis.Kletnieks@vt.edu wrote: > > In other words - how did this patch get into a tree that 0day listens to? > > 0Day has a service to automatically capture every patchset sent to LKML Something's wrong then. Nick has proven to be such a maintainer time-sink that he's not allowed to post to LKML - or any other list on vger.kernel.org. So how did he get past that and get 0day to see it?
[toc] | [prev] | [next] | [standalone]
| From | Ye Xiaolong <xiaolong.ye@intel.com> |
|---|---|
| Date | 2016-08-09 05:30 +0200 |
| Subject | Re: [lkp] [fs] 45ec18d5c7: BUG: KASAN: user-memory-access on address 00007f90291c7ec0 |
| Message-ID | <s45TP-1Zf-1@gated-at.bofh.it> |
| In reply to | #1458370 |
On 08/08, Valdis.Kletnieks@vt.edu wrote: >On Tue, 09 Aug 2016 09:17:58 +0800, Ye Xiaolong said: >> On 08/08, Valdis.Kletnieks@vt.edu wrote: >> > In other words - how did this patch get into a tree that 0day listens to? >> >> 0Day has a service to automatically capture every patchset sent to LKML > >Something's wrong then. Nick has proven to be such a maintainer time-sink >that he's not allowed to post to LKML - or any other list on vger.kernel.org. > >So how did he get past that and get 0day to see it? We'll add a blacklist for it, Thanks.
[toc] | [prev] | [standalone]
Back to top | Article view | linux.kernel
csiph-web