From: Gavin Shan <shangw@linux.vnet.ibm.com>
To: Michal Hocko <mhocko@suse.cz>
Cc: Gavin Shan <shangw@linux.vnet.ibm.com>,
linux-mm@kvack.org, rientjes@google.com, hannes@cmpxchg.org,
akpm@linux-foundation.org
Subject: Re: [PATCH 1/5] mm/sparse: check size of struct mm_section
Date: Wed, 27 Jun 2012 11:01:31 +0800 [thread overview]
Message-ID: <20120627030130.GA14213@shangw> (raw)
In-Reply-To: <20120626175704.GA17803@tiehlicka.suse.cz>
>> >> >
>> >>
>> >> I should have clarified that more clear :-)
>> >>
>> >> >> >
>> >> >> >Why? The memory is continuous, right?
>> >> >>
>> >> >> Yes, the memory is conginous and the capacity of specific entry
>> >> >> in mem_section[NR_SECTION_ROOTS] has been defined as follows:
>> >> >>
>> >> >>
>> >> >> #define SECTIONS_PER_ROOT (PAGE_SIZE / sizeof (struct mem_section))
>> >> >>
>> >> >> Also, the memory is prone to be allocated from bootmem by function
>> >> >> alloc_bootmem_node(), which has PAGE_SIZE alignment. So I think it's
>> >> >> reasonable to introduce the extra check here from my personal view :-)
>> >> >
>> >> >No it is not necessary because we will never cross the page boundary
>> >> >because (SECTIONS_PER_ROOT uses an int division)
>> >>
>> >> Current situation is that we don't cross the page foundary, but somebody
>> >> else might change the data struct (struct mem_section) in future.
>> >
>> >No, this is safe even if the structure size changes (unless it is bigger
>> >than PAGE_SIZE).
>>
>> Yeah, but it can't fully utilize the allocated memory chunk if the size of
>> the struct isn't aligned well.
>
>And you think that this is justification is sufficient to fail
>compilation? I don't think so...
>
Yeah, it's not reasonable to breat the compilation. So I'm not sure if
linux already had one macro to do warning for the case?
Thanks,
Gavin
>>
>> Let me drop it in next revision :-)
>>
>> Thanks,
>> Gavin
>
>--
>Michal Hocko
>SUSE Labs
>SUSE LINUX s.r.o.
>Lihovarska 1060/12
>190 00 Praha 9
>Czech Republic
>
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
prev parent reply other threads:[~2012-06-27 3:02 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-23 15:52 [PATCH 1/5] mm/sparse: check size of struct mm_section Gavin Shan
2012-06-23 15:52 ` [PATCH 2/5] mm/sparse: optimize sparse_index_alloc Gavin Shan
2012-06-25 15:30 ` Michal Hocko
2012-06-26 6:07 ` Gavin Shan
2012-06-26 7:04 ` Michal Hocko
2012-06-26 7:13 ` Gavin Shan
2012-06-23 15:52 ` [PATCH 3/5] mm/sparse: fix possible memory leak Gavin Shan
2012-06-25 15:48 ` Michal Hocko
2012-06-26 6:11 ` Gavin Shan
2012-06-26 7:14 ` Michal Hocko
2012-06-26 7:17 ` Gavin Shan
2012-06-23 15:52 ` [PATCH 4/5] mm/sparse: more check on mem_section number Gavin Shan
2012-06-26 16:15 ` Dave Hansen
2012-06-27 0:29 ` Gavin Shan
2012-06-23 15:52 ` [PATCH 5/5] mm/sparse: return 0 if root mem_section exists Gavin Shan
2012-06-24 19:18 ` KOSAKI Motohiro
2012-06-25 1:09 ` Gavin Shan
2012-06-25 15:39 ` Michal Hocko
2012-06-25 16:03 ` [PATCH 1/5] mm/sparse: check size of struct mm_section Michal Hocko
2012-06-25 16:35 ` Gavin Shan
2012-06-26 7:39 ` Michal Hocko
2012-06-26 7:48 ` Gavin Shan
2012-06-26 8:06 ` Michal Hocko
2012-06-26 8:24 ` Gavin Shan
2012-06-26 17:57 ` Michal Hocko
2012-06-27 3:01 ` Gavin Shan [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20120627030130.GA14213@shangw \
--to=shangw@linux.vnet.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=hannes@cmpxchg.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.cz \
--cc=rientjes@google.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).