Here's another lockdep report for you. If you hard link a file, the attached
occurs.
=
[ INFO: possible recursive locking detected ]
3.15.0-rc6-fsdevel+ #367 Tainted: GW
-
ln/2974 is trying to acq
Miklos Szeredi wrote:
> generic_file_splice_write() uses I_MUTEX_CHILD. Not sure why, though, parent
> shouldn't be locked. Maybe it's some remaining thing from the days when pipes
> used the i_mutex on the pipe inode. Probably should just remove that notation
> and things will work.
You shou
On Thu, May 29, 2014 at 05:23:22PM +0100, David Howells wrote:
> Miklos Szeredi wrote:
>
> > Fixes pushed to overlayfs.v22 (and overlayfs.current). Will
> > eventually fold these into the main overlayfs patch.
>
> Okay... those are fixed. Here's the next:
>
generic_file_splice_write() uses I
Miklos Szeredi wrote:
> Fixes pushed to overlayfs.v22 (and overlayfs.current). Will
> eventually fold these into the main overlayfs patch.
Okay... those are fixed. Here's the next:
=
[ INFO: possible recursive locking detected ]
3.15.0-rc6-fsdevel+
On Thu, May 29, 2014 at 6:06 PM, Miklos Szeredi wrote:
> On Thu, May 29, 2014 at 2:07 PM, Miklos Szeredi wrote:
>> On Thu, May 29, 2014 at 12:28:45PM +0100, David Howells wrote:
>>>
>>> This sequence of commands produces both errors:
>
> Fixes pushed to overlayfs.v22 (and overlayfs.current). Wil
On Thu, May 29, 2014 at 2:07 PM, Miklos Szeredi wrote:
> On Thu, May 29, 2014 at 12:28:45PM +0100, David Howells wrote:
>>
>> This sequence of commands produces both errors:
Fixes pushed to overlayfs.v22 (and overlayfs.current). Will
eventually fold these into the main overlayfs patch.
Thanks,
On Thu, May 29, 2014 at 12:28:45PM +0100, David Howells wrote:
>
> This sequence of commands produces both errors:
>
> mount -t tmpfs lower_layer /lower
> mount -t tmpfs upper_layer /upper
> mkdir /upper/upper
> mkdir /upper/work
> mount -t overlayfs overlayfs /mnt
> -olowerdir=/lower,upper
This sequence of commands produces both errors:
mount -t tmpfs lower_layer /lower
mount -t tmpfs upper_layer /upper
mkdir /upper/upper
mkdir /upper/work
mount -t overlayfs overlayfs /mnt
-olowerdir=/lower,upperdir=/upper/upper,workdir=/upper/work
# The lockdep error was reported in the abo
David Howells wrote:
>
> [ BUG: lock held when returning to user space! ]
> 3.15.0-rc6-fsdevel+ #363 Tainted: GW
>
> mount/4183 is leaving the kernel with locks still held!
> 1 lock held
When I run my unionmount testsuite against overlayfs, I get the following
lockdep warning (unionmount is not in the kernel sources in this test):
[ BUG: lock held when returning to user space! ]
3.15.0-rc6-fsdevel+ #363 Tainted: GW
10 matches
Mail list logo
