<?xml version="1.0"?>
<?xml-stylesheet type="text/xsl" href="/rss.xsl.xml"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
    <title>Changes in Makefile</title>
    <description></description>
    <language>en</language>
    <copyright>Copyright 2015</copyright>
    <generator>Java</generator><item>
        <title>8e1d3227 - nfs_common: make include/linux/nfs4.h include generated nfs4_1.h</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/fs/nfsd/Makefile#8e1d3227</link>
        <description>nfs_common: make include/linux/nfs4.h include generated nfs4_1.hIn the long run, the NFS development community intends to autogenerate alot of the XDR handling code.  Both the NFS client and server include&quot;include/linux/nfs4.hi&quot;. That file was hand-rolled, and some of the symbolsin it conflict with the autogenerated symbols.Add a small nfs4_1.x to Documentation that currently just has thenecessary definitions for the delstid draft, and generate the relevantheader and source files. Make include/linux/nfs4.h include the generatedinclude/linux/sunrpc/xdrgen/nfs4_1.h and remove the conflictingdefinitions from it and nfs_xdr.h.Signed-off-by: Jeff Layton &lt;jlayton@kernel.org&gt;Signed-off-by: Chuck Lever &lt;chuck.lever@oracle.com&gt;

            List of files:
            /linux-6.15/fs/nfsd/Makefile</description>
        <pubDate>Mon, 09 Dec 2024 21:13:54 +0000</pubDate>
        <dc:creator>Jeff Layton &lt;jlayton@kernel.org&gt;</dc:creator>
    </item>
<item>
        <title>fa498386 - nfsd: add LOCALIO support</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/fs/nfsd/Makefile#fa498386</link>
        <description>nfsd: add LOCALIO supportAdd server support for bypassing NFS for localhost reads, writes, andcommits. This is only useful when both the client and server arerunning on the same host.If nfsd_open_local_fh() fails then the NFS client will both retry andfallback to normal network-based read, write and commit operations iflocalio is no longer supported.Care is taken to ensure the same NFS security mechanisms are used(authentication, etc) regardless of whether localio or regular NFSaccess is used.  The auth_domain established as part of the traditionalNFS client access to the NFS server is also used for localio.  Storeauth_domain for localio in nfsd_uuid_t and transfer it to the clientif it is local to the server.Relative to containers, localio gives the client access to the networknamespace the server has.  This is required to allow the client toaccess the server&apos;s per-namespace nfsd_net struct.This commit also introduces the use of NFSD&apos;s percpu_ref to interlocknfsd_destroy_serv and nfsd_open_local_fh, to ensure nn-&gt;nfsd_serv isnot destroyed while in use by nfsd_open_local_fh and other LOCALIOclient code.CONFIG_NFS_LOCALIO enables NFS server support for LOCALIO.Signed-off-by: Weston Andros Adamson &lt;dros@primarydata.com&gt;Signed-off-by: Trond Myklebust &lt;trond.myklebust@hammerspace.com&gt;Co-developed-by: Mike Snitzer &lt;snitzer@kernel.org&gt;Signed-off-by: Mike Snitzer &lt;snitzer@kernel.org&gt;Co-developed-by: NeilBrown &lt;neilb@suse.de&gt;Signed-off-by: NeilBrown &lt;neilb@suse.de&gt;Reviewed-by: Jeff Layton &lt;jlayton@kernel.org&gt;Acked-by: Chuck Lever &lt;chuck.lever@oracle.com&gt;Signed-off-by: Anna Schumaker &lt;anna.schumaker@oracle.com&gt;

            List of files:
            /linux-6.15/fs/nfsd/Makefile</description>
        <pubDate>Thu, 05 Sep 2024 19:09:50 +0000</pubDate>
        <dc:creator>Weston Andros Adamson &lt;dros@primarydata.com&gt;</dc:creator>
    </item>
