Hi,
Function gfs2_ail_empty_gl is part of the sync process (go_sync) for
a glock. The go_sync glop is called to sync the metadata for a glock
so we can, in good conscience, tell dlm to release the lock to another
node. Its goal is not only to sync the metadata for the glock, but
also to ensure
On Fri, May 15, 2020 at 04:20:02PM +0100, David Howells wrote:
> Christoph Hellwig wrote:
>
> > > The advantage on using kernel_setsockopt here is that sctp module will
> > > only be loaded if dlm actually creates a SCTP socket. With this
> > > change, sctp will be loaded on setups that may not
Christoph Hellwig wrote:
> > The advantage on using kernel_setsockopt here is that sctp module will
> > only be loaded if dlm actually creates a SCTP socket. With this
> > change, sctp will be loaded on setups that may not be actually using
> > it. It's a quite big module and might expose the
Christoph Hellwig wrote:
> > > + ip_sock_set_mtu_discover(conn->params.local->socket->sk,
> > > + IP_PMTUDISC_DONT);
> >
> > Um... The socket in question could be an AF_INET6 socket, not an AF_INET4
> > socket - I presume it will work in that case. If so:
>
>
Christoph Hellwig wrote:
> > Looks good - but you do need to add this to
> > Documentation/networking/rxrpc.txt
> > also, thanks.
>
> That file doesn't exist, instead we now have a
> cumentation/networking/rxrpc.rst in weird markup.
Yeah - that's only in net/next thus far.
> Where do you
Looking at __sys_setsockopt() I noticed that the BPF intercept
can also cause set_fs(KERNEL_DS) be set in order to pass a
modified buffer into the actual setsockopt() code.
If that functionality is to be kept then the underlying
protocol specific code needs changing to accept a kernel buffer.
