On 09.09.2023 12:32, Mark Millard wrote:
On Sep 8, 2023, at 21:54, Mark Millard wrote:
On Sep 8, 2023, at 18:19, Mark Millard wrote:
On Sep 8, 2023, at 17:03, Mark Millard wrote:
On Sep 8, 2023, at 15:30, Martin Matuska wrote:
On 9. 9. 2023 0:09, Alexander Motin wrote:
Thank you, Martin.
On Sep 8, 2023, at 21:54, Mark Millard wrote:
> On Sep 8, 2023, at 18:19, Mark Millard wrote:
>
>> On Sep 8, 2023, at 17:03, Mark Millard wrote:
>>
>>> On Sep 8, 2023, at 15:30, Martin Matuska wrote:
>>>
I can confirm that the patch fixes the panic caused by the provided script
o
On Sep 8, 2023, at 18:19, Mark Millard wrote:
> On Sep 8, 2023, at 17:03, Mark Millard wrote:
>
>> On Sep 8, 2023, at 15:30, Martin Matuska wrote:
>>
>>> I can confirm that the patch fixes the panic caused by the provided script
>>> on my test systems.
>>> Mark, would it be possible to try p
On Fri, 8 Sep 2023 17:03:07 -0700
Mark Millard wrote:
> On Sep 8, 2023, at 15:30, Martin Matuska wrote:
>
> > I can confirm that the patch fixes the panic caused by the provided script
> > on my test systems.
> > Mark, would it be possible to try poudriere on your system with a patched
> > ke
On Sep 8, 2023, at 17:03, Mark Millard wrote:
> On Sep 8, 2023, at 15:30, Martin Matuska wrote:
>
>> I can confirm that the patch fixes the panic caused by the provided script
>> on my test systems.
>> Mark, would it be possible to try poudriere on your system with a patched
>> kernel?
>
> .
On 9/8/23 15:09, Alexander Motin wrote:
Thank you, Martin. I was able to reproduce the issue with your script
and found the cause.
I first though the issue is triggered by the `cp`, but it appeared to be
triggered by `cat`. It also got copy_file_range() support, but later
than `cp`. That i
On Sep 8, 2023, at 15:30, Martin Matuska wrote:
> I can confirm that the patch fixes the panic caused by the provided script on
> my test systems.
> Mark, would it be possible to try poudriere on your system with a patched
> kernel?
. . .
On 9. 9. 2023 0:09, Alexander Motin wrote:
> On 08.09.
Hi Alexander,
I can confirm that the patch fixes the panic caused by the provided
script on my test systems.
Mark, would it be possible to try poudriere on your system with a
patched kernel?
Thanks
mm
On 9. 9. 2023 0:09, Alexander Motin wrote:
On 08.09.2023 09:52, Martin Matuska wrote:
I di
On 08.09.2023 09:52, Martin Matuska wrote:
I digged a little and was able to reproduce the panic without poudriere
with a shell script.
#!/bin/sh
nl='
'
sed_script=s/aaa/b/
for ac_i in 1 2 3 4 5 6 7; do
sed_script="$sed_script
On Sep 8, 2023, at 06:52, Martin Matuska wrote:
> I digged a little and was able to reproduce the panic without poudriere with
> a shell script.
>
> You may want to increase "repeats".
> The script causes the panic in dmu_buf_hold_array_by_dnode() on my VirtualBox
> with the cat command on 9th
I digged a little and was able to reproduce the panic without poudriere
with a shell script.
You may want to increase "repeats".
The script causes the panic in dmu_buf_hold_array_by_dnode() on my
VirtualBox with the cat command on 9th iteration.
Here is the script:
#!/bin/sh
nl='
'
sed_scrip
[Today's main-snapshot kernel panics as well.]
On Sep 7, 2023, at 16:32, Mark Millard wrote:
> On Sep 7, 2023, at 13:07, Alexander Motin wrote:
>
>> Thanks, Mark.
>>
>> On 07.09.2023 15:40, Mark Millard wrote:
>>> On Sep 7, 2023, at 11:48, Glen Barber wrote:
On Thu, Sep 07, 2023 at 11:1
On Sep 7, 2023, at 13:07, Alexander Motin wrote:
> Thanks, Mark.
>
> On 07.09.2023 15:40, Mark Millard wrote:
>> On Sep 7, 2023, at 11:48, Glen Barber wrote:
>>> On Thu, Sep 07, 2023 at 11:17:22AM -0700, Mark Millard wrote:
When I next have time, should I retry based on a more recent
Thanks, Mark.
On 07.09.2023 15:40, Mark Millard wrote:
On Sep 7, 2023, at 11:48, Glen Barber wrote:
On Thu, Sep 07, 2023 at 11:17:22AM -0700, Mark Millard wrote:
When I next have time, should I retry based on a more recent
vintage of main that includes 969071be938c ?
Yes, please, if you ca
On Sep 7, 2023, at 11:48, Glen Barber wrote:
> On Thu, Sep 07, 2023 at 11:17:22AM -0700, Mark Millard wrote:
>> When I next have time, should I retry based on a more recent
>> vintage of main that includes 969071be938c ?
>>
>
> Yes, please, if you can.
As stands, I rebooted that machine into m
On Thu, Sep 07, 2023 at 11:17:22AM -0700, Mark Millard wrote:
> When I next have time, should I retry based on a more recent
> vintage of main that includes 969071be938c ?
>
Yes, please, if you can.
Glen
signature.asc
Description: PGP signature
[Drat, the request to rerun my tests did not not mention
the more recent change:
vfs: copy_file_range() between multiple mountpoints of the same fs type
and I'd not noticed on my own and ran the test without updating.]
On Sep 7, 2023, at 11:02, Mark Millard wrote:
> I was requested to do a te
I was requested to do a test with vfs.zfs.bclone_enabled=1 and
the bulk -a build paniced (having stored 128 *.pkg files in
.building/ first):
# more /var/crash/core.txt.3
. . .
Unread portion of the kernel message buffer:
panic: Solaris(panic): zfs: accessing past end of object 422/1108c16 (size=2
18 matches
Mail list logo