* nft: parser problem, can use mark as datatype in sets and maps @ 2015-08-10 13:48 Andreas Schultz 2015-08-10 17:09 ` Pablo Neira Ayuso 0 siblings, 1 reply; 8+ messages in thread From: Andreas Schultz @ 2015-08-10 13:48 UTC (permalink / raw) To: netfilter-devel; +Cc: Pablo Neira Ayuso Hi, The data type definition for mark and the general idea of the parser indicate that the following nft statements should work: # nft add map filter MAP1 { type ipv4_addr : mark\; } # nft add set filter SET1 { type mark\; } However, both fail with a similar error message: <cmdline>:1:40-43: Error: syntax error, unexpected mark, expecting string add map filter MAP1 { type ipv4_addr : mark; } <cmdline>:1:28-31: Error: syntax error, unexpected mark, expecting string add set filter SET1 { type mark; } The problem is parser, it expects a string as data type spec, but mark is already declared as a token. I don't have much experience with bison, so does anyone have a quick work-around for this? Andreas ^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: nft: parser problem, can use mark as datatype in sets and maps 2015-08-10 13:48 nft: parser problem, can use mark as datatype in sets and maps Andreas Schultz @ 2015-08-10 17:09 ` Pablo Neira Ayuso 2015-08-11 9:18 ` Andreas Schultz 0 siblings, 1 reply; 8+ messages in thread From: Pablo Neira Ayuso @ 2015-08-10 17:09 UTC (permalink / raw) To: Andreas Schultz; +Cc: netfilter-devel On Mon, Aug 10, 2015 at 03:48:12PM +0200, Andreas Schultz wrote: > Hi, > > The data type definition for mark and the general idea of the parser > indicate that the following nft statements should work: > > # nft add map filter MAP1 { type ipv4_addr : mark\; } > # nft add set filter SET1 { type mark\; } > > However, both fail with a similar error message: > > <cmdline>:1:40-43: Error: syntax error, unexpected mark, expecting string > add map filter MAP1 { type ipv4_addr : mark; } > <cmdline>:1:28-31: Error: syntax error, unexpected mark, expecting string > add set filter SET1 { type mark; } > > The problem is parser, it expects a string as data type spec, but > mark is already declared as a token. > > I don't have much experience with bison, so does anyone have a quick > work-around for this? This is fixed by 2baf59c ("parser_bison: allow to use mark as datatype for maps and sets"). ^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: nft: parser problem, can use mark as datatype in sets and maps 2015-08-10 17:09 ` Pablo Neira Ayuso @ 2015-08-11 9:18 ` Andreas Schultz 2015-08-11 10:41 ` Pablo Neira Ayuso 0 siblings, 1 reply; 8+ messages in thread From: Andreas Schultz @ 2015-08-11 9:18 UTC (permalink / raw) To: Pablo Neira Ayuso; +Cc: netfilter-devel On 08/10/2015 07:09 PM, Pablo Neira Ayuso wrote: > On Mon, Aug 10, 2015 at 03:48:12PM +0200, Andreas Schultz wrote: >> Hi, >> >> The data type definition for mark and the general idea of the parser >> indicate that the following nft statements should work: >> >> # nft add map filter MAP1 { type ipv4_addr : mark\; } >> # nft add set filter SET1 { type mark\; } >> >> However, both fail with a similar error message: >> >> <cmdline>:1:40-43: Error: syntax error, unexpected mark, expecting string >> add map filter MAP1 { type ipv4_addr : mark; } >> <cmdline>:1:28-31: Error: syntax error, unexpected mark, expecting string >> add set filter SET1 { type mark; } >> >> The problem is parser, it expects a string as data type spec, but >> mark is already declared as a token. >> >> I don't have much experience with bison, so does anyone have a quick >> work-around for this? > > This is fixed by 2baf59c ("parser_bison: allow to use mark as datatype > for maps and sets"). Ah, I was using the next-4.2 branch and missed this fix in master, sorry for the noise. However, the parser problem is solved, but named mark maps are still not working: anonymous maps work as expected: # nft add rule ip mangle OUTPUT mark set ip saddr map { 192.168.0.10 : 0x1 } named maps do not: # nft add map mangle CLASS05 "{ type ipv4_addr : mark; }" # nft add element mangle CLASS05 { 192.168.0.10 : 0x1 } # nft add rule ip mangle OUTPUT mark set ip saddr map @CLASS05 <cmdline>:1:1-56: Error: Could not process rule: Invalid argument Any idea? Andreas ^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: nft: parser problem, can use mark as datatype in sets and maps 2015-08-11 9:18 ` Andreas Schultz @ 2015-08-11 10:41 ` Pablo Neira Ayuso 2015-08-11 11:25 ` Andreas Schultz 0 siblings, 1 reply; 8+ messages in thread From: Pablo Neira Ayuso @ 2015-08-11 10:41 UTC (permalink / raw) To: Andreas Schultz; +Cc: netfilter-devel On Tue, Aug 11, 2015 at 11:18:54AM +0200, Andreas Schultz wrote: > On 08/10/2015 07:09 PM, Pablo Neira Ayuso wrote: > >On Mon, Aug 10, 2015 at 03:48:12PM +0200, Andreas Schultz wrote: > >>Hi, > >> > >>The data type definition for mark and the general idea of the parser > >>indicate that the following nft statements should work: > >> > >> # nft add map filter MAP1 { type ipv4_addr : mark\; } > >> # nft add set filter SET1 { type mark\; } > >> > >>However, both fail with a similar error message: > >> > >> <cmdline>:1:40-43: Error: syntax error, unexpected mark, expecting string > >> add map filter MAP1 { type ipv4_addr : mark; } > >> <cmdline>:1:28-31: Error: syntax error, unexpected mark, expecting string > >> add set filter SET1 { type mark; } > >> > >>The problem is parser, it expects a string as data type spec, but > >>mark is already declared as a token. > >> > >>I don't have much experience with bison, so does anyone have a quick > >>work-around for this? > > > >This is fixed by 2baf59c ("parser_bison: allow to use mark as datatype > >for maps and sets"). > > Ah, I was using the next-4.2 branch and missed this fix in master, > sorry for the noise. > > However, the parser problem is solved, but named mark maps are still > not working: > > anonymous maps work as expected: > > # nft add rule ip mangle OUTPUT mark set ip saddr map { > 192.168.0.10 : 0x1 } > > named maps do not: > > # nft add map mangle CLASS05 "{ type ipv4_addr : mark; }" > # nft add element mangle CLASS05 { 192.168.0.10 : 0x1 } > # nft add rule ip mangle OUTPUT mark set ip saddr map @CLASS05 > <cmdline>:1:1-56: Error: Could not process rule: Invalid argument > > Any idea? This is working fine here with a nf.git tree snapshot. table ip mangle { map CLASS05 { type ipv4_addr : mark elements = { 192.168.0.10 : 0x00000001} } chain OUTPUT { type route hook output priority 0; policy accept; mark set ip saddr map @CLASS05 } } What Linux kernel version are you using? Remember that concatenation support is there since 4.1. ^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: nft: parser problem, can use mark as datatype in sets and maps 2015-08-11 10:41 ` Pablo Neira Ayuso @ 2015-08-11 11:25 ` Andreas Schultz 2015-08-11 12:12 ` Pablo Neira Ayuso 0 siblings, 1 reply; 8+ messages in thread From: Andreas Schultz @ 2015-08-11 11:25 UTC (permalink / raw) To: Pablo Neira Ayuso; +Cc: netfilter-devel On 08/11/2015 12:41 PM, Pablo Neira Ayuso wrote: > On Tue, Aug 11, 2015 at 11:18:54AM +0200, Andreas Schultz wrote: >> On 08/10/2015 07:09 PM, Pablo Neira Ayuso wrote: >>> On Mon, Aug 10, 2015 at 03:48:12PM +0200, Andreas Schultz wrote: >>>> Hi, >>>> >>>> The data type definition for mark and the general idea of the parser >>>> indicate that the following nft statements should work: >>>> >>>> # nft add map filter MAP1 { type ipv4_addr : mark\; } >>>> # nft add set filter SET1 { type mark\; } >>>> >>>> However, both fail with a similar error message: >>>> >>>> <cmdline>:1:40-43: Error: syntax error, unexpected mark, expecting string >>>> add map filter MAP1 { type ipv4_addr : mark; } >>>> <cmdline>:1:28-31: Error: syntax error, unexpected mark, expecting string >>>> add set filter SET1 { type mark; } >>>> >>>> The problem is parser, it expects a string as data type spec, but >>>> mark is already declared as a token. >>>> >>>> I don't have much experience with bison, so does anyone have a quick >>>> work-around for this? >>> >>> This is fixed by 2baf59c ("parser_bison: allow to use mark as datatype >>> for maps and sets"). >> >> Ah, I was using the next-4.2 branch and missed this fix in master, >> sorry for the noise. >> >> However, the parser problem is solved, but named mark maps are still >> not working: >> >> anonymous maps work as expected: >> >> # nft add rule ip mangle OUTPUT mark set ip saddr map { >> 192.168.0.10 : 0x1 } >> >> named maps do not: >> >> # nft add map mangle CLASS05 "{ type ipv4_addr : mark; }" >> # nft add element mangle CLASS05 { 192.168.0.10 : 0x1 } >> # nft add rule ip mangle OUTPUT mark set ip saddr map @CLASS05 >> <cmdline>:1:1-56: Error: Could not process rule: Invalid argument >> >> Any idea? > > This is working fine here with a nf.git tree snapshot. > > table ip mangle { > map CLASS05 { > type ipv4_addr : mark > elements = { 192.168.0.10 : 0x00000001} > } > > chain OUTPUT { > type route hook output priority 0; policy accept; > mark set ip saddr map @CLASS05 > } > } When I put that into a file and try to restore it, I get this: # nft -f /tmp/map.nft /tmp/map.nft:4:28-54: Error: mapping outside of map context elements = { 192.168.0.10 : 0x00000001} ^^^^^^^^^^^^^^^^^^^^^^^^^^^ > What Linux kernel version are you using? Remember that concatenation > support is there since 4.1. Userland: git://git.netfilter.org/libnftnl branch master @ HEAD (0edeb66) git://git.netfilter.org/nftables branch master @ HEAD (ecf855b) Kernel: Linux 4.2-rc3 + net-next + nf-next net-next: https://kernel.googlesource.com/pub/scm/linux/kernel/git/davem/net-next.git (@8c1a91f) nf-next: git://git.kernel.org/pub/scm/linux/kernel/git/pablo/nf-next.git (@a6cd379) Since all patches that I need (netns stuff) have been accepted by David, I'm going to rebase the kernel to net-next and try again. Andreas ^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: nft: parser problem, can use mark as datatype in sets and maps 2015-08-11 11:25 ` Andreas Schultz @ 2015-08-11 12:12 ` Pablo Neira Ayuso 2015-08-11 12:23 ` Pablo Neira Ayuso 0 siblings, 1 reply; 8+ messages in thread From: Pablo Neira Ayuso @ 2015-08-11 12:12 UTC (permalink / raw) To: Andreas Schultz; +Cc: netfilter-devel On Tue, Aug 11, 2015 at 01:25:21PM +0200, Andreas Schultz wrote: > On 08/11/2015 12:41 PM, Pablo Neira Ayuso wrote: > >On Tue, Aug 11, 2015 at 11:18:54AM +0200, Andreas Schultz wrote: > >>On 08/10/2015 07:09 PM, Pablo Neira Ayuso wrote: > >>>On Mon, Aug 10, 2015 at 03:48:12PM +0200, Andreas Schultz wrote: > >>>>Hi, > >>>> > >>>>The data type definition for mark and the general idea of the parser > >>>>indicate that the following nft statements should work: > >>>> > >>>> # nft add map filter MAP1 { type ipv4_addr : mark\; } > >>>> # nft add set filter SET1 { type mark\; } > >>>> > >>>>However, both fail with a similar error message: > >>>> > >>>> <cmdline>:1:40-43: Error: syntax error, unexpected mark, expecting string > >>>> add map filter MAP1 { type ipv4_addr : mark; } > >>>> <cmdline>:1:28-31: Error: syntax error, unexpected mark, expecting string > >>>> add set filter SET1 { type mark; } > >>>> > >>>>The problem is parser, it expects a string as data type spec, but > >>>>mark is already declared as a token. > >>>> > >>>>I don't have much experience with bison, so does anyone have a quick > >>>>work-around for this? > >>> > >>>This is fixed by 2baf59c ("parser_bison: allow to use mark as datatype > >>>for maps and sets"). > >> > >>Ah, I was using the next-4.2 branch and missed this fix in master, > >>sorry for the noise. > >> > >>However, the parser problem is solved, but named mark maps are still > >>not working: > >> > >>anonymous maps work as expected: > >> > >> # nft add rule ip mangle OUTPUT mark set ip saddr map { > >>192.168.0.10 : 0x1 } > >> > >>named maps do not: > >> > >> # nft add map mangle CLASS05 "{ type ipv4_addr : mark; }" > >> # nft add element mangle CLASS05 { 192.168.0.10 : 0x1 } > >> # nft add rule ip mangle OUTPUT mark set ip saddr map @CLASS05 > >> <cmdline>:1:1-56: Error: Could not process rule: Invalid argument > >> > >>Any idea? > > > >This is working fine here with a nf.git tree snapshot. > > > >table ip mangle { > > map CLASS05 { > > type ipv4_addr : mark > > elements = { 192.168.0.10 : 0x00000001} > > } > > > > chain OUTPUT { > > type route hook output priority 0; policy accept; > > mark set ip saddr map @CLASS05 > > } > >} > > When I put that into a file and try to restore it, I get this: > > # nft -f /tmp/map.nft > /tmp/map.nft:4:28-54: Error: mapping outside of map context > elements = { 192.168.0.10 : 0x00000001} > ^^^^^^^^^^^^^^^^^^^^^^^^^^^ > > >What Linux kernel version are you using? Remember that concatenation > >support is there since 4.1. > > Userland: > > git://git.netfilter.org/libnftnl branch master @ HEAD (0edeb66) > git://git.netfilter.org/nftables branch master @ HEAD (ecf855b) Please, give a try to this branch: http://git.netfilter.org/nftables/log/?h=cache-consolidation I was testing your examples with these patcheset applied on top of nftables HEAD: http://marc.info/?l=netfilter-devel&m=143920709517449&w=2 Let me know, thanks. ^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: nft: parser problem, can use mark as datatype in sets and maps 2015-08-11 12:12 ` Pablo Neira Ayuso @ 2015-08-11 12:23 ` Pablo Neira Ayuso 2015-08-11 12:28 ` Andreas Schultz 0 siblings, 1 reply; 8+ messages in thread From: Pablo Neira Ayuso @ 2015-08-11 12:23 UTC (permalink / raw) To: Andreas Schultz; +Cc: netfilter-devel On Tue, Aug 11, 2015 at 02:12:12PM +0200, Pablo Neira Ayuso wrote: > On Tue, Aug 11, 2015 at 01:25:21PM +0200, Andreas Schultz wrote: > > On 08/11/2015 12:41 PM, Pablo Neira Ayuso wrote: > > >On Tue, Aug 11, 2015 at 11:18:54AM +0200, Andreas Schultz wrote: > > >>On 08/10/2015 07:09 PM, Pablo Neira Ayuso wrote: > > >>>On Mon, Aug 10, 2015 at 03:48:12PM +0200, Andreas Schultz wrote: > > >>>>Hi, > > >>>> > > >>>>The data type definition for mark and the general idea of the parser > > >>>>indicate that the following nft statements should work: > > >>>> > > >>>> # nft add map filter MAP1 { type ipv4_addr : mark\; } > > >>>> # nft add set filter SET1 { type mark\; } > > >>>> > > >>>>However, both fail with a similar error message: > > >>>> > > >>>> <cmdline>:1:40-43: Error: syntax error, unexpected mark, expecting string > > >>>> add map filter MAP1 { type ipv4_addr : mark; } > > >>>> <cmdline>:1:28-31: Error: syntax error, unexpected mark, expecting string > > >>>> add set filter SET1 { type mark; } > > >>>> > > >>>>The problem is parser, it expects a string as data type spec, but > > >>>>mark is already declared as a token. > > >>>> > > >>>>I don't have much experience with bison, so does anyone have a quick > > >>>>work-around for this? > > >>> > > >>>This is fixed by 2baf59c ("parser_bison: allow to use mark as datatype > > >>>for maps and sets"). > > >> > > >>Ah, I was using the next-4.2 branch and missed this fix in master, > > >>sorry for the noise. > > >> > > >>However, the parser problem is solved, but named mark maps are still > > >>not working: > > >> > > >>anonymous maps work as expected: > > >> > > >> # nft add rule ip mangle OUTPUT mark set ip saddr map { > > >>192.168.0.10 : 0x1 } > > >> > > >>named maps do not: > > >> > > >> # nft add map mangle CLASS05 "{ type ipv4_addr : mark; }" > > >> # nft add element mangle CLASS05 { 192.168.0.10 : 0x1 } > > >> # nft add rule ip mangle OUTPUT mark set ip saddr map @CLASS05 > > >> <cmdline>:1:1-56: Error: Could not process rule: Invalid argument > > >> > > >>Any idea? > > > > > >This is working fine here with a nf.git tree snapshot. > > > > > >table ip mangle { > > > map CLASS05 { > > > type ipv4_addr : mark > > > elements = { 192.168.0.10 : 0x00000001} > > > } > > > > > > chain OUTPUT { > > > type route hook output priority 0; policy accept; > > > mark set ip saddr map @CLASS05 > > > } > > >} > > > > When I put that into a file and try to restore it, I get this: > > > > # nft -f /tmp/map.nft > > /tmp/map.nft:4:28-54: Error: mapping outside of map context > > elements = { 192.168.0.10 : 0x00000001} > > ^^^^^^^^^^^^^^^^^^^^^^^^^^^ > > > > >What Linux kernel version are you using? Remember that concatenation > > >support is there since 4.1. > > > > Userland: > > > > git://git.netfilter.org/libnftnl branch master @ HEAD (0edeb66) > > git://git.netfilter.org/nftables branch master @ HEAD (ecf855b) > > Please, give a try to this branch: > > http://git.netfilter.org/nftables/log/?h=cache-consolidation Wait, I was testing by loading via nft -f with a linear representation: add table mangle add chain mangle OUTPUT { type route hook output priority 0; } add map mangle CLASS05 { type ipv4_addr : mark; } add element mangle CLASS05 { 192.168.0.10 : 0x1 } add rule ip mangle OUTPUT mark set ip saddr map @CLASS05 So I confirm I'm hitting the problem that you're reporting above. Let me have a look into this. ^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: nft: parser problem, can use mark as datatype in sets and maps 2015-08-11 12:23 ` Pablo Neira Ayuso @ 2015-08-11 12:28 ` Andreas Schultz 0 siblings, 0 replies; 8+ messages in thread From: Andreas Schultz @ 2015-08-11 12:28 UTC (permalink / raw) To: Pablo Neira Ayuso; +Cc: netfilter-devel On 08/11/2015 02:23 PM, Pablo Neira Ayuso wrote: > On Tue, Aug 11, 2015 at 02:12:12PM +0200, Pablo Neira Ayuso wrote: >> On Tue, Aug 11, 2015 at 01:25:21PM +0200, Andreas Schultz wrote: >>> On 08/11/2015 12:41 PM, Pablo Neira Ayuso wrote: >>>> On Tue, Aug 11, 2015 at 11:18:54AM +0200, Andreas Schultz wrote: >>>>> On 08/10/2015 07:09 PM, Pablo Neira Ayuso wrote: >>>>>> On Mon, Aug 10, 2015 at 03:48:12PM +0200, Andreas Schultz wrote: >>>>>>> Hi, >>>>>>> >>>>>>> The data type definition for mark and the general idea of the parser >>>>>>> indicate that the following nft statements should work: >>>>>>> >>>>>>> # nft add map filter MAP1 { type ipv4_addr : mark\; } >>>>>>> # nft add set filter SET1 { type mark\; } >>>>>>> >>>>>>> However, both fail with a similar error message: >>>>>>> >>>>>>> <cmdline>:1:40-43: Error: syntax error, unexpected mark, expecting string >>>>>>> add map filter MAP1 { type ipv4_addr : mark; } >>>>>>> <cmdline>:1:28-31: Error: syntax error, unexpected mark, expecting string >>>>>>> add set filter SET1 { type mark; } >>>>>>> >>>>>>> The problem is parser, it expects a string as data type spec, but >>>>>>> mark is already declared as a token. >>>>>>> >>>>>>> I don't have much experience with bison, so does anyone have a quick >>>>>>> work-around for this? >>>>>> >>>>>> This is fixed by 2baf59c ("parser_bison: allow to use mark as datatype >>>>>> for maps and sets"). >>>>> >>>>> Ah, I was using the next-4.2 branch and missed this fix in master, >>>>> sorry for the noise. >>>>> >>>>> However, the parser problem is solved, but named mark maps are still >>>>> not working: >>>>> >>>>> anonymous maps work as expected: >>>>> >>>>> # nft add rule ip mangle OUTPUT mark set ip saddr map { >>>>> 192.168.0.10 : 0x1 } >>>>> >>>>> named maps do not: >>>>> >>>>> # nft add map mangle CLASS05 "{ type ipv4_addr : mark; }" >>>>> # nft add element mangle CLASS05 { 192.168.0.10 : 0x1 } >>>>> # nft add rule ip mangle OUTPUT mark set ip saddr map @CLASS05 >>>>> <cmdline>:1:1-56: Error: Could not process rule: Invalid argument >>>>> >>>>> Any idea? >>>> >>>> This is working fine here with a nf.git tree snapshot. >>>> >>>> table ip mangle { >>>> map CLASS05 { >>>> type ipv4_addr : mark >>>> elements = { 192.168.0.10 : 0x00000001} >>>> } >>>> >>>> chain OUTPUT { >>>> type route hook output priority 0; policy accept; >>>> mark set ip saddr map @CLASS05 >>>> } >>>> } >>> >>> When I put that into a file and try to restore it, I get this: >>> >>> # nft -f /tmp/map.nft >>> /tmp/map.nft:4:28-54: Error: mapping outside of map context >>> elements = { 192.168.0.10 : 0x00000001} >>> ^^^^^^^^^^^^^^^^^^^^^^^^^^^ >>> >>>> What Linux kernel version are you using? Remember that concatenation >>>> support is there since 4.1. >>> >>> Userland: >>> >>> git://git.netfilter.org/libnftnl branch master @ HEAD (0edeb66) >>> git://git.netfilter.org/nftables branch master @ HEAD (ecf855b) >> >> Please, give a try to this branch: >> >> http://git.netfilter.org/nftables/log/?h=cache-consolidation > > Wait, I was testing by loading via nft -f with a linear representation: > > add table mangle > add chain mangle OUTPUT { type route hook output priority 0; } > add map mangle CLASS05 { type ipv4_addr : mark; } > add element mangle CLASS05 { 192.168.0.10 : 0x1 } > add rule ip mangle OUTPUT mark set ip saddr map @CLASS05 > > So I confirm I'm hitting the problem that you're reporting above. Let > me have a look into this. I have now rebuild the kernel from David's net-next tree and nftables userspace with the cache-consolidation branch applied. The test give somewhat mixed results: * nft -f with the linear representation works * nft -f with the structured representation fails with: /tmp/map2.nft:4:28-54: Error: mapping outside of map context elements = { 192.168.0.10 : 0x00000001} ^^^^^^^^^^^^^^^^^^^^^^^^^^^ * running each command separately, like so: # nft add table mangle # nft add chain mangle OUTPUT { type route hook output priority 0\; } # nft add map mangle CLASS05 "{ type ipv4_addr : mark; }" # nft add element mangle CLASS05 { 192.168.0.10 : 0x1 } # nft add rule ip mangle OUTPUT mark set ip saddr map @CLASS05 fails on the last command with: <cmdline>:1:1-56: Error: Could not process rule: Invalid argument add rule ip mangle OUTPUT mark set ip saddr map @CLASS05 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Andreas ^ permalink raw reply [flat|nested] 8+ messages in thread
end of thread, other threads:[~2015-08-11 12:28 UTC | newest] Thread overview: 8+ messages (download: mbox.gz / follow: Atom feed) -- links below jump to the message on this page -- 2015-08-10 13:48 nft: parser problem, can use mark as datatype in sets and maps Andreas Schultz 2015-08-10 17:09 ` Pablo Neira Ayuso 2015-08-11 9:18 ` Andreas Schultz 2015-08-11 10:41 ` Pablo Neira Ayuso 2015-08-11 11:25 ` Andreas Schultz 2015-08-11 12:12 ` Pablo Neira Ayuso 2015-08-11 12:23 ` Pablo Neira Ayuso 2015-08-11 12:28 ` Andreas Schultz
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for NNTP newsgroup(s).