Re: [bug report] xfs: use vmalloc instead of vm_map_area for buffer backing memory

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Subject: Re: [bug report] xfs: use vmalloc instead of vm_map_area for buffer backing memory
From: Christoph Hellwig <hch@xxxxxx>
Date: Tue, 18 Mar 2025 09:43:09 +0100
Cc: Christoph Hellwig <hch@xxxxxx>, linux-xfs@xxxxxxxxxxxxxxx
In-reply-to: <91be50b2-1c02-4952-8603-6803dd64f42d@stanley.mountain>
References: <91be50b2-1c02-4952-8603-6803dd64f42d@stanley.mountain>
User-agent: Mutt/1.5.17 (2007-11-01)

Hi Dan,

thanks for the report!

Even before we really would not want to call xfs_buf_rele with
locks held (or other preemption disabling), so I'll look into fixing
that.

References:
- [bug report] xfs: use vmalloc instead of vm_map_area for buffer backing memory
  - From: Dan Carpenter

Prev by Date: Re: [PATCH v6 11/13] xfs: add xfs_file_dio_write_atomic()
Next by Date: Re: [PATCH v6 00/13] large atomic writes for xfs with CoW
Previous by thread: [bug report] xfs: use vmalloc instead of vm_map_area for buffer backing memory
Next by thread: Re: [bug report] xfs: use vmalloc instead of vm_map_area for buffer backing memory
Index(es):
- Date
- Thread

[Index of Archives] [XFS Filesystem Development (older mail)] [Linux Filesystem Development] [Linux Audio Users] [Yosemite Trails] [Linux Kernel] [Linux RAID] [Linux SCSI]

Powered by Linux