<item>
        <title>13727f85 - NFSD: introduce netlink stubs</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/fs/nfsd/Makefile#13727f85</link>
        <description>NFSD: introduce netlink stubsGenerate stubs and uAPI for nfsd netlink protocol. For the moment,the new protocol has one operation: rpc_status.The generated header and source files are created by running:  tools/net/ynl/ynl-regen.shTested-by: Jeff Layton &lt;jlayton@kernel.org&gt;Signed-off-by: Lorenzo Bianconi &lt;lorenzo@kernel.org&gt;Acked-by: Jeff Layton &lt;jlayton@kernel.org&gt;Signed-off-by: Chuck Lever &lt;chuck.lever@oracle.com&gt;

            List of files:
            /linux-6.15/fs/nfsd/Makefile</description>
        <pubDate>Mon, 11 Sep 2023 12:49:44 +0000</pubDate>
        <dc:creator>Lorenzo Bianconi &lt;lorenzo@kernel.org&gt;</dc:creator>
    </item>
<item>
        <title>2f3a4b2a - nfsd: allow disabling NFSv2 at compile time</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/fs/nfsd/Makefile#2f3a4b2a</link>
        <description>nfsd: allow disabling NFSv2 at compile timerpc.nfsd stopped supporting NFSv2 a year ago. Take the next logicalstep toward deprecating it and allow NFSv2 support to be compiled out.Add a new CONFIG_NFSD_V2 option that can be turned off and rework theCONFIG_NFSD_V?_ACL option dependencies. Add a description thatdiscourages enabling it.Also, change the description of CONFIG_NFSD to state that the always-onversion is now 3 instead of 2.Finally, add an #ifdef around &quot;case 2:&quot; in __write_versions. When NFSv2is disabled at compile time, this should make the kernel ignore attemptsto disable it at runtime, but still error out when trying to enable it.Signed-off-by: Jeff Layton &lt;jlayton@kernel.org&gt;Reviewed-by: Tom Talpey &lt;tom@talpey.com&gt;Signed-off-by: Chuck Lever &lt;chuck.lever@oracle.com&gt;

            List of files:
            /linux-6.15/fs/nfsd/Makefile</description>
        <pubDate>Tue, 18 Oct 2022 11:47:56 +0000</pubDate>
        <dc:creator>Jeff Layton &lt;jlayton@kernel.org&gt;</dc:creator>
    </item>
<item>
        <title>5f9a62ff - NFSD: Remove CONFIG_NFSD_V3</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/fs/nfsd/Makefile#5f9a62ff</link>
        <description>NFSD: Remove CONFIG_NFSD_V3Eventually support for NFSv2 in the Linux NFS server is to bedeprecated and then removed.However, NFSv2 is the &quot;always supported&quot; version that is availableas soon as CONFIG_NFSD is set.  Before NFSv2 support can be removed,we need to choose a different &quot;always supported&quot; version.This patch removes CONFIG_NFSD_V3 so that NFSv3 is always supported,as NFSv2 is today. When NFSv2 support is removed, NFSv3 will becomethe only &quot;always supported&quot; NFS version.The defconfigs still need to be updated to remove CONFIG_NFSD_V3=y.Signed-off-by: Chuck Lever &lt;chuck.lever@oracle.com&gt;

            List of files:
            /linux-6.15/fs/nfsd/Makefile</description>
        <pubDate>Sun, 06 Feb 2022 17:25:47 +0000</pubDate>
        <dc:creator>Chuck Lever &lt;chuck.lever@oracle.com&gt;</dc:creator>
    </item>
<item>
        <title>e56dc9e2 - nfsd: remove fault injection code</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/fs/nfsd/Makefile#e56dc9e2</link>
        <description>nfsd: remove fault injection codeIt was an interesting idea but nobody seems to be using it, it&apos;s buggyat this point, and nfs4state.c is already complicated enough without it.The new nfsd/clients/ code provides some of the same functionality, andcould probably do more if desired.This feature has been deprecated since 9d60d93198c6 (&quot;Deprecate nfsdfault injection&quot;).Signed-off-by: J. Bruce Fields &lt;bfields@redhat.com&gt;

            List of files:
            /linux-6.15/fs/nfsd/Makefile</description>
        <pubDate>Fri, 31 Jul 2020 00:33:57 +0000</pubDate>
        <dc:creator>J. Bruce Fields &lt;bfields@redhat.com&gt;</dc:creator>
    </item>
