Hi,
On Sat 30-03-19 14:49:46, Steve Magnani wrote:
> On 3/25/19 11:42 AM, Jan Kara wrote:
> > Hi!
> >
> > On Sat 23-03-19 15:14:05, Steve Magnani wrote:
> > > I have been hunting a UDF bug that occasionally results in generation
> > > of an Allocation Extent Descriptor with an incorrect
Jan -
On 3/25/19 11:42 AM, Jan Kara wrote:
Hi!
On Sat 23-03-19 15:14:05, Steve Magnani wrote:
I have been hunting a UDF bug that occasionally results in generation
of an Allocation Extent Descriptor with an incorrect tagLocation. So
far I haven't been able to see a path through the code that
On 3/25/19 11:42 AM, Jan Kara wrote:
Hi!
On Sat 23-03-19 15:14:05, Steve Magnani wrote:
...
In contrast, udf_setup_indirect_aext(), which constructs an AED,
has this sequence:
bh = udf_tgetblk(...); // calls sb_getblk()
lock_buffer(bh);
memset(bh->b_data, 0,
Hi!
On Sat 23-03-19 15:14:05, Steve Magnani wrote:
> I have been hunting a UDF bug that occasionally results in generation
> of an Allocation Extent Descriptor with an incorrect tagLocation. So
> far I haven't been able to see a path through the code that could
> cause that. But, I noticed some
Hi,
I have been hunting a UDF bug that occasionally results in generation
of an Allocation Extent Descriptor with an incorrect tagLocation. So
far I haven't been able to see a path through the code that could
cause that. But, I noticed some inconsistency in locking during
AED generation and
5 matches
Mail list logo