search for: prohibit_path_max_alloc

Signed-off-by: Hu Tao <hutao@cn.fujitsu.com> --- daemon/inotify.c | 12 +++++++++++- 1 file changed, 11 insertions(+), 1 deletion(-) diff --git a/daemon/inotify.c b/daemon/inotify.c index 36e5ede..b847b7d 100644 --- a/daemon/inotify.c +++ b/daemon/inotify.c @@ -309,7 +309,7 @@ do_inotify_files (void) unsigned int i; FILE *fp = NULL; guestfs_int_inotify_event_list *events; - char

On Tuesday 23 September 2014 17:20:35 Hu Tao wrote: > Signed-off-by: Hu Tao <hutao@cn.fujitsu.com> > --- > daemon/inotify.c | 12 +++++++++++- > 1 file changed, 11 insertions(+), 1 deletion(-) While I'd personally get rid of PATH_MAX at all, I understand the Linux inotify implementation relies on it... > > diff --git a/daemon/inotify.c b/daemon/inotify.c > index

...s rather than magic number > make: *** [sc_prohibit_magic_number_exit] Error 1 I think exit (77) is acceptable. To automake, this means that the test has been skipped, and there is no constant for it. However writing a regexp that matches all numbers except "77" is quite hard. > prohibit_path_max_allocation > daemon/initrd.c:41: char filename[PATH_MAX]; > daemon/initrd.c:126: char fullpath[PATH_MAX]; > daemon/inotify.c:310: char buf[PATH_MAX]; > daemon/link.c:38: char link[PATH_MAX]; > daemon/link.c:63: char link[PATH_MAX]; > daemon/realpath.c:86: char ret[PATH_MAX+1] = &q...

...at_check syntax-check: fix prohibit_assert_without_use check syntax-check: fix prohibit_c_ctype_without_use check syntax-check: fix prohibit_dirent_without_use check syntax-check: fix prohibit_empty_lines_at_EOF check syntax-check: fix prohibit_getopt_without_use check syntax-check: fix prohibit_path_max_allocation check syntax-check: fix prohibit_test_minus_ao check syntax-check: fix prohibit_undesirable_word_seq check syntax-check: fix require_config_h_first check syntax-check: fix trailing_blank check BUGS | 6 +- align/Makefile.am...