<item>
        <title>65294c1f - nfsd: add a new struct file caching facility to nfsd</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/fs/nfsd/Makefile#65294c1f</link>
        <description>nfsd: add a new struct file caching facility to nfsdCurrently, NFSv2/3 reads and writes have to open a file, do the read orwrite and then close it again for each RPC. This is highly inefficient,especially when the underlying filesystem has a relatively slow openroutine.This patch adds a new open file cache to knfsd. Rather than doing anopen for each RPC, the read/write handlers can call into this cache tosee if there is one already there for the correct filehandle andNFS_MAY_READ/WRITE flags.If there isn&apos;t an entry, then we create a new one and attempt toperform the open. If there is, then we wait until the entry is fullyinstantiated and return it if it is at the end of the wait. If it&apos;snot, then we attempt to take over construction.Since the main goal is to speed up NFSv2/3 I/O, we don&apos;t want toclose these files on last put of these objects. We need to keep themaround for a little while since we never know when the next READ/WRITEwill come in.Cache entries have a hardcoded 1s timeout, and we have a recurringworkqueue job that walks the cache and purges any entries that haveexpired.Signed-off-by: Jeff Layton &lt;jeff.layton@primarydata.com&gt;Signed-off-by: Weston Andros Adamson &lt;dros@primarydata.com&gt;Signed-off-by: Richard Sharpe &lt;richard.sharpe@primarydata.com&gt;Signed-off-by: Trond Myklebust &lt;trond.myklebust@primarydata.com&gt;Signed-off-by: Trond Myklebust &lt;trond.myklebust@hammerspace.com&gt;Signed-off-by: J. Bruce Fields &lt;bfields@redhat.com&gt;

            List of files:
            /linux-6.15/fs/nfsd/Makefile</description>
        <pubDate>Sun, 18 Aug 2019 18:18:48 +0000</pubDate>
        <dc:creator>Jeff Layton &lt;jeff.layton@primarydata.com&gt;</dc:creator>
    </item>
