#ifndef _L3_H_ #define _L3_H_ 1 struct l3_pins { void (*setdat)(struct l3_pins *, int); void (*setclk)(struct l3_pins *, int); void (*setmode)(struct l3_pins *, int); int gpio_data; int gpio_clk; int gpio_mode; int use_gpios; int data_hold; int data_setup; int clock_high; int mode_hold; int mode; int mode_setup; }; struct device; int l3_write(struct l3_pins *adap, u8 addr, u8 *data, int len); int l3_set_gpio_ops(struct device *dev, struct l3_pins *adap); #endif t repository'/>
summaryrefslogtreecommitdiff
path: root/Documentation/acpi
diff options
context:
space:
mode:
authorTheodore Ts'o <tytso@mit.edu>2016-04-23 22:50:07 -0400
committerTheodore Ts'o <tytso@mit.edu>2016-04-23 22:50:07 -0400
commit1f60fbe7274918adb8db2f616e321890730ab7e3 (patch)
tree4e41c7a0fd5204cad9e651baa23207bf4dafe256 /Documentation/acpi
parentc3b46c73264b03000d1e18b22f5caf63332547c9 (diff)
ext4: allow readdir()'s of large empty directories to be interrupted
If a directory has a large number of empty blocks, iterating over all of them can take a long time, leading to scheduler warnings and users getting irritated when they can't kill a process in the middle of one of these long-running readdir operations. Fix this by adding checks to ext4_readdir() and ext4_htree_fill_tree(). This was reverted earlier due to a typo in the original commit where I experimented with using signal_pending() instead of fatal_signal_pending(). The test was in the wrong place if we were going to return signal_pending() since we would end up returning duplicant entries. See 9f2394c9be47 for a more detailed explanation. Added fix as suggested by Linus to check for signal_pending() in in the filldir() functions. Reported-by: Benjamin LaHaise <bcrl@kvack.org> Google-Bug-Id: 27880676 Signed-off-by: Theodore Ts'o <tytso@mit.edu>
Diffstat (limited to 'Documentation/acpi')