On Thu, Dec 28, 2017 at 5:18 PM, Andrey Ryabinin
wrote:
>
>
> On 12/28/2017 02:54 PM, Dmitry Vyukov wrote:
>> On Thu, Dec 28, 2017 at 12:51 PM, Thomas Gleixner wrote:
>>> On Wed, 27 Dec 2017, Dmitry Vyukov wrote:
On Wed, Dec 27, 2017 at 7:05 PM,
On Thu, Dec 28, 2017 at 5:18 PM, Andrey Ryabinin
wrote:
>
>
> On 12/28/2017 02:54 PM, Dmitry Vyukov wrote:
>> On Thu, Dec 28, 2017 at 12:51 PM, Thomas Gleixner wrote:
>>> On Wed, 27 Dec 2017, Dmitry Vyukov wrote:
On Wed, Dec 27, 2017 at 7:05 PM, Thomas Gleixner
wrote:
> So this
On 12/28/2017 02:54 PM, Dmitry Vyukov wrote:
> On Thu, Dec 28, 2017 at 12:51 PM, Thomas Gleixner wrote:
>> On Wed, 27 Dec 2017, Dmitry Vyukov wrote:
>>> On Wed, Dec 27, 2017 at 7:05 PM, Thomas Gleixner wrote:
So this dies simply because
On 12/28/2017 02:54 PM, Dmitry Vyukov wrote:
> On Thu, Dec 28, 2017 at 12:51 PM, Thomas Gleixner wrote:
>> On Wed, 27 Dec 2017, Dmitry Vyukov wrote:
>>> On Wed, Dec 27, 2017 at 7:05 PM, Thomas Gleixner wrote:
So this dies simply because kasan_populate_shadow() runs out of memory and
On 12/27/2017 09:12 PM, Dmitry Vyukov wrote:
>>
>> Not really a problem caused by the patch above, it's merily exposing a code
>> path which relies blindly on "enough memory available" assumptions.
>>
>> Throwing more memory at the VM makes the problem go away...
>
> Hi Thomas,
>
> We just need
On 12/27/2017 09:12 PM, Dmitry Vyukov wrote:
>>
>> Not really a problem caused by the patch above, it's merily exposing a code
>> path which relies blindly on "enough memory available" assumptions.
>>
>> Throwing more memory at the VM makes the problem go away...
>
> Hi Thomas,
>
> We just need
On Thu, Dec 28, 2017 at 12:51 PM, Thomas Gleixner wrote:
> On Wed, 27 Dec 2017, Dmitry Vyukov wrote:
>> On Wed, Dec 27, 2017 at 7:05 PM, Thomas Gleixner wrote:
>> > So this dies simply because kasan_populate_shadow() runs out of memory and
>> > has no
On Thu, Dec 28, 2017 at 12:51 PM, Thomas Gleixner wrote:
> On Wed, 27 Dec 2017, Dmitry Vyukov wrote:
>> On Wed, Dec 27, 2017 at 7:05 PM, Thomas Gleixner wrote:
>> > So this dies simply because kasan_populate_shadow() runs out of memory and
>> > has no sanity check whatsoever.
>> >
>> > static
On Wed, 27 Dec 2017, Dmitry Vyukov wrote:
> On Wed, Dec 27, 2017 at 7:05 PM, Thomas Gleixner wrote:
> > So this dies simply because kasan_populate_shadow() runs out of memory and
> > has no sanity check whatsoever.
> >
> > static __init void *early_alloc(size_t size, int nid)
On Wed, 27 Dec 2017, Dmitry Vyukov wrote:
> On Wed, Dec 27, 2017 at 7:05 PM, Thomas Gleixner wrote:
> > So this dies simply because kasan_populate_shadow() runs out of memory and
> > has no sanity check whatsoever.
> >
> > static __init void *early_alloc(size_t size, int nid)
> > {
> >
On Wed, Dec 27, 2017 at 7:05 PM, Thomas Gleixner wrote:
> On Tue, 26 Dec 2017, kernel test robot wrote:
>
>>
>> FYI, we noticed the following commit (built with gcc-6):
>>
>> commit: 10043e02db7f8a4161f76434931051e7d797a5f6 ("x86/cpu_entry_area: Add
>> debugstore entries to
On Wed, Dec 27, 2017 at 7:05 PM, Thomas Gleixner wrote:
> On Tue, 26 Dec 2017, kernel test robot wrote:
>
>>
>> FYI, we noticed the following commit (built with gcc-6):
>>
>> commit: 10043e02db7f8a4161f76434931051e7d797a5f6 ("x86/cpu_entry_area: Add
>> debugstore entries to cpu_entry_area")
>>
On Tue, 26 Dec 2017, kernel test robot wrote:
>
> FYI, we noticed the following commit (built with gcc-6):
>
> commit: 10043e02db7f8a4161f76434931051e7d797a5f6 ("x86/cpu_entry_area: Add
> debugstore entries to cpu_entry_area")
> https://git.kernel.org/cgit/linux/kernel/git/tip/tip.git
On Tue, 26 Dec 2017, kernel test robot wrote:
>
> FYI, we noticed the following commit (built with gcc-6):
>
> commit: 10043e02db7f8a4161f76434931051e7d797a5f6 ("x86/cpu_entry_area: Add
> debugstore entries to cpu_entry_area")
> https://git.kernel.org/cgit/linux/kernel/git/tip/tip.git
14 matches
Mail list logo