<!-- 
RSS generated by JIRA (9.4.14#940014-sha1:734e6822bbf0d45eff9af51f82432957f73aa32c) at Sat Feb 10 02:44:59 UTC 2024

It is possible to restrict the fields that are returned in this document by specifying the 'field' parameter in your request.
For example, to request only the issue key and summary append 'field=key&field=summary' to the URL of your request.
-->
<rss version="0.92" >
<channel>
    <title>Whamcloud Community JIRA</title>
    <link>https://jira.whamcloud.com</link>
    <description>This file is an XML representation of an issue</description>
    <language>en-us</language>    <build-info>
        <version>9.4.14</version>
        <build-number>940014</build-number>
        <build-date>05-12-2023</build-date>
    </build-info>


<item>
            <title>[LU-11566] sanity test_60aa: llog_print_cb()) not enough space for print log records</title>
                <link>https://jira.whamcloud.com/browse/LU-11566</link>
                <project id="10000" key="LU">Lustre</project>
                    <description>&lt;p&gt;This issue was created by maloo for Andreas Dilger  &amp;lt;adilger@whamcloud.com&amp;gt;&lt;/p&gt;

&lt;p&gt;This issue relates to the following test suite run: &lt;a href=&quot;https://testing.whamcloud.com/test_sets/473e7234-d712-11e8-ad90-52540065bddc&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://testing.whamcloud.com/test_sets/473e7234-d712-11e8-ad90-52540065bddc&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;test_60aa produced the following stack trace:&lt;/p&gt;
&lt;div class=&quot;preformatted panel&quot; style=&quot;border-width: 1px;&quot;&gt;&lt;div class=&quot;preformattedContent panelContent&quot;&gt;
&lt;pre&gt;Lustre: DEBUG MARKER: /usr/sbin/lctl --device %MGS llog_print \$lustre-client
------------[ cut here ]------------
WARNING: CPU: 1 PID: 5457 at lib/vsprintf.c:1741 vsnprintf+0x691/0x6a0
CPU: 1 PID: 5457 Comm: llog_process_th Kernel: 3.10.0-862.14.4.el7_lustre.x86_64 #1
Call Trace:
 dump_stack+0x19/0x1b
 warn_slowpath_null+0x1d/0x20
 vsnprintf+0x691/0x6a0
 snprintf+0x49/0x70
 class_config_yaml_output+0x22a/0x430 [obdclass]
 llog_print_cb+0x415/0x4f0 [obdclass]
 llog_process_thread+0x892/0x15a0 [obdclass]
 llog_process_thread_daemonize+0x9f/0xe0 [obdclass]
 kthread+0xd1/0xe0
---[ end trace a7e0036714283adf ]---
LustreError: 5457:0:(llog_ioctl.c:264:llog_print_cb()) not enough space for print log records
&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;

&lt;p&gt;It looks like this is a problem in how &lt;tt&gt;class_config_yaml_output()&lt;/tt&gt; is written:&lt;/p&gt;
&lt;div class=&quot;code panel&quot; style=&quot;border-width: 1px;&quot;&gt;&lt;div class=&quot;codeContent panelContent&quot;&gt;
&lt;pre class=&quot;code-java&quot;&gt;
&#65533;&#65533;&#65533;&#65533;&#65533;&#65533;&#65533;&#65533;        &lt;span class=&quot;code-keyword&quot;&gt;if&lt;/span&gt; (LUSTRE_CFG_BUFLEN(lcfg, 0) &amp;gt; 0)
               &#65533;&#65533;&#65533;&#65533;&#65533;&#65533;&#65533;&#65533;&#65533;&#65533;&#65533;&#65533;&#65533;&#65533;&#65533;&#65533;ptr += snprintf(ptr, end - ptr, &lt;span class=&quot;code-quote&quot;&gt;&quot;, device: %s&quot;&lt;/span&gt;,
                              &#65533;&#65533;&#65533;&#65533;&#65533;&#65533;&#65533;&#65533;&#65533;&#65533;&#65533;&#65533;&#65533;&#65533;&#65533;&#65533;&#65533;&#65533;&#65533;&#65533;&#65533;&#65533;&#65533;&#65533;&#65533;&#65533;&#65533;&#65533;&#65533;&#65533;&#65533;&#65533;lustre_cfg_string(lcfg, 0));
