[OpenAFS] compile fails kernel version 4.4.0-1-default
Edgecombe, Jason
jwedgeco@uncc.edu
Wed, 2 Mar 2016 13:25:04 -0500
--001a1142702c5d712f052d15015a
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Can the OpenAFS folks work on kAFS? I was under the impression that they
were "tainted" by having read the IBM-provided code.
---------------------------------------------------------------------------
Jason Edgecombe | Linux Administrator
UNC Charlotte | The William States Lee College of Engineering
9201 University City Blvd. | Charlotte, NC 28223-0001
Phone: 704-687-1943
jwedgeco@uncc.edu | http://engr.uncc.edu | Facebook
---------------------------------------------------------------------------
If you are not the intended recipient of this transmission or a person
responsible for delivering it to the intended recipient, any disclosure,
copying, distribution, or other use of any of the information in this
transmission is strictly prohibited. If you have received this transmission
in error, please notify me immediately by reply e-mail or by telephone at
704-687-1943. Thank you.
On Wed, Mar 2, 2016 at 10:21 AM, Brandon Allbery <ballbery@sinenomine.net>
wrote:
> Not until someone adds pioctl support to it.
>
> -----Original Message-----
> From: openafs-info-admin@openafs.org [mailto:
> openafs-info-admin@openafs.org] On Behalf Of Ted Creedon
> Sent: Wednesday, March 2, 2016 10:13 AM
> Cc: openafs-info@openafs.org
> Subject: Re: [OpenAFS] compile fails kernel version 4.4.0-1-default
>
> Would it be appropriate to force a move to kafs now?
>
> ________________________________________
> From: openafs-info-admin@openafs.org <openafs-info-admin@openafs.org> on
> behalf of Benjamin Kaduk <kaduk@MIT.EDU>
> Sent: Tuesday, March 1, 2016 7:31 PM
> To: Michael La=C3=9F
> Cc: OpenAFS-info@openafs.org
> Subject: Re: [OpenAFS] compile fails kernel version 4.4.0-1-default
>
> On Tue, 1 Mar 2016, Michael La=C3=9F wrote:
>
> > Hi!
> >
> > Am 23.01.2016 um 18:22 schrieb Benjamin Kaduk <kaduk@MIT.EDU>:
> > >
> > > Though the patches linked there are sufficient to permit the build
> > > to complete, there are some more subtle behavior changes in the
> > > kernel in that some of the splice functions will now return
> > > ERESTARTSYS if there is any signal pending in the current process.
> > > In particular, there are presumed to be codepaths for which we do
> > > not have proper error handling, that could lead to data loss.
> > > Further analysis is needed (which I am not prepared to undertake at
> present).
> >
> > It seems like you were spot on with this. Some Arch Linux users have
> been brave enough to test OpenAFS with these patches on Linux 4.4. One
> reported a data corruption issue now. Quote from
> https://aur.archlinux.org/packages/openafs/:
> >
> > > I tried the patch and I get problems. When I do checkout a different
> branch of my software from a git repository things fail and I'm left with=
a
> corrupted workspace. The log files shows the following message:
> > > kernel: afs: Lost contact with file server ... in cell ... (code
> > > -512) (all multi-homed ip addresses down for the server)
> > > kernel: afs: failed to store file (network problems)
> > > kernel: afs: file server ... in cell ... is back up (code 0)
> > > (multi-homed address; other same-host interfaces may still be down)
> >
> >
> > Guess what error core -512 is=E2=80=A6 Yep, it=E2=80=99s -ERESTARTSYS.
> >
> > So there is definitely some additional work required for Linux 4.4.
>
> Hi Michael,
>
> Thank you for reporting this back to the list. To the list members:
>
> I would like to point out that no openafs developer has stated that they
> are working on this issue, and it appears that a proper fix will require
> modifications through many different parts of the cache manager; that is,
> it will be an invasive change that requires substantial development
> effort. There is a real risk that OpenAFS will not be able to support
> kernels from the 4.4 series and newer -- the openafs package is slated fo=
r
> removal from Debian testing in just three weeks.
>
> If there are sites that will be adversely affected by the lack of a
> functioning openafs client for linux kernel 4.4 or newer, it will be easi=
er
> if they can contribute resources now, rather than months from now when
> these kernels make their way into the linux distributions deployed at the=
se
> sites.
>
> -Ben
> _______________________________________________
> OpenAFS-info mailing list
> OpenAFS-info@openafs.org
> https://lists.openafs.org/mailman/listinfo/openafs-info
>
--001a1142702c5d712f052d15015a
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr"><div class=3D"gmail_default" style=3D"font-family:arial,he=
lvetica,sans-serif">Can the OpenAFS folks work on kAFS? I was under the imp=
ression that they were "tainted" by having read the IBM-provided =
code.<br></div></div><div class=3D"gmail_extra"><br clear=3D"all"><div><div=
class=3D"gmail_signature"><div dir=3D"ltr">-------------------------------=
--------------------------------------------<br>
Jason Edgecombe | Linux Administrator<br>
UNC Charlotte | The William States Lee College of Engineering<br>
9201 University City Blvd. | Charlotte, NC 28223-0001<br>
Phone: <a href=3D"tel:704-687-1943" value=3D"+17046871943" target=3D"_blank=
"><span>704</span>-<span>687</span>-<span>1943</span></a><br>
<a href=3D"mailto:jwedgeco@uncc.edu" target=3D"_blank">jwedgeco@uncc.edu</a=
> | <a href=3D"http://engr.uncc.edu" target=3D"_blank">http://engr.uncc.edu=
</a> | =C2=A0Facebook<br>
---------------------------------------------------------------------------=
<br>
If you are not the intended recipient of this transmission or a person=20
responsible for delivering it to the intended recipient, any disclosure,
copying, distribution, or other use of any of the information in this=20
transmission is strictly prohibited. If you have received this=20
transmission in error, please notify me immediately by reply e-mail or=20
by telephone at<br>
<a href=3D"tel:704-687-1943" value=3D"+17046871943" target=3D"_blank"><span=
>704</span>-<span>687</span>-<span>1943</span></a>.=C2=A0 Thank you.</div><=
/div></div>
<br><div class=3D"gmail_quote">On Wed, Mar 2, 2016 at 10:21 AM, Brandon All=
bery <span dir=3D"ltr"><<a href=3D"mailto:ballbery@sinenomine.net" targe=
t=3D"_blank">ballbery@sinenomine.net</a>></span> wrote:<br><blockquote c=
lass=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;=
padding-left:1ex">Not until someone adds pioctl support to it.<br>
<div class=3D"HOEnZb"><div class=3D"h5"><br>
-----Original Message-----<br>
From: <a href=3D"mailto:openafs-info-admin@openafs.org">openafs-info-admin@=
openafs.org</a> [mailto:<a href=3D"mailto:openafs-info-admin@openafs.org">o=
penafs-info-admin@openafs.org</a>] On Behalf Of Ted Creedon<br>
Sent: Wednesday, March 2, 2016 10:13 AM<br>
Cc: <a href=3D"mailto:openafs-info@openafs.org">openafs-info@openafs.org</a=
><br>
Subject: Re: [OpenAFS] compile fails kernel version 4.4.0-1-default<br>
<br>
Would it be appropriate to force a move to kafs now?<br>
<br>
________________________________________<br>
From: <a href=3D"mailto:openafs-info-admin@openafs.org">openafs-info-admin@=
openafs.org</a> <<a href=3D"mailto:openafs-info-admin@openafs.org">opena=
fs-info-admin@openafs.org</a>> on behalf of Benjamin Kaduk <<a href=
=3D"mailto:kaduk@MIT.EDU">kaduk@MIT.EDU</a>><br>
Sent: Tuesday, March 1, 2016 7:31 PM<br>
To: Michael La=C3=9F<br>
Cc: <a href=3D"mailto:OpenAFS-info@openafs.org">OpenAFS-info@openafs.org</a=
><br>
Subject: Re: [OpenAFS] compile fails kernel version 4.4.0-1-default<br>
<br>
On Tue, 1 Mar 2016, Michael La=C3=9F wrote:<br>
<br>
> Hi!<br>
><br>
> Am 23.01.2016 um 18:22 schrieb Benjamin Kaduk <<a href=3D"mailto:ka=
duk@MIT.EDU">kaduk@MIT.EDU</a>>:<br>
> ><br>
> > Though the patches linked there are sufficient to permit the buil=
d<br>
> > to complete, there are some more subtle behavior changes in the<b=
r>
> > kernel in that some of the splice functions will now return<br>
> > ERESTARTSYS if there is any signal pending in the current process=
.<br>
> > In particular, there are presumed to be codepaths for which we do=
<br>
> > not have proper error handling, that could lead to data loss.<br>
> > Further analysis is needed (which I am not prepared to undertake =
at present).<br>
><br>
> It seems like you were spot on with this. Some Arch Linux users have b=
een brave enough to test OpenAFS with these patches on Linux 4.4. One repor=
ted a data corruption issue now. Quote from <a href=3D"https://aur.archlinu=
x.org/packages/openafs/" rel=3D"noreferrer" target=3D"_blank">https://aur.a=
rchlinux.org/packages/openafs/</a>:<br>
><br>
> > I tried the patch and I get problems. When I do checkout a differ=
ent branch of my software from a git repository things fail and I'm lef=
t with a corrupted workspace. The log files shows the following message:<br=
>
> > kernel: afs: Lost contact with file server ... in cell ... (code<=
br>
> > -512) (all multi-homed ip addresses down for the server)<br>
> > kernel: afs: failed to store file (network problems)<br>
> > kernel: afs: file server ... in cell ... is back up (code 0)<br>
> > (multi-homed address; other same-host interfaces may still be dow=
n)<br>
><br>
><br>
> Guess what error core -512 is=E2=80=A6 Yep, it=E2=80=99s -ERESTARTSYS.=
<br>
><br>
> So there is definitely some additional work required for Linux 4.4.<br=
>
<br>
Hi Michael,<br>
<br>
Thank you for reporting this back to the list.=C2=A0 To the list members:<b=
r>
<br>
I would like to point out that no openafs developer has stated that they ar=
e working on this issue, and it appears that a proper fix will require modi=
fications through many different parts of the cache manager; that is, it wi=
ll be an invasive change that requires substantial development effort.=C2=
=A0 There is a real risk that OpenAFS will not be able to support kernels f=
rom the 4.4 series and newer -- the openafs package is slated for removal f=
rom Debian testing in just three weeks.<br>
<br>
If there are sites that will be adversely affected by the lack of a functio=
ning openafs client for linux kernel 4.4 or newer, it will be easier if the=
y can contribute resources now, rather than months from now when these kern=
els make their way into the linux distributions deployed at these sites.<br=
>
<br>
-Ben<br>
_______________________________________________<br>
OpenAFS-info mailing list<br>
<a href=3D"mailto:OpenAFS-info@openafs.org">OpenAFS-info@openafs.org</a><br=
>
<a href=3D"https://lists.openafs.org/mailman/listinfo/openafs-info" rel=3D"=
noreferrer" target=3D"_blank">https://lists.openafs.org/mailman/listinfo/op=
enafs-info</a><br>
</div></div></blockquote></div><br></div>
--001a1142702c5d712f052d15015a--