Re: [RFC PATCH] driver: base: memory: Maintain correct mem->end_section_nr when memory block is partially filled

2015-08-17 Thread Greg KH
On Mon, Aug 17, 2015 at 11:56:53AM +0530, Bharata B Rao wrote: > On Fri, Aug 14, 2015 at 10:27:53AM -0500, Nathan Fontenot wrote: > > On 08/13/2015 04:17 AM, Bharata B Rao wrote: > > > Last section of memory block is always initialized to > > > > > > mem->start_section_nr + sections_per_block - 1

Re: [RFC PATCH] driver: base: memory: Maintain correct mem->end_section_nr when memory block is partially filled

2015-08-17 Thread Bharata B Rao
On Fri, Aug 14, 2015 at 10:27:53AM -0500, Nathan Fontenot wrote: > On 08/13/2015 04:17 AM, Bharata B Rao wrote: > > Last section of memory block is always initialized to > > > > mem->start_section_nr + sections_per_block - 1 > > > > which will not be true for a section that doesn't contain

Re: [RFC PATCH] driver: base: memory: Maintain correct mem-end_section_nr when memory block is partially filled

2015-08-17 Thread Greg KH
On Mon, Aug 17, 2015 at 11:56:53AM +0530, Bharata B Rao wrote: On Fri, Aug 14, 2015 at 10:27:53AM -0500, Nathan Fontenot wrote: On 08/13/2015 04:17 AM, Bharata B Rao wrote: Last section of memory block is always initialized to mem-start_section_nr + sections_per_block - 1 which

Re: [RFC PATCH] driver: base: memory: Maintain correct mem-end_section_nr when memory block is partially filled

2015-08-17 Thread Bharata B Rao
On Fri, Aug 14, 2015 at 10:27:53AM -0500, Nathan Fontenot wrote: On 08/13/2015 04:17 AM, Bharata B Rao wrote: Last section of memory block is always initialized to mem-start_section_nr + sections_per_block - 1 which will not be true for a section that doesn't contain

Re: [RFC PATCH] driver: base: memory: Maintain correct mem->end_section_nr when memory block is partially filled

2015-08-14 Thread Nathan Fontenot
On 08/13/2015 04:17 AM, Bharata B Rao wrote: > Last section of memory block is always initialized to > > mem->start_section_nr + sections_per_block - 1 > > which will not be true for a section that doesn't contain sections_per_block > sections due to the memory size specified. This causes the

Re: [RFC PATCH] driver: base: memory: Maintain correct mem-end_section_nr when memory block is partially filled

2015-08-14 Thread Nathan Fontenot
On 08/13/2015 04:17 AM, Bharata B Rao wrote: Last section of memory block is always initialized to mem-start_section_nr + sections_per_block - 1 which will not be true for a section that doesn't contain sections_per_block sections due to the memory size specified. This causes the following

[RFC PATCH] driver: base: memory: Maintain correct mem->end_section_nr when memory block is partially filled

2015-08-13 Thread Bharata B Rao
Last section of memory block is always initialized to mem->start_section_nr + sections_per_block - 1 which will not be true for a section that doesn't contain sections_per_block sections due to the memory size specified. This causes the following kernel crash when memory blocks under a node are

[RFC PATCH] driver: base: memory: Maintain correct mem-end_section_nr when memory block is partially filled

2015-08-13 Thread Bharata B Rao
Last section of memory block is always initialized to mem-start_section_nr + sections_per_block - 1 which will not be true for a section that doesn't contain sections_per_block sections due to the memory size specified. This causes the following kernel crash when memory blocks under a node are