&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;
&lt;p&gt;If &lt;tt&gt;ptr&lt;/tt&gt; ever exceeds &lt;tt&gt;end&lt;/tt&gt; then a negative value is passed to &lt;tt&gt;snprintf()&lt;/tt&gt;, and triggers this &lt;tt&gt;WARN_ONCE()&lt;/tt&gt;. This can happen if the message is too long, because &lt;tt&gt;snprintf()&lt;/tt&gt; will return the total length that would have been printed, not the actual length, so it keeps growing.&lt;/p&gt;

&lt;p&gt;Two fixes are needed here:&lt;/p&gt;
&lt;ul class=&quot;alternate&quot; type=&quot;square&quot;&gt;
	&lt;li&gt;increase the buffer size so we don&apos;t overflow it, and userspace gets the records it wants&lt;/li&gt;
	&lt;li&gt;fix the code to stop printing, or compute the remaining buffer space differently so it doesn&apos;t become negative&lt;/li&gt;
&lt;/ul&gt;







&lt;p&gt;VVVVVVV DO NOT REMOVE LINES BELOW, Added by Maloo for auto-association VVVVVVV&lt;br/&gt;
sanity test_60b - CDEBUG_LIMIT not limiting messages (103)&lt;/p&gt;</description>
                <environment></environment>
        <key id="53809">LU-11566</key>
            <summary>sanity test_60aa: llog_print_cb()) not enough space for print log records</summary>
                <type id="1" iconUrl="https://jira.whamcloud.com/secure/viewavatar?size=xsmall&amp;avatarId=11303&amp;avatarType=issuetype">Bug</type>
                                            <priority id="4" iconUrl="https://jira.whamcloud.com/images/icons/priorities/minor.svg">Minor</priority>
                        <status id="5" iconUrl="https://jira.whamcloud.com/images/icons/statuses/resolved.png" description="A resolution has been taken, and it is awaiting verification by reporter. From here issues are either reopened, or are closed.">Resolved</status>
                    <statusCategory id="3" key="done" colorName="success"/>
                                    <resolution id="1">Fixed</resolution>
                                        <assignee username="bevans">Ben Evans</assignee>
                                    <reporter username="maloo">Maloo</reporter>
                        <labels>
                    </labels>
                <created>Wed, 24 Oct 2018 22:10:08 +0000</created>
                <updated>Tue, 1 Mar 2022 21:54:05 +0000</updated>
                            <resolved>Mon, 9 Sep 2019 18:46:42 +0000</resolved>
                                    <version>Lustre 2.12.0</version>
                    <version>Lustre 2.10.6</version>
                                    <fixVersion>Lustre 2.13.0</fixVersion>
                    <fixVersion>Lustre 2.12.3</fixVersion>
                                        <due></due>
                            <votes>0</votes>
                                    <watches>6</watches>
                                                                            <comments>
                            <comment id="235447" author="adilger" created="Wed, 24 Oct 2018 22:29:36 +0000"  >&lt;p&gt;This looks a bit worse than I thought. It seems that the current mechanism for printing the config logs is to print the whole log into a single buffer in the kernel. This means any config with a lot of records is going to overflow the 8192-byte buffer (I thought it was holding at most a single line of output).&lt;/p&gt;

&lt;p&gt;It seems there are a couple of options here:&lt;/p&gt;
&lt;ul class=&quot;alternate&quot; type=&quot;square&quot;&gt;
	&lt;li&gt;rework how the logs are printed to be one-per-line&lt;/li&gt;
	&lt;li&gt;allow the call to dump logs to be continued at the next record&lt;/li&gt;
	&lt;li&gt;completely change how logs are dumped, and use debugfs&lt;/li&gt;
