config GFS2_FS
	tristate "GFS2 file system support"
	depends on (64BIT || LBDAF)
	select FS_POSIX_ACL
	select CRC32
	select QUOTACTL
	help
	  A cluster filesystem.

	  Allows a cluster of computers to simultaneously use a block device
	  that is shared between them (with FC, iSCSI, NBD, etc...).  GFS reads
	  and writes to the block device like a local filesystem, but also uses
	  a lock module to allow the computers coordinate their I/O so
	  filesystem consistency is maintained.  One of the nifty features of
	  GFS is perfect consistency -- changes made to the filesystem on one
	  machine show up immediately on all other machines in the cluster.

	  To use the GFS2 filesystem in a cluster, you will need to enable
	  the locking module below. Documentation and utilities for GFS2 can
	  be found here: http://sources.redhat.com/cluster

	  The "nolock" lock module is now built in to GFS2 by default. If
	  you want to use the DLM, be sure to enable IPv4/6 networking.

config GFS2_FS_LOCKING_DLM
	bool "GFS2 DLM locking"
	depends on (GFS2_FS!=n) && NET && INET && (IPV6 || IPV6=n) && \
		CONFIGFS_FS && SYSFS && (DLM=y || DLM=GFS2_FS)
	help
	  Multiple node locking module for GFS2

	  Most users of GFS2 will require this. It provides the locking
	  interface between GFS2 and the DLM, which is required to use GFS2
	  in a cluster environment.
ion>
</select> <input type='submit' value='switch'/></form></td></tr>
<tr><td class='sub'>net-next plumbings</td><td class='sub right'>Tobias Klauser</td></tr></table>
<table class='tabs'><tr><td>
<a href='/cgit.cgi/linux/net-next.git/?h=nds-private-remove'>summary</a><a href='/cgit.cgi/linux/net-next.git/refs/?h=nds-private-remove&amp;id=4ff0620354f2b39b9fe2a91c22c4de9d1fba0c8e'>refs</a><a class='active' href='/cgit.cgi/linux/net-next.git/log/tools?h=nds-private-remove&amp;showmsg=1'>log</a><a href='/cgit.cgi/linux/net-next.git/tree/tools?h=nds-private-remove&amp;id=4ff0620354f2b39b9fe2a91c22c4de9d1fba0c8e'>tree</a><a href='/cgit.cgi/linux/net-next.git/commit/tools?h=nds-private-remove&amp;id=4ff0620354f2b39b9fe2a91c22c4de9d1fba0c8e'>commit</a><a href='/cgit.cgi/linux/net-next.git/diff/tools?h=nds-private-remove&amp;id=4ff0620354f2b39b9fe2a91c22c4de9d1fba0c8e'>diff</a></td><td class='form'><form class='right' method='get' action='/cgit.cgi/linux/net-next.git/log/tools'>
<input type='hidden' name='h' value='nds-private-remove'/><input type='hidden' name='id' value='4ff0620354f2b39b9fe2a91c22c4de9d1fba0c8e'/><input type='hidden' name='showmsg' value='1'/><select name='qt'>
<option value='grep'>log msg</option>
<option value='author'>author</option>
<option value='committer'>committer</option>
<option value='range'>range</option>
</select>
<input class='txt' type='search' size='10' name='q' value=''/>
<input type='submit' value='search'/>
</form>
</td></tr></table>
<div class='path'>path: <a href='/cgit.cgi/linux/net-next.git/log/?h=nds-private-remove&amp;id=4ff0620354f2b39b9fe2a91c22c4de9d1fba0c8e&amp;showmsg=1'>root</a>/<a href='/cgit.cgi/linux/net-next.git/log/tools?h=nds-private-remove&amp;id=4ff0620354f2b39b9fe2a91c22c4de9d1fba0c8e&amp;showmsg=1'>tools</a></div><div class='content'><table class='list nowrap'><tr class='nohover'><th class='left'>Age</th><th class='left'>Commit message (<a href='/cgit.cgi/linux/net-next.git/log/tools?h=nds-private-remove&amp;id=4ff0620354f2b39b9fe2a91c22c4de9d1fba0c8e'>Collapse</a>)</th><th class='left'>Author</th><th class='left'>Files</th><th class='left'>Lines</th></tr>
<tr class='logheader'><td><span title='2017-02-06 22:50:04 -0500'>2017-02-06</span></td><td class='logsubject'><a href='/cgit.cgi/linux/net-next.git/commit/tools?h=nds-private-remove&amp;id=63dfef75ed75364901d7caa52c6420cec3e73519'>bpf: enable verifier to add 0 to packet ptr</a></td><td>William Tu</td><td>1</td><td><span class='deletions'>-0</span>/<span class='insertions'>+23</span></td></tr>
<tr class='nohover-highlight'><td/><td colspan='5' class='logmsg'>
The patch fixes the case when adding a zero value to the packet
pointer.  The zero value could come from src_reg equals type
BPF_K or CONST_IMM.  The patch fixes both, otherwise the verifer
reports the following error:
  [...]
    R0=imm0,min_value=0,max_value=0
    R1=pkt(id=0,off=0,r=4)
    R2=pkt_end R3=fp-12
    R4=imm4,min_value=4,max_value=4
    R5=pkt(id=0,off=4,r=4)
  269: (bf) r2 = r0     // r2 becomes imm0
  270: (77) r2 &gt;&gt;= 3
  271: (bf) r4 = r1     // r4 becomes pkt ptr
  272: (0f) r4 += r2    // r4 += 0
  addition of negative constant to packet pointer is not allowed

Signed-off-by: William Tu &lt;u9012063@gmail.com&gt;
Signed-off-by: Mihai Budiu &lt;mbudiu@vmware.com&gt;
Cc: Daniel Borkmann &lt;daniel@iogearbox.net&gt;
Cc: Alexei Starovoitov &lt;ast@kernel.org&gt;
Acked-by: Daniel Borkmann &lt;daniel@iogearbox.net&gt;
Acked-by: Alexei Starovoitov &lt;ast@kernel.org&gt;
Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;


</td></tr>
<tr class='logheader'><td><span title='2017-02-06 22:35:58 -0500'>2017-02-06</span></td><td class='logsubject'><a href='/cgit.cgi/linux/net-next.git/commit/tools?h=nds-private-remove&amp;id=29200c199cc9bde59033ab30fcc40b6c8ae630b0'>bpf: test for AND edge cases</a></td><td>Josef Bacik</td><td>1</td><td><span class='deletions'>-0</span>/<span class='insertions'>+55</span></td></tr>
<tr class='nohover-highlight'><td/><td colspan='5' class='logmsg'>
These two tests are based on the work done for f23cc643f9ba.  The first test is
just a basic one to make sure we don't allow AND'ing negative values, even if it
would result in a valid index for the array.  The second is a cleaned up version
of the original testcase provided by Jann Horn that resulted in the commit.

Acked-by: Alexei Starovoitov &lt;ast@kernel.org&gt;
Acked-by: Daniel Borkmann &lt;daniel@iogearbox.net&gt;
Signed-off-by: Josef Bacik &lt;jbacik@fb.com&gt;
Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;


</td></tr>