Re: btrfs/058 deadlock with lseek

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

 



On Tue, Nov 26, 2019 at 05:56:27PM +0800, Qu Wenruo wrote:
> On 2019/11/26 下午4:17, Qu Wenruo wrote:
> > Just got a reproducible error in btrfs/058.
> > The backtrace is completely in VFS territory, not btrfs related lock at all:
> 
> With the help of Nikolay and Johannes, the offending commit is pinned
> down to 0be0ee71816b ("vfs: properly and reliably lock f_pos in
> fdget_pos()"), and Linus will soon revert it.
> 
> Not a big deal, but testers would have a much easier life using David's
> misc-5.5 (still based on v5.4-rc).
> 
> And to David, would you please keep your misc-5.5 branch until the
> offending patch get reverted?

misc-5.5 will not rebase, it's the branch that gets pulled to master.
I won't rebase misc-next until rc1 at least and will rebase only after I
see that tests pass. During merge window lots of things are in flux so
breakage is expected so we need a development base for testing.



[Index of Archives]     [Linux Ext4 Filesystem]     [Union Filesystem]     [Filesystem Testing]     [Ceph Users]     [Ecryptfs]     [AutoFS]     [Kernel Newbies]     [Share Photos]     [Security]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux Cachefs]     [Reiser Filesystem]     [Linux RAID]     [Samba]     [Device Mapper]     [CEPH Development]

  Powered by Linux