&lt;/ul&gt;


&lt;p&gt;Probably the third option is best. This would involve creating a debugfs entry for each config record that generates the YAML-formatted output, then have &lt;tt&gt;llog_print&lt;/tt&gt; access that file (for compatibility, users could also then use &quot;&lt;tt&gt;lctl get_param mgs.param.&amp;lt;config&amp;gt;&lt;/tt&gt;&quot; or similar. &lt;/p&gt;

&lt;p&gt;Note that the MGS should only generate debugfs entries for well-known config files, like &lt;tt&gt;param&lt;/tt&gt;, &lt;tt&gt;&amp;lt;fsname&amp;gt;-MDTxxxx&lt;/tt&gt;, &lt;tt&gt;&amp;lt;fsname&amp;gt;-OSTxxxx&lt;/tt&gt;}, and whatever the sptlrpc file is named, and not any cruft in the CONFIGS directory such as backups or other files in that directory. &lt;/p&gt;</comment>
                            <comment id="235465" author="adilger" created="Thu, 25 Oct 2018 04:46:50 +0000"  >&lt;p&gt;Ben, it looks like this will affect your patch to backup/restore the config logs.  If the config log is large, then the supplied buffer will not be large enough to hold all of the config records.&lt;/p&gt;

&lt;p&gt;As a short term solution, it might be enough to increase &lt;tt&gt;MAX_IOC_BUFLEN&lt;/tt&gt; to e.g. 16KB, but I don&apos;t think that is a long-term solution.  See my previous comment about using debugfs for the longer-term solution.  I think that would be more suitable for 2.13, since it will involve some non-trivial changes to this code.&lt;/p&gt;</comment>
                            <comment id="235881" author="gerrit" created="Tue, 30 Oct 2018 05:10:03 +0000"  >&lt;p&gt;Andreas Dilger (adilger@whamcloud.com) uploaded a new patch: &lt;a href=&quot;https://review.whamcloud.com/33511&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://review.whamcloud.com/33511&lt;/a&gt;&lt;br/&gt;
Subject: &lt;a href=&quot;https://jira.whamcloud.com/browse/LU-11566&quot; title=&quot;sanity test_60aa: llog_print_cb()) not enough space for print log records&quot; class=&quot;issue-link&quot; data-issue-key=&quot;LU-11566&quot;&gt;&lt;del&gt;LU-11566&lt;/del&gt;&lt;/a&gt; utils: increase llog_print buffer size&lt;br/&gt;
Project: fs/lustre-release&lt;br/&gt;
Branch: master&lt;br/&gt;
Current Patch Set: 1&lt;br/&gt;
Commit: 0027b58de29e1d8574098eed892377ad15b6d0bf&lt;/p&gt;</comment>
                            <comment id="235975" author="simmonsja" created="Tue, 30 Oct 2018 23:49:43 +0000"  >&lt;p&gt;I do like the idea of using debugfs but remember its limited to root only. Will this matter to admins or for logging tools? In case we do need non root, but still privileged access, we can use the generic netlink API. For the generic netlink case we can send up to 32K size packets and each packet could contain a seq number so the packets can be pieced together. Just another option for the 2.13 window.&lt;/p&gt;</comment>
                            <comment id="236006" author="adilger" created="Wed, 31 Oct 2018 05:24:51 +0000"  >&lt;p&gt;We already have an ioctl, I don&apos;t think netlink is an improvement for this case.  For &lt;tt&gt;llog_print&lt;/tt&gt; this should really be a root-only operation anyway, so debugfs is OK.&lt;/p&gt;</comment>
                            <comment id="237279" author="adilger" created="Tue, 20 Nov 2018 22:03:50 +0000"  >&lt;p&gt;Ben, is there any chance you could look into this?  I think that without some kind of fix here, your (IMHO very useful) &lt;a href=&quot;https://jira.whamcloud.com/browse/LU-4939&quot; title=&quot;Need to be able to sanely query and change MGS configuration information&quot; class=&quot;issue-link&quot; data-issue-key=&quot;LU-4939&quot;&gt;&lt;del&gt;LU-4939&lt;/del&gt;&lt;/a&gt; patch to allow config backup/restore will only be useful for small configurations that don&apos;t have very many config records.&lt;/p&gt;</comment>
                            <comment id="237281" author="bevans" created="Tue, 20 Nov 2018 22:07:14 +0000"  >&lt;p&gt;Yep, it&apos;s on my list of things to do.&#160; I think the short-term solution is to read each file in chunks.&#160; Long term, debugfs should work fine.&lt;/p&gt;</comment>
                            <comment id="237284" author="adilger" created="Tue, 20 Nov 2018 22:22:19 +0000"  >&lt;p&gt;If you can work up a mechanism to read the file in chunks, that is fine too. Probably the easiest would be to print a single record per call, so that the buffer is always large enough. A bit more complex would be to pack multiple whole records into the buffer, and stop when the last one doesn&apos;t fit. Splitting a single record across multiple calls would be hard to handle in both the kernel and userspace.&lt;/p&gt;

