Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1457902
| From | Valdis.Kletnieks@vt.edu |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [lkp] [fs] 45ec18d5c7: BUG: KASAN: user-memory-access on address 00007f90291c7ec0 |
| Date | 2016-08-08 18:40 +0200 |
| Message-ID | <s3VKN-3JN-9@gated-at.bofh.it> (permalink) |
| References | <s3wW5-4OI-11@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
[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?
Back to linux.kernel | Previous | Next — Next in thread | Find similar | Unroll thread
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
csiph-web