On 23.02.2018 01:39, David Sterba wrote:
> On Thu, Feb 22, 2018 at 12:24:40PM -0700, Liu Bo wrote:
> Not even that far, isize is truncated before calling inode_dio_wait()
> and a memory barrier is set to ensure the correct order, so dio read
> would simply return if it's reading past
On Thu, Feb 22, 2018 at 12:24:40PM -0700, Liu Bo wrote:
> > > > Not even that far, isize is truncated before calling inode_dio_wait()
> > > > and a memory barrier is set to ensure the correct order, so dio read
> > > > would simply return if it's reading past isize.
> > >
> > > Please, describe
On Thu, Feb 22, 2018 at 12:09:45PM -0700, Liu Bo wrote:
> On Thu, Feb 22, 2018 at 08:49:30AM +0200, Nikolay Borisov wrote:
> >
> >
> > On 22.02.2018 00:38, Liu Bo wrote:
> > > On Wed, Feb 21, 2018 at 07:05:13PM +, Filipe Manana wrote:
> > >> On Wed, Feb 21, 2018 at 6:28 PM, Liu Bo
On Thu, Feb 22, 2018 at 08:49:30AM +0200, Nikolay Borisov wrote:
>
>
> On 22.02.2018 00:38, Liu Bo wrote:
> > On Wed, Feb 21, 2018 at 07:05:13PM +, Filipe Manana wrote:
> >> On Wed, Feb 21, 2018 at 6:28 PM, Liu Bo wrote:
> >>> On Wed, Feb 21, 2018 at 02:42:08PM +,
On Wed, Feb 21, 2018 at 10:38 PM, Liu Bo wrote:
> On Wed, Feb 21, 2018 at 07:05:13PM +, Filipe Manana wrote:
>> On Wed, Feb 21, 2018 at 6:28 PM, Liu Bo wrote:
>> > On Wed, Feb 21, 2018 at 02:42:08PM +, Filipe Manana wrote:
>> >> On Wed, Feb 21,
On 22.02.2018 00:38, Liu Bo wrote:
> On Wed, Feb 21, 2018 at 07:05:13PM +, Filipe Manana wrote:
>> On Wed, Feb 21, 2018 at 6:28 PM, Liu Bo wrote:
>>> On Wed, Feb 21, 2018 at 02:42:08PM +, Filipe Manana wrote:
On Wed, Feb 21, 2018 at 2:15 PM, Nikolay Borisov
On Wed, Feb 21, 2018 at 07:05:13PM +, Filipe Manana wrote:
> On Wed, Feb 21, 2018 at 6:28 PM, Liu Bo wrote:
> > On Wed, Feb 21, 2018 at 02:42:08PM +, Filipe Manana wrote:
> >> On Wed, Feb 21, 2018 at 2:15 PM, Nikolay Borisov wrote:
> >> >
> >> >
>
On Wed, Feb 21, 2018 at 04:15:38PM +0200, Nikolay Borisov wrote:
>
>
> On 21.02.2018 15:51, Filipe Manana wrote:
> > On Wed, Feb 21, 2018 at 11:41 AM, Nikolay Borisov wrote:
> >> Currently the DIO read cases uses a botched idea from ext4 to ensure
> >> that DIO reads don't
On 21.02.2018 20:28, Liu Bo wrote:
> On Wed, Feb 21, 2018 at 02:42:08PM +, Filipe Manana wrote:
>> On Wed, Feb 21, 2018 at 2:15 PM, Nikolay Borisov wrote:
>>>
>>>
>>> On 21.02.2018 15:51, Filipe Manana wrote:
On Wed, Feb 21, 2018 at 11:41 AM, Nikolay Borisov
On Wed, Feb 21, 2018 at 6:28 PM, Liu Bo wrote:
> On Wed, Feb 21, 2018 at 02:42:08PM +, Filipe Manana wrote:
>> On Wed, Feb 21, 2018 at 2:15 PM, Nikolay Borisov wrote:
>> >
>> >
>> > On 21.02.2018 15:51, Filipe Manana wrote:
>> >> On Wed, Feb 21, 2018
On Wed, Feb 21, 2018 at 02:42:08PM +, Filipe Manana wrote:
> On Wed, Feb 21, 2018 at 2:15 PM, Nikolay Borisov wrote:
> >
> >
> > On 21.02.2018 15:51, Filipe Manana wrote:
> >> On Wed, Feb 21, 2018 at 11:41 AM, Nikolay Borisov
> >> wrote:
> >>> Currently
On Wed, Feb 21, 2018 at 2:15 PM, Nikolay Borisov wrote:
>
>
> On 21.02.2018 15:51, Filipe Manana wrote:
>> On Wed, Feb 21, 2018 at 11:41 AM, Nikolay Borisov wrote:
>>> Currently the DIO read cases uses a botched idea from ext4 to ensure
>>> that DIO reads
On 21.02.2018 15:51, Filipe Manana wrote:
> On Wed, Feb 21, 2018 at 11:41 AM, Nikolay Borisov wrote:
>> Currently the DIO read cases uses a botched idea from ext4 to ensure
>> that DIO reads don't race with truncate. The idea is that if we have a
>> pending truncate we set
On Wed, Feb 21, 2018 at 11:41 AM, Nikolay Borisov wrote:
> Currently the DIO read cases uses a botched idea from ext4 to ensure
> that DIO reads don't race with truncate. The idea is that if we have a
> pending truncate we set BTRFS_INODE_READDIO_NEED_LOCK which in turn
>
On Wed, Feb 21, 2018 at 11:41 AM, Nikolay Borisov wrote:
> Currently the DIO read cases uses a botched idea from ext4 to ensure
> that DIO reads don't race with truncate. The idea is that if we have a
> pending truncate we set BTRFS_INODE_READDIO_NEED_LOCK which in turn
>
On 21.02.2018 15:06, Filipe Manana wrote:
> On Wed, Feb 21, 2018 at 11:41 AM, Nikolay Borisov wrote:
>> Currently the DIO read cases uses a botched idea from ext4 to ensure
>> that DIO reads don't race with truncate. The idea is that if we have a
>> pending truncate we set
On Wed, Feb 21, 2018 at 1:10 PM, Nikolay Borisov wrote:
>
>
> On 21.02.2018 15:06, Filipe Manana wrote:
>> On Wed, Feb 21, 2018 at 11:41 AM, Nikolay Borisov wrote:
>>> Currently the DIO read cases uses a botched idea from ext4 to ensure
>>> that DIO reads
Currently the DIO read cases uses a botched idea from ext4 to ensure
that DIO reads don't race with truncate. The idea is that if we have a
pending truncate we set BTRFS_INODE_READDIO_NEED_LOCK which in turn
forces the dio read case to fallback to inode_locking to prevent
read/truncate races.
18 matches
Mail list logo