search for: fragments

Hi It seem that the fragment interface on certain plugins exceeds the amount of fragment operations possible on Intel GMA cards. This only occurs with the "water" and "blur" plugins. the plugins activate OK and do not report a missing GL_ARB_fragment_program in the server extensions. Waves appear when I use the water plugin with <Super><Ctrl> but there is no

After much effort I upgraded our fairly large Rails app from 2.1 to 2.3. After deployment yesterday I noticed an across the board increase in response times. It seems that every call to memcache now takes 10x longer than before. Here are some example numbers from my development log (below), with memcache running locally. We see similar scale of performance drop in production as well - average

The code to detect fragments in checksum_setup() was missing for IPv4 and too eager for IPv6. (It transpires that Windows seems to send IPv6 packets with a fragment header even if they are not a fragment - i.e. offset is zero, and M bit is not set). Signed-off-by: Paul Durrant <paul.durrant@citrix.com> Cc: Wei Liu <w...

Hello, I want to play Eve Online in Wine. It was working (mostly) on my old card, a GTX 280, using the nvidia driver. It was the 3rd card I've had from Nvidia in a row with manufacturing defects, so I bought a Radeon 6870, which is working good except with Wine. I am using fglrx, and have a dual head setup using xrandr. When I log in, I get to the screen where it is entering the game after I

...ragmentation (numbers reported by telnet sessions to the SAN device). Fragmentation decreases are very significant. We see most files now created without any fragmentation (single fragment reported by sysinternals contig utility) whereas prior to the patch the same files were containing 40,000 fragments and above. In some cases we are still getting fragmented files but those files normally contain less than 2000 fragments and are only on files 10GB and above. Just my two cents. -------------- next part -------------- HTML attachment scrubbed and removed

...agram Sockets} > > > > > + > > > > > +\drivernormative{\paragraph}{Device Operation: Packet Fragmentation}{Device Types / Socket Device / Datagram Sockets / Fragmentation} > > > > > + > > > > > +Drivers MAY disassemble packets into smaller fragments. If drivers fragment a > > > > > +packet, they MUST follow the fragmentation rules described in section > > > > > +\ref{sec:Device Types / Socket Device / Device Operation / Datagram Sockets / Fragmentation}. > > > > > + > > > > > +Drivers...

...agram Sockets} > > > > > + > > > > > +\drivernormative{\paragraph}{Device Operation: Packet Fragmentation}{Device Types / Socket Device / Datagram Sockets / Fragmentation} > > > > > + > > > > > +Drivers MAY disassemble packets into smaller fragments. If drivers fragment a > > > > > +packet, they MUST follow the fragmentation rules described in section > > > > > +\ref{sec:Device Types / Socket Device / Device Operation / Datagram Sockets / Fragmentation}. > > > > > + > > > > > +Drivers...

...> > + > > > > > > > +\drivernormative{\paragraph}{Device Operation: Packet Fragmentation}{Device Types / Socket Device / Datagram Sockets / Fragmentation} > > > > > > > + > > > > > > > +Drivers MAY disassemble packets into smaller fragments. If drivers fragment a > > > > > > > +packet, they MUST follow the fragmentation rules described in section > > > > > > > +\ref{sec:Device Types / Socket Device / Device Operation / Datagram Sockets / Fragmentation}. > > > > > > > + &gt...

Hi all, At the recent LLVM developers' meeting, I presented a lightning talk on an approach to reduce the amount of dead debug data left in an executable following operations such as --gc-sections and duplicate COMDAT removal. In that presentation, I presented some figures based on linking a game that had been built by our downstream clang port and fragmented using the described approach.

Also unify .index-fragment files --- builder/templates/debian-7.index-fragment | 7 ------- builder/templates/debian-8.index-fragment | 7 ------- builder/templates/debian-9.index-fragment | 18 ++++++------------ builder/templates/debian.preseed | 1 + builder/templates/make-template.ml | 6 ------ 5 files changed, 7 insertions(+), 32 deletions(-) diff --git

https://bugzilla.netfilter.org/show_bug.cgi?id=987 Bug ID: 987 Summary: nf_conntrack_reasm.c : Silent discard of overlapping fragments is not silent Product: netfilter/iptables Version: unspecified Hardware: x86_64 OS: Debian GNU/Linux Status: NEW Severity: normal Priority: P5 Component: nf_conntrack Assignee: netfilter-buglog at lis...

