Bug 1265197

Summary: quota: restrict creating hard-links across quota limit directories
Product: [Red Hat Storage] Red Hat Gluster Storage Reporter: Vijaikumar Mallikarjuna <vmallika>
Component: quotaAssignee: Manikandan <mselvaga>
Status: CLOSED WONTFIX QA Contact: storage-qa-internal <storage-qa-internal>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rhgs-3.1CC: mselvaga, rhs-bugs, smohan, storage-qa-internal, vagarwal
Target Milestone: ---Keywords: ZStream
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 1267464 (view as bug list) Environment:
Last Closed: 2015-10-06 08:21:08 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1267464    

Description Vijaikumar Mallikarjuna 2015-09-22 11:11:34 UTC
Currently it is allowed to create hard-link across quota limit directories. 
This becomes hard to enforce quota.

Comment 2 Vijaikumar Mallikarjuna 2015-10-06 08:21:08 UTC
This cannot be implemented in the current quota design:
Consider below scenario

Case-1)
a) below data with hard-links pre-exists
   /d1/f1
   /d2/f1
b) Set quota limit on /d1 and /d2
c) Now when creating hard-link /d1/f1 /d1/f2 can fail
   As we do fetch the inode_parent of f1 (f1's parent can be /d1 or /d2 in the
   dentry list)

Case-2)
a) Set quota limit on /d1 and /d2
b) create file /d1/f1 and link /d1/f2
c) rename /d1/f2 /d2/f2
d) Now when creating hard-link /d1/f1 /d1/f2 can fail
   As we do fetch the inode_parent of f1 (f1's parent can be /d1 or /d2 in the
   dentry list)


So marking the bug as wontfix