Hi, you can try these patches and check their respective Jira entry: git cherry-pick --strategy=recursive -X theirs 97823e65efd85bb2db325232584d65646be5644f # for centos 7.8 LU-13347 git cherry-pick --strategy=recursive -X theirs 851ba18ee0424a3a4bf27d54d0c1af20eaf04ed6 # for centos 7.8 LU-13347 git cherry-pick --strategy=recursive -X theirs 14a18654a64ae05a94a4394d53b030ce91357e9a # for centos 7.8 LU-12904
It seems 14a186 is directly what should fix your specific error, but the other one seems to be required when I tried to build it. On Thu, May 14, 2020 at 7:11 PM Hebenstreit, Michael < [email protected]> wrote: > Trying to compile for new RH kernel I got some errors, I think because of > https://patchwork.kernel.org/patch/11061873/. My solution was this patch > > $ cat > /admin/work/buildenv_rh7/OFED/mlnx-5.0-2.1.8.0-1127.8.2-2.10.8/extra/gss_svc_upcall.patch > --- lustre/ptlrpc/gss/gss_svc_upcall.c.orig 2020-05-14 > 15:58:38.000000000 -0600 > +++ lustre/ptlrpc/gss/gss_svc_upcall.c 2020-05-14 16:12:55.000000000 -0600 > @@ -1175,14 +1175,14 @@ > * drop the request direclty, thus lead to unnecessary recovery > time. > * here we wait at miximum 1.5 seconds. */ > for (i = 0; i < 6; i++) { > - if (atomic_read(&rsi_cache.readers) > 0) > + if (atomic_read(&rsi_cache.writers) > 0) > break; > set_current_state(TASK_UNINTERRUPTIBLE); > LASSERT(msecs_to_jiffies(MSEC_PER_SEC) >= 4); > schedule_timeout(msecs_to_jiffies(MSEC_PER_SEC / 4)); > } > > - if (atomic_read(&rsi_cache.readers) == 0) > + if (atomic_read(&rsi_cache.writers) == 0) > CWARN("Init channel is not opened by lsvcgssd, following " > "request might be dropped until lsvcgssd is > active\n"); > > > Does that look correct? > > Thanks > Michael > > ------------------------------------------------------------------------ > Michael Hebenstreit Senior Cluster Architect > Intel Corporation, MS: RR1-105/H14 TSACG > 1600 Rio Rancho Blvd SE Tel.: +1 505-794-3144 > Rio Rancho, NM 87124 > UNITED STATES E-mail: [email protected] > > > _______________________________________________ > lustre-discuss mailing list > [email protected] > http://lists.lustre.org/listinfo.cgi/lustre-discuss-lustre.org >
_______________________________________________ lustre-discuss mailing list [email protected] http://lists.lustre.org/listinfo.cgi/lustre-discuss-lustre.org
