mirror of
https://github.com/git/git.git
synced 2024-11-24 10:26:17 +08:00
838cd34664
Since v1.6.0.2~13^2~ the completion of a thin pack uses sha1write() for
its ability to compute a SHA1 on the written data. This also provides
data buffering which, along with commit 92392b4a45, will confuse pread()
whenever an appended object is 1) freed due to memory pressure because
of the depth-first delta processing, and 2) needed again because it has
many delta children, and 3) its data is still buffered by sha1write().
Let's fix the issue by simply forcing cached data out when such an
object is written so it can be pread()'d at leisure.
Signed-off-by: Nicolas Pitre <nico@cam.org>
Signed-off-by: Shawn O. Pearce <spearce@spearce.org>
32 lines
757 B
C
32 lines
757 B
C
#ifndef CSUM_FILE_H
|
|
#define CSUM_FILE_H
|
|
|
|
struct progress;
|
|
|
|
/* A SHA1-protected file */
|
|
struct sha1file {
|
|
int fd;
|
|
unsigned int offset;
|
|
SHA_CTX ctx;
|
|
off_t total;
|
|
struct progress *tp;
|
|
const char *name;
|
|
int do_crc;
|
|
uint32_t crc32;
|
|
unsigned char buffer[8192];
|
|
};
|
|
|
|
/* sha1close flags */
|
|
#define CSUM_CLOSE 1
|
|
#define CSUM_FSYNC 2
|
|
|
|
extern struct sha1file *sha1fd(int fd, const char *name);
|
|
extern struct sha1file *sha1fd_throughput(int fd, const char *name, struct progress *tp);
|
|
extern int sha1close(struct sha1file *, unsigned char *, unsigned int);
|
|
extern int sha1write(struct sha1file *, void *, unsigned int);
|
|
extern void sha1flush(struct sha1file *f);
|
|
extern void crc32_begin(struct sha1file *);
|
|
extern uint32_t crc32_end(struct sha1file *);
|
|
|
|
#endif
|