Re: [PATCH] crypto/async_pq: use __free_page() instead of put_page()

2016-03-04 Thread Vlastimil Babka
On 02/29/2016 10:33 AM, Arnd Bergmann wrote: > The addition of tracepoints to the page reference tracking had an > unfortunate side-effect in at least one driver that calls put_page > from its exit function, resulting in a link error: > > `.exit.text' referenced in section `__jump_table' of crypto

Re: [PATCH] crypto/async_pq: use __free_page() instead of put_page()

2016-03-03 Thread Vinod Koul
On Tue, Mar 01, 2016 at 10:54:50PM +0900, Joonsoo Kim wrote: > 2016-03-01 3:04 GMT+09:00 Dan Williams : > > On Mon, Feb 29, 2016 at 1:33 AM, Arnd Bergmann wrote: > >> The addition of tracepoints to the page reference tracking had an > >> unfortunate side-effect in at least one driver that calls pu

Re: [PATCH] crypto/async_pq: use __free_page() instead of put_page()

2016-03-01 Thread Joonsoo Kim
2016-03-01 3:04 GMT+09:00 Dan Williams : > On Mon, Feb 29, 2016 at 1:33 AM, Arnd Bergmann wrote: >> The addition of tracepoints to the page reference tracking had an >> unfortunate side-effect in at least one driver that calls put_page >> from its exit function, resulting in a link error: >> >> `.

Re: [PATCH] crypto/async_pq: use __free_page() instead of put_page()

2016-02-29 Thread Dan Williams
On Mon, Feb 29, 2016 at 1:33 AM, Arnd Bergmann wrote: > The addition of tracepoints to the page reference tracking had an > unfortunate side-effect in at least one driver that calls put_page > from its exit function, resulting in a link error: > > `.exit.text' referenced in section `__jump_table'

[PATCH] crypto/async_pq: use __free_page() instead of put_page()

2016-02-29 Thread Arnd Bergmann
The addition of tracepoints to the page reference tracking had an unfortunate side-effect in at least one driver that calls put_page from its exit function, resulting in a link error: `.exit.text' referenced in section `__jump_table' of crypto/built-in.o: defined in discarded section `.exit.text'