On Fri, Mar 14, 2014 at 10:44:04PM +, Hugo Mills wrote:
On Fri, Mar 14, 2014 at 02:51:22PM -0400, Josef Bacik wrote:
On 03/13/2014 06:16 PM, Hugo Mills wrote:
On Thu, Mar 13, 2014 at 03:42:13PM -0400, Josef Bacik wrote:
Lets try this again. We can deadlock the box if we send on a box
On Thu, Mar 13, 2014 at 10:16:28PM +, Hugo Mills wrote:
On Thu, Mar 13, 2014 at 03:42:13PM -0400, Josef Bacik wrote:
Lets try this again. We can deadlock the box if we send on a box and try to
write onto the same fs with the app that is trying to listen to the send
pipe.
This is
Lets try this again. We can deadlock the box if we send on a box and try to
write onto the same fs with the app that is trying to listen to the send pipe.
This is because the writer could get stuck waiting for a transaction commit
which is being blocked by the send. So fix this by making
On 03/13/2014 06:16 PM, Hugo Mills wrote:
On Thu, Mar 13, 2014 at 03:42:13PM -0400, Josef Bacik wrote:
Lets try this again. We can deadlock the box if we send on a box and try to
write onto the same fs with the app that is trying to listen to the send pipe.
This is because the writer could get
On Fri, Mar 14, 2014 at 02:51:22PM -0400, Josef Bacik wrote:
On 03/13/2014 06:16 PM, Hugo Mills wrote:
On Thu, Mar 13, 2014 at 03:42:13PM -0400, Josef Bacik wrote:
Lets try this again. We can deadlock the box if we send on a box and try to
write onto the same fs with the app that is trying to
Lets try this again. We can deadlock the box if we send on a box and try to
write onto the same fs with the app that is trying to listen to the send pipe.
This is because the writer could get stuck waiting for a transaction commit
which is being blocked by the send. So fix this by making sure
On Thu, Mar 13, 2014 at 03:42:13PM -0400, Josef Bacik wrote:
Lets try this again. We can deadlock the box if we send on a box and try to
write onto the same fs with the app that is trying to listen to the send pipe.
This is because the writer could get stuck waiting for a transaction commit