<item>
        <title>b2441318 - License cleanup: add SPDX GPL-2.0 license identifier to files with no license</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/fs/nfsd/Makefile#b2441318</link>
        <description>License cleanup: add SPDX GPL-2.0 license identifier to files with no licenseMany source files in the tree are missing licensing information, whichmakes it harder for compliance tools to determine the correct license.By default all files without license information are under the defaultlicense of the kernel, which is GPL version 2.Update the files which contain no license information with the &apos;GPL-2.0&apos;SPDX license identifier.  The SPDX identifier is a legally bindingshorthand, which can be used instead of the full boiler plate text.This patch is based on work done by Thomas Gleixner and Kate Stewart andPhilippe Ombredanne.How this work was done:Patches were generated and checked against linux-4.14-rc6 for a subset ofthe use cases: - file had no licensing information it it. - file was a */uapi/* one with no licensing information in it, - file was a */uapi/* one with existing licensing information,Further patches will be generated in subsequent months to fix up caseswhere non-standard license headers were used, and references to licensehad to be inferred by heuristics based on keywords.The analysis to determine which SPDX License Identifier to be applied toa file was done in a spreadsheet of side by side results from of theoutput of two independent scanners (ScanCode &amp; Windriver) producing SPDXtag:value files created by Philippe Ombredanne.  Philippe prepared thebase worksheet, and did an initial spot review of a few 1000 files.The 4.13 kernel was the starting point of the analysis with 60,537 filesassessed.  Kate Stewart did a file by file comparison of the scannerresults in the spreadsheet to determine which SPDX license identifier(s)to be applied to the file. She confirmed any determination that was notimmediately clear with lawyers working with the Linux Foundation.Criteria used to select files for SPDX license identifier tagging was: - Files considered eligible had to be source code files. - Make and config files were included as candidates if they contained &gt;5   lines of source - File already had some variant of a license header in it (even if &lt;5   lines).All documentation files were explicitly excluded.The following heuristics were used to determine which SPDX licenseidentifiers to apply. - when both scanners couldn&apos;t find any license traces, file was   considered to have no license information in it, and the top level   COPYING file license applied.   For non */uapi/* files that summary was:   SPDX license identifier                            # files   ---------------------------------------------------|-------   GPL-2.0                                              11139   and resulted in the first patch in this series.   If that file was a */uapi/* path one, it was &quot;GPL-2.0 WITH   Linux-syscall-note&quot; otherwise it was &quot;GPL-2.0&quot;.  Results of that was:   SPDX license identifier                            # files   ---------------------------------------------------|-------   GPL-2.0 WITH Linux-syscall-note                        930   and resulted in the second patch in this series. - if a file had some form of licensing information in it, and was one   of the */uapi/* ones, it was denoted with the Linux-syscall-note if   any GPL family license was found in the file or had no licensing in   it (per prior point).  Results summary:   SPDX license identifier                            # files   ---------------------------------------------------|------   GPL-2.0 WITH Linux-syscall-note                       270   GPL-2.0+ WITH Linux-syscall-note                      169   ((GPL-2.0 WITH Linux-syscall-note) OR BSD-2-Clause)    21   ((GPL-2.0 WITH Linux-syscall-note) OR BSD-3-Clause)    17   LGPL-2.1+ WITH Linux-syscall-note                      15   GPL-1.0+ WITH Linux-syscall-note                       14   ((GPL-2.0+ WITH Linux-syscall-note) OR BSD-3-Clause)    5   LGPL-2.0+ WITH Linux-syscall-note                       4   LGPL-2.1 WITH Linux-syscall-note                        3   ((GPL-2.0 WITH Linux-syscall-note) OR MIT)              3   ((GPL-2.0 WITH Linux-syscall-note) AND MIT)             1   and that resulted in the third patch in this series. - when the two scanners agreed on the detected license(s), that became   the concluded license(s). - when there was disagreement between the two scanners (one detected a   license but the other didn&apos;t, or they both detected different   licenses) a manual inspection of the file occurred. - In most cases a manual inspection of the information in the file   resulted in a clear resolution of the license that should apply (and   which scanner probably needed to revisit its heuristics). - When it was not immediately clear, the license identifier was   confirmed with lawyers working with the Linux Foundation. - If there was any question as to the appropriate license identifier,   the file was flagged for further research and to be revisited later   in time.In total, over 70 hours of logged manual review was done on thespreadsheet to determine the SPDX license identifiers to apply to thesource files by Kate, Philippe, Thomas and, in some cases, confirmationby lawyers working with the Linux Foundation.Kate also obtained a third independent scan of the 4.13 code base fromFOSSology, and compared selected files where the other two scannersdisagreed against that SPDX file, to see if there was new insights.  TheWindriver scanner is based on an older version of FOSSology in part, sothey are related.Thomas did random spot checks in about 500 files from the spreadsheetsfor the uapi headers and agreed with SPDX license identifier in thefiles he inspected. For the non-uapi files Thomas did random spot checksin about 15000 files.In initial set of patches against 4.14-rc6, 3 files were found to havecopy/paste license identifier errors, and have been fixed to reflect thecorrect identifier.Additionally Philippe spent 10 hours this week doing a detailed manualinspection and review of the 12,461 patched files from the initial patchversion early this week with: - a full scancode scan run, collecting the matched texts, detected   license ids and scores - reviewing anything where there was a license detected (about 500+   files) to ensure that the applied SPDX license was correct - reviewing anything where there was no detection but the patch license   was not GPL-2.0 WITH Linux-syscall-note to ensure that the applied   SPDX license was correctThis produced a worksheet with 20 files needing minor correction.  Thisworksheet was then exported into 3 different .csv files for thedifferent types of files to be modified.These .csv files were then reviewed by Greg.  Thomas wrote a script toparse the csv files and add the proper SPDX tag to the file, in theformat that the file expected.  This script was further refined by Gregbased on the output to detect more types of files automatically and todistinguish between header and source .c files (which need differentcomment types.)  Finally Greg ran the script using the .csv files togenerate the patches.Reviewed-by: Kate Stewart &lt;kstewart@linuxfoundation.org&gt;Reviewed-by: Philippe Ombredanne &lt;pombredanne@nexb.com&gt;Reviewed-by: Thomas Gleixner &lt;tglx@linutronix.de&gt;Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

            List of files:
            /linux-6.15/fs/nfsd/Makefile</description>
        <pubDate>Wed, 01 Nov 2017 14:07:57 +0000</pubDate>
        <dc:creator>Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;</dc:creator>
    </item>
<item>
        <title>9b9960a0 - nfsd: Add a super simple flex file server</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/fs/nfsd/Makefile#9b9960a0</link>
        <description>nfsd: Add a super simple flex file serverHave a simple flex file server where the mds (NFSv4.1 or NFSv4.2)is also the ds (NFSv3). I.e., the metadata and the data file arethe exact same file.This will allow testing of the flex file client.Simply add the &quot;pnfs&quot; export option to your exportin /etc/exports and mount from a client that supportsflex files.Signed-off-by: Tom Haynes &lt;loghyr@primarydata.com&gt;Reviewed-by: Christoph Hellwig &lt;hch@lst.de&gt;Signed-off-by: J. Bruce Fields &lt;bfields@redhat.com&gt;

            List of files:
            /linux-6.15/fs/nfsd/Makefile</description>
        <pubDate>Tue, 14 Jun 2016 20:41:28 +0000</pubDate>
        <dc:creator>Tom Haynes &lt;thomas.haynes@primarydata.com&gt;</dc:creator>
    </item>
<item>
        <title>f99d4fbd - nfsd: add SCSI layout support</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/fs/nfsd/Makefile#f99d4fbd</link>
        <description>nfsd: add SCSI layout supportThis is a simple extension to the block layout driver to use SCSIpersistent reservations for access control and fencing, as well asSCSI VPD pages for device identification.For this we need to pass the nfs4_client to the proc_getdeviceinfo methodto generate the reservation key, and add a new fence_client methodto allow for fence actions in the layout driver.Signed-off-by: Christoph Hellwig &lt;hch@lst.de&gt;Signed-off-by: J. Bruce Fields &lt;bfields@redhat.com&gt;

            List of files:
            /linux-6.15/fs/nfsd/Makefile</description>
        <pubDate>Fri, 04 Mar 2016 19:46:17 +0000</pubDate>
        <dc:creator>Christoph Hellwig &lt;hch@lst.de&gt;</dc:creator>
    </item>
<item>
        <title>81c39329 - nfsd: add a new config option for the block layout driver</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/fs/nfsd/Makefile#81c39329</link>
        <description>nfsd: add a new config option for the block layout driverSplit the config symbols into a generic pNFS one, which is invisibleand gets selected by the layout drivers, and one for the block layoutdriver.Signed-off-by: Christoph Hellwig &lt;hch@lst.de&gt;Signed-off-by: J. Bruce Fields &lt;bfields@redhat.com&gt;

            List of files:
            /linux-6.15/fs/nfsd/Makefile</description>
        <pubDate>Fri, 04 Mar 2016 19:46:16 +0000</pubDate>
        <dc:creator>Christoph Hellwig &lt;hch@lst.de&gt;</dc:creator>
    </item>
<item>
        <title>8650b8a0 - nfsd: pNFS block layout driver</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/fs/nfsd/Makefile#8650b8a0</link>
        <description>nfsd: pNFS block layout driverAdd a small shim between core nfsd and filesystems to translate thesomewhat cumbersome pNFS data structures and semantics to somethingmore palatable for Linux filesystems.Thanks to Rick McNeal for the old prototype pNFS blocklayout servercode, which gave a lot of inspiration to this version even if nocode is left from it.Signed-off-by: Christoph Hellwig &lt;hch@lst.de&gt;

            List of files:
            /linux-6.15/fs/nfsd/Makefile</description>
        <pubDate>Wed, 21 Jan 2015 10:40:00 +0000</pubDate>
        <dc:creator>Christoph Hellwig &lt;hch@lst.de&gt;</dc:creator>
    </item>
<item>
        <title>31ef83dc - nfsd: add trace events</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/fs/nfsd/Makefile#31ef83dc</link>
        <description>nfsd: add trace eventsFor now just a few simple events to trace the layout stateid lifetime, butthese already were enough to find several bugs in the Linux client layoutstateid handling.Signed-off-by: Christoph Hellwig &lt;hch@lst.de&gt;

            List of files:
            /linux-6.15/fs/nfsd/Makefile</description>
        <pubDate>Sun, 17 Aug 2014 00:02:22 +0000</pubDate>
        <dc:creator>Christoph Hellwig &lt;hch@lst.de&gt;</dc:creator>
    </item>
<item>
        <title>9cf514cc - nfsd: implement pNFS operations</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/fs/nfsd/Makefile#9cf514cc</link>
        <description>nfsd: implement pNFS operationsAdd support for the GETDEVICEINFO, LAYOUTGET, LAYOUTCOMMIT andLAYOUTRETURN NFSv4.1 operations, as well as backing code to manageoutstanding layouts and devices.Layout management is very straight forward, with a nfs4_layout_stateidstructure that extends nfs4_stid to manage layout stateids as thetop-level structure.  It is linked into the nfs4_file and nfs4_clientstructures like the other stateids, and contains a linked list oflayouts that hang of the stateid.  The actual layout operations areimplemented in layout drivers that are not part of this commit, butwill be added later.The worst part of this commit is the management of the pNFS device IDs,which suffers from a specification that is not sanely implementable dueto the fact that the device-IDs are global and not bound to an export,and have a small enough size so that we can&apos;t store the fsid portion ofa file handle, and must never be reused.  As we still do need perform allexport authentication and validation checks on a device ID passed toGETDEVICEINFO we are caught between a rock and a hard place.  To workaround this issue we add a new hash that maps from a 64-bit integer to afsid so that we can look up the export to authenticate against it,a 32-bit integer as a generation that we can bump when changing the device,and a currently unused 32-bit integer that could be used in the futureto handle more than a single device per export.  Entries in this hashtable are never deleted as we can&apos;t reuse the ids anyway, and would havea severe lifetime problem anyway as Linux export structures are temporarystructures that can go away under load.Parts of the XDR data, structures and marshaling/unmarshaling code, aswell as many concepts are derived from the old pNFS server implementationfrom Andy Adamson, Benny Halevy, Dean Hildebrand, Marc Eshel, Fred Isaman,Mike Sager, Ricardo Labiaga and many others.Signed-off-by: Christoph Hellwig &lt;hch@lst.de&gt;

            List of files:
            /linux-6.15/fs/nfsd/Makefile</description>
        <pubDate>Mon, 05 May 2014 11:11:59 +0000</pubDate>
        <dc:creator>Christoph Hellwig &lt;hch@lst.de&gt;</dc:creator>
    </item>
<item>
        <title>65178db4 - NFSD: Added fault injection</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/fs/nfsd/Makefile#65178db4</link>
        <description>NFSD: Added fault injectionFault injection on the NFS server makes it easier to test the client&apos;sstate manager and recovery threads.  Simulating errors on the server iseasier than finding the right conditions that cause them naturally.This patch uses debugfs to add a simple framework for fault injection tothe server.  This framework is a config option, and can be enabledthrough CONFIG_NFSD_FAULT_INJECTION.  Assuming you have debugfs mountedto /sys/debug, a set of files will be created in /sys/debug/nfsd/.Writing to any of these files will cause the corresponding action andwrite a log entry to dmesg.Signed-off-by: Bryan Schumaker &lt;bjschuma@netapp.com&gt;Signed-off-by: J. Bruce Fields &lt;bfields@redhat.com&gt;

            List of files:
            /linux-6.15/fs/nfsd/Makefile</description>
        <pubDate>Tue, 01 Nov 2011 17:35:21 +0000</pubDate>
        <dc:creator>Bryan Schumaker &lt;bjschuma@netapp.com&gt;</dc:creator>
    </item>
<item>
        <title>f725b217 - knfsd: trivial makefile cleanup</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/fs/nfsd/Makefile#f725b217</link>
        <description>knfsd: trivial makefile cleanupkbuild directly interprets &lt;modulename&gt;-y as objects to build into a module,no need to assign it to the old foo-objs variable.Signed-off-by: Christoph Hellwig &lt;hch@lst.de&gt;Signed-off-by: Neil Brown &lt;neilb@suse.de&gt;Signed-off-by: Andrew Morton &lt;akpm@linux-foundation.org&gt;Signed-off-by: Linus Torvalds &lt;torvalds@linux-foundation.org&gt;

            List of files:
            /linux-6.15/fs/nfsd/Makefile</description>
        <pubDate>Wed, 09 May 2007 09:34:56 +0000</pubDate>
        <dc:creator>Christoph Hellwig &lt;hch@lst.de&gt;</dc:creator>
    </item>
<item>
        <title>a55370a3 - [PATCH] knfsd: nfsd4: reboot hash</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/fs/nfsd/Makefile#a55370a3</link>
        <description>[PATCH] knfsd: nfsd4: reboot hashFor the purposes of reboot recovery we keep a directory with subdirectorieseach having a name that is the ascii hex representation of the md5 sum of aclient identifier for an active client.This adds the code to calculate that name.  We also use it for the purposes ofcomparing clients, so if someone ever manages to find two client names thatare md5 collisions, then we&apos;ll return clid_inuse to the second.Signed-off-by: Andy Adamson &lt;andros@citi.umich.edu&gt;Signed-off-by: J. Bruce Fields &lt;bfields@citi.umich.edu&gt;Signed-off-by: Neil Brown &lt;neilb@cse.unsw.edu.au&gt;Signed-off-by: Andrew Morton &lt;akpm@osdl.org&gt;Signed-off-by: Linus Torvalds &lt;torvalds@osdl.org&gt;

            List of files:
            /linux-6.15/fs/nfsd/Makefile</description>
        <pubDate>Fri, 24 Jun 2005 05:03:52 +0000</pubDate>
        <dc:creator>NeilBrown &lt;neilb@cse.unsw.edu.au&gt;</dc:creator>
    </item>
<item>
        <title>a257cdd0 - [PATCH] NFSD: Add server support for NFSv3 ACLs.</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/fs/nfsd/Makefile#a257cdd0</link>
        <description>[PATCH] NFSD: Add server support for NFSv3 ACLs. This adds functions for encoding and decoding POSIX ACLs for the NFSACL protocol extension, and the GETACL and SETACL RPCs.  The implementation is compatible with NFSACL in Solaris. Signed-off-by: Andreas Gruenbacher &lt;agruen@suse.de&gt; Acked-by: Olaf Kirch &lt;okir@suse.de&gt; Signed-off-by: Andrew Morton &lt;akpm@osdl.org&gt; Signed-off-by: Trond Myklebust &lt;Trond.Myklebust@netapp.com&gt;

            List of files:
            /linux-6.15/fs/nfsd/Makefile</description>
        <pubDate>Wed, 22 Jun 2005 17:16:26 +0000</pubDate>
        <dc:creator>Andreas Gruenbacher &lt;agruen@suse.de&gt;</dc:creator>
    </item>
<item>
        <title>1da177e4 - Linux-2.6.12-rc2</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/fs/nfsd/Makefile#1da177e4</link>
        <description>Linux-2.6.12-rc2Initial git repository build. I&apos;m not bothering with the full history,even though we have it. We can create a separate &quot;historical&quot; gitarchive of that later if we want to, and in the meantime it&apos;s about3.2GB when imported into git - space that would just make the earlygit days unnecessarily complicated, when we don&apos;t have a lot of goodinfrastructure for it.Let it rip!

            List of files:
            /linux-6.15/fs/nfsd/Makefile</description>
        <pubDate>Sat, 16 Apr 2005 22:20:36 +0000</pubDate>
        <dc:creator>Linus Torvalds &lt;torvalds@ppc970.osdl.org&gt;</dc:creator>
    </item>
</channel>
</rss>
