On Thu, Jun 29, 2017 at 11:49 AM, Jeff Mahoney wrote:
> On 6/29/17 2:46 PM, Sargun Dhillon wrote:
>> On Thu, Jun 29, 2017 at 11:42 AM, Jeff Mahoney wrote:
>>> On 6/28/17 6:02 PM, Sargun Dhillon wrote:
On Wed, Jun 28, 2017 at 2:55 PM, Jeff Mahoney
On 6/29/17 2:46 PM, Sargun Dhillon wrote:
> On Thu, Jun 29, 2017 at 11:42 AM, Jeff Mahoney wrote:
>> On 6/28/17 6:02 PM, Sargun Dhillon wrote:
>>> On Wed, Jun 28, 2017 at 2:55 PM, Jeff Mahoney wrote:
On 6/27/17 5:12 PM, Jeff Mahoney wrote:
> On 6/13/17
On Thu, Jun 29, 2017 at 11:42 AM, Jeff Mahoney wrote:
> On 6/28/17 6:02 PM, Sargun Dhillon wrote:
>> On Wed, Jun 28, 2017 at 2:55 PM, Jeff Mahoney wrote:
>>> On 6/27/17 5:12 PM, Jeff Mahoney wrote:
On 6/13/17 9:05 PM, Sargun Dhillon wrote:
> On Thu, Jun
On 6/28/17 6:02 PM, Sargun Dhillon wrote:
> On Wed, Jun 28, 2017 at 2:55 PM, Jeff Mahoney wrote:
>> On 6/27/17 5:12 PM, Jeff Mahoney wrote:
>>> On 6/13/17 9:05 PM, Sargun Dhillon wrote:
On Thu, Jun 8, 2017 at 11:34 AM, Sargun Dhillon wrote:
> I have a
On Wed, Jun 28, 2017 at 2:55 PM, Jeff Mahoney wrote:
> On 6/27/17 5:12 PM, Jeff Mahoney wrote:
>> On 6/13/17 9:05 PM, Sargun Dhillon wrote:
>>> On Thu, Jun 8, 2017 at 11:34 AM, Sargun Dhillon wrote:
I have a deadlock caught in the wild between two processes
On 6/27/17 5:12 PM, Jeff Mahoney wrote:
> On 6/13/17 9:05 PM, Sargun Dhillon wrote:
>> On Thu, Jun 8, 2017 at 11:34 AM, Sargun Dhillon wrote:
>>> I have a deadlock caught in the wild between two processes --
>>> btrfs-cleaner, and userspace process (Docker). Here, you can see
On 6/13/17 9:05 PM, Sargun Dhillon wrote:
> On Thu, Jun 8, 2017 at 11:34 AM, Sargun Dhillon wrote:
>> I have a deadlock caught in the wild between two processes --
>> btrfs-cleaner, and userspace process (Docker). Here, you can see both
>> of the backtraces. btrfs-cleaner is
On Thu, Jun 8, 2017 at 11:34 AM, Sargun Dhillon wrote:
> I have a deadlock caught in the wild between two processes --
> btrfs-cleaner, and userspace process (Docker). Here, you can see both
> of the backtraces. btrfs-cleaner is trying to get a lock on
> 9859d360caf0, which
I have a deadlock caught in the wild between two processes --
btrfs-cleaner, and userspace process (Docker). Here, you can see both
of the backtraces. btrfs-cleaner is trying to get a lock on
9859d360caf0, which is owned by Docker's pid. Docker on the other
hand is trying to get a lock on