On Mon, 2015-01-26 at 09:37 -0500, Vladislav Yasevich wrote: > If the IPv6 fragment id has not been set and we perform > fragmentation due to UFO, select a new fragment id. > When we store the fragment id into skb_shinfo, set the bit > in the skb so we can re-use the selected id. > This preserves the behavior of UFO packets generated on the > host and solves the issue of id

On Mon, 2015-01-26 at 09:37 -0500, Vladislav Yasevich wrote: > If the IPv6 fragment id has not been set and we perform > fragmentation due to UFO, select a new fragment id. > When we store the fragment id into skb_shinfo, set the bit > in the skb so we can re-use the selected id. > This preserves the behavior of UFO packets generated on the > host and solves the issue of id

.../show_bug.cgi?id=48 ------- Additional Comments From tatonet@tiscali.it 2004-02-25 15:05 ------- I know that this is an old bug report, but it's still opened... If we save the size of each single fragment we have to face another problem: how should we re-fragment the packet if original fragments were partially or totally overlapped? Another approach could be the following: if the DF flag is set in the fragments of a packet, the maximum length fragment determines the fate of the whole packet during routing. A possible solution could be to save the maximum length of fragments in PR...

...rames would still get the > > fragmentation id generated in the host kernel. > > Why would non-gso frames need a frag id? We are talking only UDP IPv6 > here, so there is no frag id generation if the packet does't need to > be fragmented. E.g. raw sockets still can generate fragments locally. It is also a valid setup to have multiple interfaces in one machine, one that is UFO enabled and one that isn't. In that case, fragmentation id generation happens on different hosts which I want to avoid. I haven't looked closely but mismatch of MTUs on interfaces seems like it co...

...rames would still get the > > fragmentation id generated in the host kernel. > > Why would non-gso frames need a frag id? We are talking only UDP IPv6 > here, so there is no frag id generation if the packet does't need to > be fragmented. E.g. raw sockets still can generate fragments locally. It is also a valid setup to have multiple interfaces in one machine, one that is UFO enabled and one that isn't. In that case, fragmentation id generation happens on different hosts which I want to avoid. I haven't looked closely but mismatch of MTUs on interfaces seems like it co...

...wever, for the attack to succeed, the attacker will have to deliver several thousand packets to the target, which can take up to several minutes. A quick exploit and the patch are appended to the end of this post. The problem starts in ip_glue() in ip_fragment.c: /* Copy the data portions of all fragments into the new buffer. */ fp = qp->fragments; count = qp->ihlen; while(fp) { if ((fp->len < 0) || ((count + fp->len) > skb->len)) goto out_invalid; memcpy((ptr + fp->offset), fp->ptr, fp->len); if (count == qp->ihlen) { skb->dst = dst_clone(fp->sk...

Hello all, I understand that relatively high fragmentation is inherent to ZFS due to its COW and possible intermixing of metadata and data blocks (of which metadata path blocks are likely to expire and get freed relatively quickly). I believe it was sometimes implied on this list that such fragmentation for "static" data can be currently combatted only by zfs send-ing existing

...tacks etc.). > > See also details on such kind of attacks in the description of commit > > 04ca6973f7c1a0d. > > > > AFAIK IETF tried with IPv6 to push fragmentation id generation to the > > end hosts, that's also the reason for the introduction of atomic > > fragments (which are now being rolled back ;) ). > > > > Still it is better to generate a frag id on the hypervisor than just > > sending a 0, so I am ok with this change, albeit not happy. > > > > Thanks, > > Hannes > > > > OK so to summarize, identifiers...

...tacks etc.). > > See also details on such kind of attacks in the description of commit > > 04ca6973f7c1a0d. > > > > AFAIK IETF tried with IPv6 to push fragmentation id generation to the > > end hosts, that's also the reason for the introduction of atomic > > fragments (which are now being rolled back ;) ). > > > > Still it is better to generate a frag id on the hypervisor than just > > sending a 0, so I am ok with this change, albeit not happy. > > > > Thanks, > > Hannes > > > > OK so to summarize, identifiers...