summaryrefslogtreecommitdiff
path: root/proto_icmpv4.c
diff options
context:
space:
mode:
authorDaniel Borkmann <dborkman@redhat.com>2013-05-24 13:48:50 +0200
committerDaniel Borkmann <dborkman@redhat.com>2013-05-24 13:48:50 +0200
commit0548e971eeb7fc7ceffaa608f1ece638d6549ec1 (patch)
tree56029706a924e6d29904d62fd524f0da483cde49 /proto_icmpv4.c
parent37dd6912701cb16f6339af97216e159c3f9038ee (diff)
make: add HARDENING build option
Add HARDENING=1 build option and move all hardening-related GCC flags into this condition. This allows the user to choose whether or not he wants to have a hardened build with some possible performance tradeoff at load/runtime. Signed-off-by: Daniel Borkmann <dborkman@redhat.com>
Diffstat (limited to 'proto_icmpv4.c')
0 files changed, 0 insertions, 0 deletions
usStateConnected notification leading to: ----- blkback_changed() > because now frontstate != XenbusStateInitialised talk_to_blkback() is also called again > blkfront state changed from XenbusStateConnected to XenbusStateInitialised (Which is not correct!) front_changed(): > Do nothing because blkback already in XenbusStateConnected Now blkback is in XenbusStateConnected but blkfront is still in XenbusStateInitialised - leading to no disks. Poking of the XenbusStateConnected state is allowed (to deal with block disk change) and has to be dealt with. The most likely cause of this bug are custom udev scripts hooking up the disks and then validating the size. Signed-off-by: Bob Liu <bob.liu@oracle.com> Signed-off-by: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Diffstat (limited to 'Documentation/devicetree')