Hi
Am 04.02.25 um 09:37 schrieb Lorenzo Stoakes:
On Tue, Feb 04, 2025 at 09:21:55AM +0100, Thomas Zimmermann wrote:
Hi
Am 31.01.25 um 19:28 schrieb Lorenzo Stoakes:
With the introduction of mapping_wrprotect_page() there is no need to use
folio_mkclean() in order to write-protect mappings o
On Tue, Feb 04, 2025 at 09:21:55AM +0100, Thomas Zimmermann wrote:
> Hi
>
>
> Am 31.01.25 um 19:28 schrieb Lorenzo Stoakes:
> > With the introduction of mapping_wrprotect_page() there is no need to use
> > folio_mkclean() in order to write-protect mappings of frame buffer pages,
> > and therefore n
Hi
Am 31.01.25 um 19:28 schrieb Lorenzo Stoakes:
With the introduction of mapping_wrprotect_page() there is no need to use
folio_mkclean() in order to write-protect mappings of frame buffer pages,
and therefore no need to inappropriately set kernel-allocated page->index,
mapping fields to permi
(This time sent in reply to the correct series...)
On Fri, Jan 31, 2025 at 06:28:58PM +, Lorenzo Stoakes wrote:
> With the introduction of mapping_wrprotect_page() there is no need to use
> folio_mkclean() in order to write-protect mappings of frame buffer pages,
> and therefore no need to ina
With the introduction of mapping_wrprotect_page() there is no need to use
folio_mkclean() in order to write-protect mappings of frame buffer pages,
and therefore no need to inappropriately set kernel-allocated page->index,
mapping fields to permit this operation.
Instead, store the pointer to the
On Wed, Jan 08, 2025 at 07:41:31PM +, Lorenzo Stoakes wrote:
> On Wed, Jan 08, 2025 at 05:32:54PM +, Matthew Wilcox wrote:
> > On Wed, Jan 08, 2025 at 04:18:42PM +, Lorenzo Stoakes wrote:
> > > @@ -280,7 +269,10 @@ static void fb_deferred_io_work(struct work_struct
> > > *work)
> > >
On Wed, Jan 08, 2025 at 10:12:36PM +0100, David Hildenbrand wrote:
> On 08.01.25 21:54, Matthew Wilcox wrote:
> > On Wed, Jan 08, 2025 at 09:14:53PM +0100, David Hildenbrand wrote:
> > > On 08.01.25 18:32, Matthew Wilcox wrote:
> > > > On Wed, Jan 08, 2025 at 04:18:42PM +, Lorenzo Stoakes wrote
On Wed, Jan 08, 2025 at 11:02:57PM +0100, David Hildenbrand wrote:
> On 08.01.25 22:55, Matthew Wilcox wrote:
> > On Wed, Jan 08, 2025 at 10:12:36PM +0100, David Hildenbrand wrote:
> > > On 08.01.25 21:54, Matthew Wilcox wrote:
> > > > Not necessarily! We already do that (since 2022) for DAX (see
On 08.01.25 22:55, Matthew Wilcox wrote:
On Wed, Jan 08, 2025 at 10:12:36PM +0100, David Hildenbrand wrote:
On 08.01.25 21:54, Matthew Wilcox wrote:
Not necessarily! We already do that (since 2022) for DAX (see
6a8e0596f004). rmap lets you find every place that a given range
of a file is mapp
On Wed, Jan 08, 2025 at 10:12:36PM +0100, David Hildenbrand wrote:
> On 08.01.25 21:54, Matthew Wilcox wrote:
> > Not necessarily! We already do that (since 2022) for DAX (see
> > 6a8e0596f004). rmap lets you find every place that a given range
> > of a file is mapped into user address spaces; bu
On 08.01.25 21:54, Matthew Wilcox wrote:
On Wed, Jan 08, 2025 at 09:14:53PM +0100, David Hildenbrand wrote:
On 08.01.25 18:32, Matthew Wilcox wrote:
On Wed, Jan 08, 2025 at 04:18:42PM +, Lorenzo Stoakes wrote:
@@ -280,7 +269,10 @@ static void fb_deferred_io_work(struct work_struct *work)
On Wed, Jan 08, 2025 at 09:14:53PM +0100, David Hildenbrand wrote:
> On 08.01.25 18:32, Matthew Wilcox wrote:
> > On Wed, Jan 08, 2025 at 04:18:42PM +, Lorenzo Stoakes wrote:
> > > @@ -280,7 +269,10 @@ static void fb_deferred_io_work(struct work_struct
> > > *work)
> > > stru
On 08.01.25 18:32, Matthew Wilcox wrote:
On Wed, Jan 08, 2025 at 04:18:42PM +, Lorenzo Stoakes wrote:
@@ -280,7 +269,10 @@ static void fb_deferred_io_work(struct work_struct *work)
struct folio *folio = page_folio(pageref->page);
folio_lock(folio);
- fol
On Wed, Jan 08, 2025 at 05:32:54PM +, Matthew Wilcox wrote:
> On Wed, Jan 08, 2025 at 04:18:42PM +, Lorenzo Stoakes wrote:
> > @@ -280,7 +269,10 @@ static void fb_deferred_io_work(struct work_struct
> > *work)
> > struct folio *folio = page_folio(pageref->page);
> >
> >
On Wed, Jan 08, 2025 at 04:18:42PM +, Lorenzo Stoakes wrote:
> @@ -280,7 +269,10 @@ static void fb_deferred_io_work(struct work_struct *work)
> struct folio *folio = page_folio(pageref->page);
>
> folio_lock(folio);
> - folio_mkclean(folio);
> +
With the introduction of rmap_wrprotect_file_page() there is no need to use
folio_mkclean() in order to write-protect mappings of frame buffer pages,
and therefore no need to inappropriately set kernel-allocated page->index,
mapping fields to permit this operation.
Instead, store the pointer to th
16 matches
Mail list logo
