<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux/fs, branch v2.6.13</title>
<subtitle>Mirror of https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/
</subtitle>
<id>https://git.shady.money/linux/atom?h=v2.6.13</id>
<link rel='self' href='https://git.shady.money/linux/atom?h=v2.6.13'/>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/'/>
<updated>2005-08-27T02:37:13Z</updated>
<entry>
<title>[PATCH] Fix oops in sysfs_hash_and_remove_file()</title>
<updated>2005-08-27T02:37:13Z</updated>
<author>
<name>James Bottomley</name>
<email>James.Bottomley@SteelEye.com</email>
</author>
<published>2005-08-27T01:34:17Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=36676bcbf9f6bcbea9d06e67ee8d04eacde54952'/>
<id>urn:sha1:36676bcbf9f6bcbea9d06e67ee8d04eacde54952</id>
<content type='text'>
The problem arises if an entity in sysfs is created and removed without
ever having been made completely visible.  In SCSI this is triggered by
removing a device while it's initialising.

The problem appears to be that because it was never made visible in sysfs,
the sysfs dentry has a null d_inode which oopses when a reference is made
to it.  The solution is simply to check d_inode and assume the object was
never made visible (and thus doesn't need deleting) if it's NULL.

(akpm: possibly a stopgap for 2.6.13 scsi problems.  May not be the
long-term fix)

Signed-off-by: James Bottomley &lt;James.Bottomley@SteelEye.com&gt;
Cc: Greg KH &lt;greg@kroah.com&gt;
Signed-off-by: Andrew Morton &lt;akpm@osdl.org&gt;
Signed-off-by: Linus Torvalds &lt;torvalds@osdl.org&gt;
</content>
</entry>
<entry>
<title>[PATCH] Fix oops in fs/locks.c on close of file with pending locks</title>
<updated>2005-08-26T23:05:35Z</updated>
<author>
<name>Steve French</name>
<email>smfltc@us.ibm.com</email>
</author>
<published>2005-08-26T19:42:59Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=d634cc15e8f33332038dc9c078beae79f9382ada'/>
<id>urn:sha1:d634cc15e8f33332038dc9c078beae79f9382ada</id>
<content type='text'>
The recent change to locks_remove_flock code in fs/locks.c changes how
byte range locks are removed from closing files, which shows up a bug in
cifs.

The assumption in the cifs code was that the close call sent to the
server would remove any pending locks on the server on this file, but
that is no longer safe as the fs/locks.c code on the client wants unlock
of 0 to PATH_MAX to remove all locks (at least from this client, it is
not possible AFAIK to remove all locks from other clients made to the
server copy of the file).

Note that cifs locks are different from posix locks - and it is not
possible to map posix locks perfectly on the wire yet, due to
restrictions of the cifs network protocol, even to Samba without adding
a new request type to the network protocol (which we plan to do for
Samba 3.0.21 within a few months), but the local client will have the
correct, posix view, of the lock in most cases.

The correct fix for cifs for this would involve a bigger change than I
would like to do this late in the 2.6.13-rc cycle - and would involve
cifs keeping track of all unmerged (uncoalesced) byte range locks for
each remote inode and scanning that list to remove locks that intersect
or fall wholly within the range - locks that intersect may have to be
reaquired with the smaller, remaining range.

Signed-off-by: Steve French &lt;sfrench@us.ibm.com&gt;
Signed-off-by: Dave Kleikamp &lt;shaggy@austin.ibm.com&gt;
Signed-off-by: Linus Torvalds &lt;torvalds@osdl.org&gt;
</content>
</entry>
<entry>
<title>[PATCH] hppfs: fix symlink error path</title>
<updated>2005-08-26T18:39:19Z</updated>
<author>
<name>Paolo 'Blaisorblade' Giarrusso</name>
<email>blaisorblade@yahoo.it</email>
</author>
<published>2005-08-26T14:57:53Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=fd589e0b662c1ea8cfb1e0d20d60a2510979865b'/>
<id>urn:sha1:fd589e0b662c1ea8cfb1e0d20d60a2510979865b</id>
<content type='text'>
While touching this code I noticed the error handling is bogus, so I
fixed it up.

I've removed the IS_ERR(proc_dentry) check, which will never trigger and
is clearly a typo: we must check proc_file instead.

Signed-off-by: Paolo 'Blaisorblade' Giarrusso &lt;blaisorblade@yahoo.it&gt;
Signed-off-by: Linus Torvalds &lt;torvalds@osdl.org&gt;
</content>
</entry>
<entry>
<title>[PATCH] Fixup symlink function pointers for hppfs [for 2.6.13]</title>
<updated>2005-08-26T18:39:19Z</updated>
<author>
<name>Paolo 'Blaisorblade' Giarrusso</name>
<email>blaisorblade@yahoo.it</email>
</author>
<published>2005-08-26T14:57:44Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=d7a60d50d7713b65a3fd88f11d5717b83a6b6a97'/>
<id>urn:sha1:d7a60d50d7713b65a3fd88f11d5717b83a6b6a97</id>
<content type='text'>
Update hppfs for the symlink functions prototype change.

Yes, I know the code I leave there is still _bogus_, see next patch for
this.

Signed-off-by: Paolo 'Blaisorblade' Giarrusso &lt;blaisorblade@yahoo.it&gt;
Signed-off-by: Linus Torvalds &lt;torvalds@osdl.org&gt;
</content>
</entry>
<entry>
<title>[PATCH] Document idr_get_new_above() semantics, update inotify</title>
<updated>2005-08-26T18:32:57Z</updated>
<author>
<name>John McCutchan</name>
<email>ttb@tentacle.dhs.org</email>
</author>
<published>2005-08-26T18:02:04Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=7c657f2f25d50c602df9291bc6242b98fc090759'/>
<id>urn:sha1:7c657f2f25d50c602df9291bc6242b98fc090759</id>
<content type='text'>
There is an off by one problem with idr_get_new_above.

The comment and function name suggest that it will return an id &gt;
starting_id, but it actually returned an id &gt;= starting_id, and kernel
callers other than inotify treated it as such.

The patch below fixes the comment, and fixes inotifys usage.  The
function name still doesn't match the behaviour, but it never did.

Signed-off-by: John McCutchan &lt;ttb@tentacle.dhs.org&gt;
Signed-off-by: Linus Torvalds &lt;torvalds@osdl.org&gt;
</content>
</entry>
<entry>
<title>Don't allow normal users to set idle IO priority</title>
<updated>2005-08-21T01:51:29Z</updated>
<author>
<name>Linus Torvalds</name>
<email>torvalds@g5.osdl.org</email>
</author>
<published>2005-08-21T01:51:29Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=f6fdd7d9c273bb2a20ab467cb57067494f932fa3'/>
<id>urn:sha1:f6fdd7d9c273bb2a20ab467cb57067494f932fa3</id>
<content type='text'>
It has all the normal priority inversion problems.

Signed-off-by: Linus Torvalds &lt;torvalds@osdl.org&gt;
</content>
</entry>
<entry>
<title>[PATCH] freevxfs: fix breakage introduced by symlink fixes</title>
<updated>2005-08-20T21:30:50Z</updated>
<author>
<name>Alexey Dobriyan</name>
<email>adobriyan@gmail.com</email>
</author>
<published>2005-08-20T21:08:36Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=a5ea169c9581553662bb79a1c8c98fed1ee84246'/>
<id>urn:sha1:a5ea169c9581553662bb79a1c8c98fed1ee84246</id>
<content type='text'>
Signed-off-by: Alexey Dobriyan &lt;adobriyan@gmail.com&gt;
Signed-off-by: Linus Torvalds &lt;torvalds@osdl.org&gt;
</content>
</entry>
<entry>
<title>befs: fix up missed follow_link declaration change</title>
<updated>2005-08-20T20:20:01Z</updated>
<author>
<name>Linus Torvalds</name>
<email>torvalds@g5.osdl.org</email>
</author>
<published>2005-08-20T20:20:01Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=db873896d168217e213902c7163fda7ee798781b'/>
<id>urn:sha1:db873896d168217e213902c7163fda7ee798781b</id>
<content type='text'>
We'd updated the prototype and the return value, but not the function
declaration itself.
</content>
</entry>
<entry>
<title>[PATCH] NFSv4: unbalanced BKL in nfs_atomic_lookup()</title>
<updated>2005-08-20T01:44:56Z</updated>
<author>
<name>Steve Dickson</name>
<email>SteveD@redhat.com</email>
</author>
<published>2005-08-20T00:57:48Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=01c314a0c0f6367960a7cb1ffb5796560ccaa1c1'/>
<id>urn:sha1:01c314a0c0f6367960a7cb1ffb5796560ccaa1c1</id>
<content type='text'>
Added missing unlock_kernel() to NFSv4 atomic lookup.

Signed-off-by: Steve Dickson &lt;steved@redhat.com&gt;
Signed-off-by: Trond Myklebust &lt;Trond.Myklebust@netapp.com&gt;
Signed-off-by: Andrew Morton &lt;akpm@osdl.org&gt;
Signed-off-by: Linus Torvalds &lt;torvalds@osdl.org&gt;
</content>
</entry>
<entry>
<title>[PATCH] Fix up symlink function pointers</title>
<updated>2005-08-20T01:08:21Z</updated>
<author>
<name>Al Viro</name>
<email>viro@parcelfarce.linux.theplanet.co.uk</email>
</author>
<published>2005-08-19T23:17:39Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=008b150a3c4d971cd65d02d107b8fcc860bc959c'/>
<id>urn:sha1:008b150a3c4d971cd65d02d107b8fcc860bc959c</id>
<content type='text'>
This fixes up the symlink functions for the calling convention change:

 * afs, autofs4, befs, devfs, freevxfs, jffs2, jfs, ncpfs, procfs,
   smbfs, sysvfs, ufs, xfs - prototype change for -&gt;follow_link()
 * befs, smbfs, xfs - same for -&gt;put_link()

Signed-off-by: Linus Torvalds &lt;torvalds@osdl.org&gt;
</content>
</entry>
</feed>