&lt;p&gt;Strangely, I didn&apos;t know that &lt;tt&gt;llog_print&lt;/tt&gt; allows specifying the start and end record, so that makes the solution relatively easy to implement. Just specify a series of start/end pairs internally until there are no more records. It would be relatively safe to assume e.g. 256 bytes/record and then plan accordingly.&lt;/p&gt;

&lt;p&gt;Note that there is a minor bug in &lt;tt&gt;jt_llog_print()&lt;/tt&gt; in that it doesn&apos;t allow specifying only the starting record (i.e. &lt;tt&gt;argc == 3&lt;/tt&gt;). There is also a small bug in the &lt;tt&gt;lctl-llog_print.8&lt;/tt&gt; man page, in that it should show &quot;&lt;tt&gt;lctl llog_print &amp;lt;logname&amp;gt; [start_index &lt;span class=&quot;error&quot;&gt;&amp;#91;end_index&amp;#93;&lt;/span&gt;]&quot;&lt;/tt&gt; (i.e. &quot;&lt;tt&gt;end_index&quot;&lt;/tt&gt; is only allowed if &quot;&lt;tt&gt;start_index&quot;&lt;/tt&gt; is specified, instead of implying that &quot;&lt;tt&gt;end_index&lt;/tt&gt;&quot; can be used independently). It would also be useful if&#160;&lt;tt&gt;llog_print&lt;/tt&gt; checked for named arguments like &lt;tt&gt;&amp;#45;&amp;#45;start&lt;/tt&gt; and &lt;tt&gt;&amp;#45;&amp;#45;end&lt;/tt&gt; (or similar) instead of depending on positional parameters, since that makes parsing more complex as new options are added.&lt;/p&gt;</comment>
                            <comment id="238268" author="gerrit" created="Mon, 10 Dec 2018 11:46:43 +0000"  >&lt;p&gt;Andreas Dilger (adilger@whamcloud.com) uploaded a new patch: &lt;a href=&quot;https://review.whamcloud.com/33815&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://review.whamcloud.com/33815&lt;/a&gt;&lt;br/&gt;
Subject: &lt;a href=&quot;https://jira.whamcloud.com/browse/LU-11566&quot; title=&quot;sanity test_60aa: llog_print_cb()) not enough space for print log records&quot; class=&quot;issue-link&quot; data-issue-key=&quot;LU-11566&quot;&gt;&lt;del&gt;LU-11566&lt;/del&gt;&lt;/a&gt; utils: lctl llog_print for large configurations&lt;br/&gt;
Project: fs/lustre-release&lt;br/&gt;
Branch: master&lt;br/&gt;
Current Patch Set: 1&lt;br/&gt;
Commit: 039ed418fa9a7e075af8e3e45b22776227259abd&lt;/p&gt;</comment>
                            <comment id="238593" author="gerrit" created="Fri, 14 Dec 2018 04:45:23 +0000"  >&lt;p&gt;Andreas Dilger (adilger@whamcloud.com) uploaded a new patch: &lt;a href=&quot;https://review.whamcloud.com/33863&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://review.whamcloud.com/33863&lt;/a&gt;&lt;br/&gt;
Subject: &lt;a href=&quot;https://jira.whamcloud.com/browse/LU-11566&quot; title=&quot;sanity test_60aa: llog_print_cb()) not enough space for print log records&quot; class=&quot;issue-link&quot; data-issue-key=&quot;LU-11566&quot;&gt;&lt;del&gt;LU-11566&lt;/del&gt;&lt;/a&gt; utils: fix lctl llog_print for large configs&lt;br/&gt;
Project: fs/lustre-release&lt;br/&gt;
Branch: b2_10&lt;br/&gt;
Current Patch Set: 1&lt;br/&gt;
Commit: 79d5c1f0aac2459070c0837835a2aac3e75ec4c5&lt;/p&gt;</comment>
                            <comment id="239665" author="gerrit" created="Thu, 10 Jan 2019 01:30:43 +0000"  >&lt;p&gt;Andreas Dilger (adilger@whamcloud.com) uploaded a new patch: &lt;a href=&quot;https://review.whamcloud.com/34004&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://review.whamcloud.com/34004&lt;/a&gt;&lt;br/&gt;
Subject: &lt;a href=&quot;https://jira.whamcloud.com/browse/LU-11566&quot; title=&quot;sanity test_60aa: llog_print_cb()) not enough space for print log records&quot; class=&quot;issue-link&quot; data-issue-key=&quot;LU-11566&quot;&gt;&lt;del&gt;LU-11566&lt;/del&gt;&lt;/a&gt; utils: improve usage/docs for lctl llog commands&lt;br/&gt;
Project: fs/lustre-release&lt;br/&gt;
Branch: master&lt;br/&gt;
Current Patch Set: 1&lt;br/&gt;
Commit: 32082e82469176652f90b261457993708aa4e1d6&lt;/p&gt;</comment>
                            <comment id="240927" author="gerrit" created="Wed, 30 Jan 2019 02:40:37 +0000"  >&lt;p&gt;Oleg Drokin (green@whamcloud.com) merged in patch &lt;a href=&quot;https://review.whamcloud.com/33815/&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://review.whamcloud.com/33815/&lt;/a&gt;&lt;br/&gt;
Subject: &lt;a href=&quot;https://jira.whamcloud.com/browse/LU-11566&quot; title=&quot;sanity test_60aa: llog_print_cb()) not enough space for print log records&quot; class=&quot;issue-link&quot; data-issue-key=&quot;LU-11566&quot;&gt;&lt;del&gt;LU-11566&lt;/del&gt;&lt;/a&gt; utils: fix lctl llog_print for large configs&lt;br/&gt;
Project: fs/lustre-release&lt;br/&gt;
Branch: master&lt;br/&gt;
Current Patch Set: &lt;br/&gt;
Commit: 3783aa285b15a811081a8de829d52f7f83e91209&lt;/p&gt;</comment>
                            <comment id="242590" author="gerrit" created="Sat, 23 Feb 2019 05:10:39 +0000"  >&lt;p&gt;Oleg Drokin (green@whamcloud.com) merged in patch &lt;a href=&quot;https://review.whamcloud.com/33863/&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://review.whamcloud.com/33863/&lt;/a&gt;&lt;br/&gt;
Subject: &lt;a href=&quot;https://jira.whamcloud.com/browse/LU-11566&quot; title=&quot;sanity test_60aa: llog_print_cb()) not enough space for print log records&quot; class=&quot;issue-link&quot; data-issue-key=&quot;LU-11566&quot;&gt;&lt;del&gt;LU-11566&lt;/del&gt;&lt;/a&gt; utils: fix lctl llog_print for large configs&lt;br/&gt;
Project: fs/lustre-release&lt;br/&gt;
Branch: b2_10&lt;br/&gt;
Current Patch Set: &lt;br/&gt;
Commit: a8abec1d666c92eb5003e020488f10d10da82787&lt;/p&gt;</comment>
                            <comment id="244798" author="gerrit" created="Thu, 28 Mar 2019 08:51:16 +0000"  >&lt;p&gt;Andreas Dilger (adilger@whamcloud.com) uploaded a new patch: &lt;a href=&quot;https://review.whamcloud.com/34523&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://review.whamcloud.com/34523&lt;/a&gt;&lt;br/&gt;
Subject: &lt;a href=&quot;https://jira.whamcloud.com/browse/LU-11566&quot; title=&quot;sanity test_60aa: llog_print_cb()) not enough space for print log records&quot; class=&quot;issue-link&quot; data-issue-key=&quot;LU-11566&quot;&gt;&lt;del&gt;LU-11566&lt;/del&gt;&lt;/a&gt; llog: consolidate argument validation&lt;br/&gt;
Project: fs/lustre-release&lt;br/&gt;
Branch: master&lt;br/&gt;
Current Patch Set: 1&lt;br/&gt;
Commit: eb63a2f319a8e087f9223db3c41f00bc3f126747&lt;/p&gt;</comment>
                            <comment id="245357" author="gerrit" created="Mon, 8 Apr 2019 05:35:29 +0000"  >&lt;p&gt;Oleg Drokin (green@whamcloud.com) merged in patch &lt;a href=&quot;https://review.whamcloud.com/34004/&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://review.whamcloud.com/34004/&lt;/a&gt;&lt;br/&gt;
Subject: &lt;a href=&quot;https://jira.whamcloud.com/browse/LU-11566&quot; title=&quot;sanity test_60aa: llog_print_cb()) not enough space for print log records&quot; class=&quot;issue-link&quot; data-issue-key=&quot;LU-11566&quot;&gt;&lt;del&gt;LU-11566&lt;/del&gt;&lt;/a&gt; utils: improve usage/docs for lctl llog commands&lt;br/&gt;
Project: fs/lustre-release&lt;br/&gt;
Branch: master&lt;br/&gt;
Current Patch Set: &lt;br/&gt;
Commit: 2ec11b04dd76ea176ba9c76f809f576a04dafc1a&lt;/p&gt;</comment>
                            <comment id="247015" author="gerrit" created="Fri, 10 May 2019 22:39:36 +0000"  >&lt;p&gt;Andreas Dilger (adilger@whamcloud.com) uploaded a new patch: &lt;a href=&quot;https://review.whamcloud.com/34850&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://review.whamcloud.com/34850&lt;/a&gt;&lt;br/&gt;
Subject: &lt;a href=&quot;https://jira.whamcloud.com/browse/LU-11566&quot; title=&quot;sanity test_60aa: llog_print_cb()) not enough space for print log records&quot; class=&quot;issue-link&quot; data-issue-key=&quot;LU-11566&quot;&gt;&lt;del&gt;LU-11566&lt;/del&gt;&lt;/a&gt; utils: fix lctl llog_print for large configs&lt;br/&gt;
Project: fs/lustre-release&lt;br/&gt;
Branch: b2_12&lt;br/&gt;
Current Patch Set: 1&lt;br/&gt;
Commit: ca403753ec60503ab599fb7292db95789bda858e&lt;/p&gt;</comment>
                            <comment id="248783" author="gerrit" created="Sat, 8 Jun 2019 02:33:04 +0000"  >&lt;p&gt;Oleg Drokin (green@whamcloud.com) merged in patch &lt;a href=&quot;https://review.whamcloud.com/34850/&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://review.whamcloud.com/34850/&lt;/a&gt;&lt;br/&gt;
Subject: &lt;a href=&quot;https://jira.whamcloud.com/browse/LU-11566&quot; title=&quot;sanity test_60aa: llog_print_cb()) not enough space for print log records&quot; class=&quot;issue-link&quot; data-issue-key=&quot;LU-11566&quot;&gt;&lt;del&gt;LU-11566&lt;/del&gt;&lt;/a&gt; utils: fix lctl llog_print for large configs&lt;br/&gt;
Project: fs/lustre-release&lt;br/&gt;
Branch: b2_12&lt;br/&gt;
Current Patch Set: &lt;br/&gt;
Commit: c1b11bf102ea73860fcb65afceb99db5b4fcc2e2&lt;/p&gt;</comment>
                            <comment id="254410" author="pfarrell" created="Mon, 9 Sep 2019 18:46:42 +0000"  >&lt;p&gt;Main patches landed, moved remaining cleanup to&#160;&lt;a href=&quot;https://jira.whamcloud.com/browse/LU-12737&quot; title=&quot;consolidate argument validation in llog&quot; class=&quot;issue-link&quot; data-issue-key=&quot;LU-12737&quot;&gt;LU-12737&lt;/a&gt;.&lt;/p&gt;</comment>
                            <comment id="326034" author="gerrit" created="Fri, 11 Feb 2022 17:54:18 +0000"  >&lt;p&gt;&quot;Etienne AUJAMES &amp;lt;eaujames@ddn.com&amp;gt;&quot; uploaded a new patch: &lt;a href=&quot;https://review.whamcloud.com/46510&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://review.whamcloud.com/46510&lt;/a&gt;&lt;br/&gt;
Subject: &lt;a href=&quot;https://jira.whamcloud.com/browse/LU-11566&quot; title=&quot;sanity test_60aa: llog_print_cb()) not enough space for print log records&quot; class=&quot;issue-link&quot; data-issue-key=&quot;LU-11566&quot;&gt;&lt;del&gt;LU-11566&lt;/del&gt;&lt;/a&gt; utils: improve usage/docs for lctl llog commands&lt;br/&gt;
Project: fs/lustre-release&lt;br/&gt;
Branch: b2_12&lt;br/&gt;
Current Patch Set: 1&lt;br/&gt;
Commit: af53bb19913ea41a9fdbee386cb5e1ef3eaf0cae&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10011">
                    <name>Related</name>
                                            <outwardlinks description="is related to ">
                                        <issuelink>
            <issuekey id="53297">LU-11373</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="24319">LU-4939</issuekey>
        </issuelink>
                            </outwardlinks>
                                                                <inwardlinks description="is related to">
                                        <issuelink>
            <issuekey id="55613">LU-12285</issuekey>
        </issuelink>
                            </inwardlinks>
                                    </issuelinktype>
                    </issuelinks>
                <attachments>
                    </attachments>
                <subtasks>
                    </subtasks>
                <customfields>
                                                                                                                                                                                            <customfield id="customfield_10890" key="com.atlassian.jira.plugins.jira-development-integration-plugin:devsummary">
                        <customfieldname>Development</customfieldname>
                        <customfieldvalues>
                            
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                        <customfield id="customfield_10390" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>1|i00527:</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10090" key="com.pyxis.greenhopper.jira:gh-global-rank">
                        <customfieldname>Rank (Obsolete)</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>9223372036854775807</customfieldvalue>
                        </customfieldvalues>
                    </customfield>
                                                                                            <customfield id="customfield_10060" key="com.atlassian.jira.plugin.system.customfieldtypes:select">
                        <customfieldname>Severity</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="10022"><![CDATA[3]]></customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                        </customfields>
    </item>
</channel>
</rss>